Web editor

/blazebans editor

Needs blazebans.command.editor. BlazeBans creates a session and sends you a link, which expires after 24 hours.

Open the link. The first thing it shows is a verification screen with a command to run:

/blazebans trust <code>

Run that in game. The browser then unlocks and you can edit.

The link alone is not enough to edit anything. Verification proves the person in the browser is the person on the server, so a leaked link is a dead link rather than access to your punishment configuration.

The session also belongs to whoever opened it. Someone else verifying against it is refused by name.

Everything in templates.yml:

Templates, grouped by type, with duration, reason, proof requirement, broadcast toggle and message, and console commands.

Ladders, as reorderable steps. Each step is a collapsible card showing its type, duration, reason, and badges for proof, broadcast, and commands. Only the step you are working on expands, so a long ladder stays readable.

The editor lists every placeholder available in a broadcast beside the field, which is the main reason it beats hand-editing: you are not switching between the file and a reference.

"Apply changes" is the only write action. Nothing is saved until you press it.

The flow is: the browser stages the change, your server polls for it, writes templates.yml, and reloads. The interface tells you which of those has happened, so you know whether the change is waiting on the server or already live.

Before writing, BlazeBans backs the existing file up and logs the backup path to console. If a change is wrong, the previous file is on disk.

When changes are applied, staff see a summary in game:

Editor audit | revision 3
templates.yml applied: 2 added, 1 updated
+ ban Combat-Cheats added
~ mute Spam updated: duration, reason
- kick Old-Template removed

That is deliberate. Configuration changing under a live server should be visible to the people running it, not silent.

Run /blazebans editor again for a fresh link at any time.

Only templates.yml. Not settings.yml, not database.yml, not discord.yml, and not the message files.

That boundary is deliberate. Templates are what a head moderator adjusts weekly; database credentials and permission behaviour are not, and exposing them through a browser session would be a larger attack surface for no real gain.

The editor never shows license keys, server credentials, session tokens, or the raw YAML document.

The server needs outbound HTTPS to blazestudios.store, and a valid license. Both are already true for a normal install, but a server behind a strict egress firewall will see the editor fail to open a session while everything else keeps working.

templates.yml is a normal file. Edit it however you like and reload:

/blazebans reload templates.yml

The editor is a convenience, not a requirement. Format details are in Templates and ladders.

The MiniMessage editor is the companion piece: write and preview broadcast messages and ban screens there, then paste the result into a template.