# Check which Rust worlds actually enforce a ban

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md)

Once staff have decided where a ban applies, test that the game enforces the same scope. A setting or panel entry gives you the intended result. A fresh join with a test account tells you what the player experiences.

## Write down the expected joins first

Use two isolated test worlds with test accounts that can normally join both, and keep production enforcement out of the rehearsal. The example starts with a temporary local test ban already set on Birch Weekly. Birch Monthly should allow the same account. Give each world a distinct join address and keep another regular test account as your comparison.

Read any local and shared ban entries that apply to the test account. Label each entry with its owning tool and scope. If you use Facepunch's centralized ban check, it queries the list on a join. An existing session is not proof that a newly added entry was checked.

## Run a fresh join on each world

Keep the world name and any refusal text beside the result. Use a fresh connection, including for a test of removal.

| Test | Expected result |
| --- | --- |
| A regular comparison account joins each known address | Both worlds accept the join. Otherwise diagnose that world's access or availability before judging the ban. |
| The restricted test account tries Weekly and Monthly | Weekly refuses the join for the test ban. Monthly allows it. |
| Remove only the temporary test ban in the tool that owns it and retry | The account joins Weekly again. Monthly still accepts the same join. |
| If you also test a shared rule, use a separate clean test account | Both named test worlds enforce it as expected. When you remove the test entry, both worlds return to the baseline. |

## Check the layer that still reports a restriction

When the join does not match the expected result, confirm the address and check the local, shared and host records for that test account. If you removed one entry and a different recorded restriction still applies, keep that restriction intact and verify what it covers. Finish when every join agrees with the written scope on the isolated worlds.

In a disposable Oxide run, removing managed test bans left unrelated entries from another tool present. That run checked the live game list on one host without connected clients. Use the two join tests to verify the behavior of your own worlds.

## Sources

- [Facepunch centralized ban checks at join time](https://wiki.facepunch.com/rust/centralized-banning)

## Related resources

- [How to review a ban appeal for your Rust server](https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/index.html.md)
- [Handle one conduct incident reported from two Rust worlds](https://rustsc.com/learn/community/handle-a-conduct-incident-reported-from-two-rust-worlds/index.html.md)
- [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md)

---

HTML version: https://rustsc.com/learn/troubleshooting/check-a-rust-ban-on-the-intended-worlds/
