
ID Conflicts Viewer
A mod that simplifies the handling of conflicting IDs
About this Mod
This mod is created for modpack developers and is focused around giving extra info on Biome, Dimension and World Provider (since 1.1), Enchantment, Entity (since 1.1), and Potion IDs in your pack (and a little support with DataWatcher).
This includes following:
- Outputs a list of available IDs
- Outputs a list of taken IDs, followed by name and class of registered object
- When at least one conflict is detected, a report with all conflicts will be generated
- When a mod tries to register a new object in any entity's DataWatcher with an ID that is already taken, a detailed report will be generated in logs (or crash report if configured so), including all taken IDs at the moment of conflicting registration, followed by game crash.
Every generated file is located in IDCV folder of your minecraft installation directory.
Every file is most complete with all IDs at the moment of server start (either SP or MP) that is the moment of file generation. If any mod registers anything after that – that is out of mod scope. If the game crashes before that, either by other mod conflict detection or any other reason, no reports will be generated.
By default, any conflict will lead the game to forced stop (crash) except configured otherwise (DataWatcher ignores that config for internal reasons), in which case, it will send a warning message every 30 seconds, so you won't miss it.
This mod requires ASJCore to run!
Some technical info if something does not work:
Spoiler (click to show)
Have you installed ASJCore as mentioned above?
This mod is modifying vanilla minecraft classes loaded at runtime (no files are changed on your disk), including removing a forced exception in Enchantment constructor. If any mod is relying on that exception (like Artifice mod) – it will be broken, so you should disable enchantment part in config.
This mod is open for suggestions on new features or improvements, so send them in comments.
Available Versions
How to Install ID Conflicts Viewer on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set forge Loader
In the panel under "Egg", select the forge loader and matching Minecraft version (1.7.10).
Install Mod
Open the mod browser in the dashboard and search for "ID Conflicts Viewer". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.7.10
Server-side
~ OptionalRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
ID Conflicts Viewer server crashes on startup – what to do?
Most common cause: wrong forge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.7.10). You can switch loaders with one click in the panel.
Is ID Conflicts Viewer compatible with forge?
ID Conflicts Viewer officially supports forge for Minecraft 1.7.10. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with ID Conflicts Viewer – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if ID Conflicts Viewer consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install ID Conflicts Viewer with just one click on your server.