STYGION Panel a0.4.0 · Novinky

Writing to us from inside the panel goes somewhere. It had been posting to an address that stopped existing when the backend was rewritten, so a report written in the panel reached nobody — and the screen blamed a missing setting, which read like something nobody had got round to rather than a path that was gone. It now files through the STYGION ID this panel is licensed to, into the same queue the website and Discord file into. There is nothing to configure: if the panel is linked, it can write. The reply lands in your STYGION account, and the panel links straight to it.
STYGION_TICKET_URL and STYGION_TICKET_KEY are gone. They configured the path that no longer exists. Nothing replaces them.

A refused SFTP sign-in says so. It used to fail silently, which is indistinguishable from the server being down.
Stop actually stops a server that will not listen. A server ignoring the request stayed "stopping" until somebody restarted the panel.
Console commands survive a panel restart. The console keeps its own pipe rather than attaching to the container, so a restart no longer takes the input with it.
Sharing a server means something. Server users have a grant model and a gate behind them rather than a screen with nothing under it.
The release build ships the real frontend, instead of the placeholder that disappears at build time.