AdvancedBan tasks Task guides and troubleshooting for AdvancedBan. Check the installed release before changing configuration or data. Test an AdvancedBan time layout before staff use it A time layout can increase a punishment duration as a player repeats an offence. Test the progression on isolated records before using a layout name in a real moderation command. Follow the procedure Open the installed AdvancedBan configuration and its maintainer’s Features reference. Identify the exact time layout and reason shortcut staff intend to use; syntax varies with the release. Write the expected first, second and later durations in a small table. Include the outcome after the final configured entry, since that is where an unexpected long punishment can appear. Use an isolated staging copy with disposable account records and no connection to the production punishment database. Copy the relevant layout configuration without real player information. Issue the documented temporary punishment using the layout and inspect its actual expiry. Reverse the trial restriction while retaining the history needed for the next progression test. Repeat the offence on the same test account and compare each duration with the table. Separately test a new account to confirm progression is not incorrectly shared. Apply only the reviewed layout change to production using the release’s supported configuration procedure. Give staff the exact approved reason shortcut and escalation policy. Check the result Each trial should produce the documented duration for its position in the progression. Reversing a punishment may interact with progression differently from deleting history, so record the exact sequence used. Staff should be able to predict the next action before applying it. If the result is wrong If the layout yields a surprising duration, restore its previous definition and keep the staging records for diagnosis. Do not reset production history to make a layout appear correct. Check spelling, layout selection and prior offences before changing the escalation policy. References and related help AdvancedBan maintainer reference AdvancedBan maintainer reference Set up AdvancedBan with controlled moderation tests Find Minecraft logs and send useful troubleshooting details Check AdvancedBan warnings without accidentally escalating a real player Warning tests can trigger escalating moderation rules. Use disposable records and inspect the warning policy first so a demonstration cannot accidentally ban an established player. Follow the procedure Read the installed warning and temporary-warning configuration. Identify any thresholds, time layouts or actions that depend on accumulated history rather than the latest warning alone. Create a test environment with independent punishment storage. Choose a clearly labelled test account whose prior records can be inspected without mixing them with real player cases. Use the documented history or warning-list command to establish the account’s starting position. Record active warnings separately from expired or reversed entries. Issue one controlled warning with an unmistakable trial reason. Inspect its displayed duration, identifier and any action AdvancedBan reports as a consequence. Repeat only the number of warnings needed to verify the chosen threshold. Stop if an unexpected action occurs; do not continue adding warnings merely to see whether the system eventually behaves. Review the staff instructions against the observed result. Document when a warning is temporary and what staff must check before applying another warning to an existing account. Check the result The warning count and any configured escalation should agree with your written policy in the isolated test. A successful warning command proves only that a record was created; it does not establish that the next warning or an expiry will produce the intended result. If the result is wrong If the threshold is wrong, revert the warning-layout edit and inspect the complete trial history. Use targeted documented reversals for trial restrictions. Avoid deleting real punishment data or changing a customer’s warnings to manufacture a clean test case. References and related help AdvancedBan maintainer reference AdvancedBan maintainer reference Set up AdvancedBan with controlled moderation tests Find Minecraft logs and send useful troubleshooting details Give an AdvancedBan helper access to history without ban powers A support helper may need to explain a moderation message without being allowed to punish players. Build the role from the specific history commands your installed AdvancedBan version exposes. Follow the procedure List the information helpers actually need, such as an account’s punishment reason and expiry. Exclude IP-based account discovery and administrative database operations unless they are separately required. Find the exact read-command permissions in the Commands and Permissions reference. Keep a note of each node and whether it applies on the proxy or Bukkit server. Assign those nodes to a test group in your permission manager. Remove operator status from the test helper and inspect inherited groups for accidental moderation privileges. Query an approved disposable account’s history using the installed command syntax. Check whether the output includes hidden reasons or other information that should remain with senior staff. Test denial of a punishment command without supplying a live target. Confirm the helper cannot remove records, reload the plugin or issue bans through an alternative alias. Provide a support procedure that records the punishment identifier and passes appeals to authorized moderators. Keep screenshots of real player history out of public help channels. Check the result The helper should be able to retrieve the approved history and explain its status while failing administrative permission checks. Verify using the helper account itself. A console query or operator account cannot demonstrate that the restricted group is correctly configured. If the result is wrong If access fails, inspect the command’s documented node and execution platform before granting more permissions. If the role exposes too much, withdraw the new node and reassess the workflow. Do not solve a missing read permission by granting the plugin’s entire administrative permission tree. References and related help AdvancedBan maintainer reference AdvancedBan maintainer reference Set up AdvancedBan with controlled moderation tests Find Minecraft logs and send useful troubleshooting details Check AdvancedBan storage before changing from local files to MySQL A storage change can make existing punishments appear to disappear when the plugin simply reads an empty destination. Establish the supported migration route before switching the live connection. Follow the procedure Identify the AdvancedBan version, current storage mode and number of known records. Save examples of an active restriction and an older historical entry for comparison. Read the matching installation and migration guidance. Confirm whether your release offers a documented importer; do not assume changing the storage setting transfers existing records. Arrange a consistent backup of the current punishment storage and configuration while writes are paused. Keep a separate copy of any destination database before testing a migration. Create an isolated server copy and an independent empty test database. Rehearse only the officially supported migration procedure and capture the complete startup output. Compare the known record identifiers, account identities, reasons and expiry times in the destination. Verify an active test restriction is enforced as well as visible in history. Schedule production work only after the rehearsal succeeds. Prevent staff punishment writes during the final copy and keep the previous storage available for a coordinated rollback. CloudExa game panel reference. This image shows the panel, not the AdvancedBan interface. Check the result The destination should contain the same historical and active records, with a supported plugin startup and working enforcement. A database connection that succeeds but returns zero familiar records is not a completed migration. Confirm identity and time fields as well as counts. If the result is wrong If no supported migration path is documented for the installed release, retain the current storage and request maintainer guidance. Do not merge tables by guessed column names or restore only a plugin jar after schema changes. Roll back the matched configuration and storage together. References and related help AdvancedBan maintainer reference AdvancedBan maintainer reference Set up AdvancedBan with controlled moderation tests Find Minecraft logs and send useful troubleshooting details Lift one AdvancedBan restriction after an approved appeal An appeal reversal should affect the intended punishment while leaving the player’s other records available. Review the record and command syntax before applying an unban or unmute. Follow the procedure Confirm the account identity and the approved appeal decision privately. Record the punishment type, issuing moderator, reason and timestamp rather than relying on the latest chat screenshot. Inspect the account’s history and current restrictions with the documented read commands. Distinguish the appealed action from a later independent ban, mute or warning. Check the installed reversal command and permission. Use an identifier where that release supports it; otherwise confirm exactly how the account-based command chooses the active record. Execute the targeted reversal from the correct proxy or backend. Retain its response and ask the player to retry the previously restricted action through the usual public route. Read history and current status again. Confirm the appeal’s record is inactive while unrelated restrictions and historical evidence remain available. Attach the decision and reversal timestamp to your moderation case. Tell the player what was changed without exposing staff-only notes or another account’s network information. Check the result The selected restriction should cease enforcement and the audit trail should still explain the original action and its reversal. If access remains blocked by another system or restriction, identify that independently before making a second change. Do not assume every refusal belongs to AdvancedBan. If the result is wrong If the command targets an unexpected record, stop and ask a senior moderator to review the captured output. Avoid bulk unban, database edits or deleting the player’s entire punishment history. Correct the specific action with the release’s documented controls and preserve the case record. References and related help AdvancedBan maintainer reference AdvancedBan maintainer reference Set up AdvancedBan with controlled moderation tests Find Minecraft logs and send useful troubleshooting details 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. References and related help AdvancedBan maintainer reference AdvancedBan maintainer reference Set up AdvancedBan with controlled moderation tests Find Minecraft logs and send useful troubleshooting details