Creativecore Wiki › Guides › Troubleshooting Features in Dependent Mods
Troubleshooting Features in Dependent Mods
When using advanced mods like LittleTiles, AmbientSounds, or ItemPhysic Full, complex visuals, custom menus, and network data must all interact cleanly. CreativeCore coordinates these background processes.
Checking Dependent Mod Requirements
If a dependent mod fails to load properly, has broken menus, or refuses to open certain interfaces, verify the following in your game:
- Check the Mod Menu: Ensure CreativeCore is loaded alongside dependent mods. Mods like LittleTiles cannot build custom interfaces or manipulate tiny blocks without CreativeCore's underlying dynamic rendering and fake world support.
- Verify Custom Menus: When interacting with complex blocks or items from supported mods, CreativeCore generates the custom GUI screens. If a menu fails to appear, ensure no configuration errors were introduced via
/cmdconfig.
Verifying Background Systems
CreativeCore manages several automated functions that prevent common multiplayer and rendering issues:
- Data Transfer: It uses split packets to ensure large chunks of custom data transfer reliably across the network without disconnecting players.
- Item Grouping: It uses uniform InfoStack structures to keep item data organized across different systems.
If unexpected behavior occurs, open /cmdclientconfig or /cmdconfig to reset any misconfigured values back to their defaults.