Config Key Audit
The keys that shipped but did nothing before 1.5.0, what each one does now, and what to check after you upgrade.
A group of keys shipped in config.yml for a long time without any code behind them. Editing them changed nothing, no matter what value you gave them and no matter how many times you reloaded.
As of 1.5.0 every one of them is read. This page is the record of what was broken, what it does now, and the handful of things worth checking on your own server after the upgrade.
If you are setting a server up fresh, you do not need this page. Go to Configuration instead.
Fixed in 1.5.0
| Key | What it did before | What it does now |
|---|---|---|
storage.mysql.use-ssl | Never seen. The plugin read a differently spelled storage.mysql.useSSL, so SSL stayed off | Read as spelled. The old useSSL spelling is still honoured as a fallback, so hand added keys keep working |
freeze.prevent-movement | Ignored. Movement was always blocked | Gates the movement block. Set it to false and frozen players can walk |
freeze.prevent-damage | Ignored. Damage was always blocked in both directions | Gates the damage block |
freeze.prevent-commands | Ignored. No command blocking existed anywhere in the plugin | Blocks commands from frozen players, with the freeze.cannot-command message |
freeze.allowed-commands | Ignored, because commands were never blocked | The whitelist that prevent-commands checks against |
freeze.quit-punishment.enabled and freeze.quit-punishment.commands | Ignored. The plugin read a flat freeze.quit-punishment-command that the shipped file never contained, so no punishment ever ran | Read as shipped. Every command in the list runs from console, in order, with {player} replaced |
cps.check-duration | Ignored. The sample window was hardcoded to one second | Sets the sampling window, in seconds |
reports.duplicate-report-cooldown-hours | Ignored, and the duplicate check behind it always returned "allowed", so reports.duplicate-active could never be sent | Blocks a repeat report against the same target for this many hours, whether or not staff closed the earlier one. Sends reports.duplicate-active while it is open, reports.duplicate once it is resolved |
Two more things behaved the same way and are also fixed.
{threshold}incps.alertused to print as literal text. It is now replaced with yourcps.warning-thresholdvalue.{type}is filled from the newcps.type-leftandcps.type-rightkeys, so the whole alert reads in one language.messages.ymlshipped inside the jar and nothing ever loaded it. It no longer ships. All text lives inlang/<language>.yml, see Messages and Language.
What to check after upgrading
Your existing config.yml is kept as you wrote it. That is usually what you want, but four of these keys now have teeth they did not have before, so a value you set and forgot can suddenly matter.
Check cps.check-duration
This is the one that catches people out. The old shipped default was 10, and 1.5.0 ships 1. An upgrade keeps whatever number is already in your file.
At 10 the plugin averages ten seconds of clicks back down to a per second figure, so a two second burst of 20 CPS reads as about 4 and your cps.warning-threshold almost never trips. Set it to 1 unless you specifically want a smoothed reading.
cps:
check-duration: 1Check your quit punishment commands
freeze.quit-punishment.commands now runs. The shipped default bans the player and broadcasts it. If that block is still at its defaults and you did not intend to ban logout offenders, change it or set enabled: false.
If you previously added the flat freeze.quit-punishment-command as a workaround, it still runs, so leaving it in place alongside the list means both fire. Delete the flat key unless you want two commands.
Check freeze.allowed-commands
Frozen players are now blocked from every command that is not on this list. The shipped list allows /report and /helpop. Add whatever your players genuinely need, such as your ticket command.
Entries match with or without a leading slash. Aliases are not resolved, so list the alias as well if you want it allowed.
Check reports.duplicate-report-cooldown-hours
The default of 24 now applies. A player who reports someone cannot report that same person again for a day, whether or not staff have closed the earlier report. Set it to 0 if you would rather keep the old unlimited behaviour.
Removed in 1.5.0
/staffmode-debug is gone, along with the atstaffmode.debug.staffmode permission and the debug.staffmode-enabled and debug.staffmode-disabled messages. It toggled an internal flag that nothing read, and its description never matched what it did.
/freezedebug and atstaffmode.debug.freeze are untouched and still work. That is the command you want for testing freeze on another staff member.
If a setting still looks wrong after checking this page, ask on Discord. Bring your config.yml and the exact behaviour you expected.