Skip to content
Feature RequestOtherImplemented

More freedom with server name and description in the panel

Currently, there are restrictions in the web interface for some games regarding server name and server description, even though these characters are generally supported by the game itself. In Rust, I specifically noticed that characters like +, |, and / cannot be saved in the panel. Additionally, the server name and description are taken from the panel at startup, which means manual entries in the server.cfg are overwritten again. This makes it impossible to display the server exactly as it is actually supported by the game. Example in Rust: Desired server name: AIRDROP [ 2X | EVENTS | KITS ] Desired description: Airdrop 2x | Vanilla+ | PvP/PvE Zones | Raidable Bases | Playtime VIP | Balanced Kits | Active Admins Suggestion / Request: Please enable one of the following options: Less strict character restrictions in the panel for server name and description An optional deactivation of the panel takeover, so that values are taken directly from the respective config Generally more freedom for all games where the panel currently has stricter rules than the game itself This would not only be helpful for Rust but also for other game servers where names and descriptions should be individually formatted. Thank you.

Originally posted by denizlebaguette on our previous feedback board.

Ffeaturebase-import6 Apr 2026

Comments (2)

ZAP
Official response
30 Apr 2026, 03:06

Hi, thanks for the suggestion. I've forwarded this to our developers. At the moment, though, we're mainly focused on a completely new web panel, and that would already include options like the ones you mentioned. We expect to release the whole new web interface soon which would include these and make it more easier for you to maintain the server.

ZAP
Official response
28 Sep 2026, 17:41

In the new ZapX panel, server name and description are free-text fields without the old character restrictions, so names like the one in your example work. Marking this as completed.

Log in to comment.

Timeline

All important changes at a glance.

Official response from the ZAP team added.

From ZAP

28 Sep 2026

17:41

Status changed from “Open” to “Implemented”.

From ZAP

28 Sep 2026

17:41

Feedback

Do you have another suggestion?