Join our Discord and be part of our community!
Binary Testing Your Plugins or Mods
Binary testing helps you isolate a single plugin or mod that is causing an issue on your server when the exact cause isn't immediately clear. This guide covers when to use binary testing, how to safely prepare your server, how to perform the test step-by-step, and how to restore your plugins or mods once the problematic one has been identified.
Identify When to Use Binary Testing
- Use binary testing when your server is experiencing a crash, lag, or undesirable behavior (such as vanilla mechanics behaving unexpectedly) and the Console tab doesn't show a clear error pointing to a specific plugin or mod.
- If the console logs already reference a specific plugin or mod by name (for example, lines containing
Caused by,Failed to load, orDuplicate mod), remove that plugin or mod directly instead. Binary testing is only necessary when no clear culprit is visible in the logs. - Binary testing works by removing half of your plugins or mods at a time, testing the server, and narrowing down the remaining half until only the problematic file is left.
Prepare for Binary Testing
Before removing any files, stop the server and take a fresh backup. This ensures you can safely restore the server to its current state at any point during the process.
- Navigate to the Console tab and click 1 Stop. Wait until the server shows 2 Offline before continuing — do not perform binary testing while the server is running.
- Create a manual backup before making any changes. See No access for full steps.
Perform Binary Testing
- Open the Files tab and navigate to your
pluginsormodsfolder. - Create a temporary folder outside of the
pluginsormodsfolder (for example,disabled-plugins) to hold files you remove during testing. Move files here instead of deleting them, so you can restore them once the problematic file is found.
- Move half of your plugins or mods into the temporary folder.
- Start the server and reproduce the issue.
- If the issue persists, the problematic file is in the half still installed. Move half of those into the temporary folder and repeat.
- If the issue is resolved, the problematic file is in the half you removed. Move half of those files back into the plugins/mods folder and repeat.
- Repeat this process, halving the active group each time, until only one plugin or mod remains as the suspect.
Confirm the Problematic Plugin or Mod
- Once you've narrowed the issue down to a single suspect, move every other plugin or mod back into the
pluginsormodsfolder, leaving only the suspect out. - Start the server and confirm the issue does not occur.
- Move the suspect plugin or mod back in on its own, restart the server, and confirm the issue returns.
- This confirms the plugin or mod is the source of the issue.
Restore Your Plugins or Mods
- Once confirmed, move all other plugins and mods back into the
pluginsormodsfolder. - Decide how to proceed with the confirmed plugin or mod:
- Check for an updated version that may resolve the conflict.
- Reach out to the plugin or mod's developer or community for support.
- Leave the plugin or mod out of the
pluginsormodsfolder if it isn't essential. - Restart the server once your final plugin or mod list is in place.
Contact Support
- If binary testing doesn't resolve the issue, or you'd like assistance confirming a result, open a support ticket and include:
- A description of the crash, lag, or behavior you're seeing.
- The steps you've already taken, including which plugins or mods you've tested.
- The relevant portion of the server's
latest.log.
If you require further assistance, you can open a support ticket here.
Feedback and suggestions can be submitted here or further discussed on our Discord server.