Locate AdvancedBan correctly on a proxy network
A moderation command can run on a proxy or a backend, but those placements do not automatically share enforcement. Map the installed copies before troubleshooting a player who can bypass a restriction by switching servers.
Follow the procedure
- Draw the normal connection path from the public proxy to each backend. List where AdvancedBan is installed and which storage mode each copy uses.
- Read the official installation guidance for the platform actually running each copy. Bukkit and BungeeCord support does not establish compatibility with every proxy product or fork.
- Compare the configuration of each intended participating copy without sharing database credentials. Identify separate databases or local files that explain different player histories.
- Use read-only history queries for one approved test record on each execution platform. Record the command response and which plugin owns any overlapping ban alias.
- Test a short authorized restriction on a disposable account through the public route, then try the intended server-switch paths. Keep backend addresses protected rather than opening them for convenience.
- Choose a documented deployment design and make one planned correction at a time. Update staff instructions so they know where commands run and which services enforce them.
Check the result
The same intended moderation decision should be visible and enforced wherever your documented network policy requires it. Different histories on different copies reveal a placement or storage problem, not necessarily a broken command. Verify actual public login and switching behaviour after correction.
If the result is wrong
If the architecture is unsupported, leave existing restrictions intact while planning a supported setup. Do not duplicate plugin files blindly or point unrelated production copies at shared tables without documentation. Restore the previous placement if a trial causes command or startup conflicts.