“It says it is not protecting this server”
The line names a reason. Match it below.
- The licence was not accepted
- Check
license-keyandserver-nameinloader.ymlagainst what we issued. They have to match exactly, including case. - The licence has expired
- Renew, then restart. Nothing else is needed.
- The server name does not match
server-namehas to be the one your licence is registered to, not your server’s display name.- Every slot is in use
- More servers are running than your plan covers. A server that goes quiet frees its slot on its own. If this keeps happening, you need a larger plan.
- More players than your plan covers
- Protection resumes on its own when the count drops. If it is happening at peak every day, size up.
- It could not reach us
- Check outbound internet access from the server. Nothing needs an inbound port.
“It loaded but I get no alerts”
Check the staff member has realac.alerts, and that they have run /realac alerts. Alerts are opt-in per person.
Check RealScore.yml: a category set to off does not run.
Check whether the player is exempt. Anyone with realac.exempt is skipped by every check, and realac.* includes it.
“It alerts but never bans”
RealAC ships in monitor mode, which alerts and never bans. Set mode: enforce in RealScore.yml when you are ready.
Then check the category is set to ban, and that ban-commands is not empty.
Movement categories are alert-only by design. Setting them to ban does nothing.
“Discord alerts are not arriving”
Set enabled: true in discord.yml, put your webhook URL in, and run /realac testwebhook.
“The alert does not say which check fired”
That is deliberate. Alerts name the cheat category, never the internal check, because an exact check name tells a cheat developer which detection to work around.
“I think a flag was wrong”
/realac reportfalse <player>, pick the flag, say why. It reaches us with the full context attached.
Still stuck? Discord. Bring your console output from start-up.