Forge has found world ID mismatches
Posted 15 February 2013 - 07:24 PM
Forge Mod Loader has found world ID mismatches
ID 22760 (ModID: WeatherMod, type weather.worldObjectives.ItemTornado) is missing
ID 22761 (ModID:WeatherMod, type weather.worldObjectives.ItemTornado) is missing
ID 1900 (ModID: WeatherMod, type weather.blocks.BlockTSensor) is missing
ID 190 (ModID: WeatherMod, type weather.blocks.BlockTSiren) is missing
ID 22758 (ModID: WeatherMod, type weather.worldObjectives.ItemTornado) is missing
ID 22759 (ModID: WeatherMod, type weather.worldObjectives.ItemTornado) is missing
ID 22757 (ModID: WeatherMod, type weather.worldObjectives.ItemTornado) is missing
If you need more Information im free to give it to you
Sorry if i make mistakes my grammar sucks.
Posted 15 February 2013 - 07:41 PM
Posted 15 February 2013 - 08:15 PM
Could it be the config file in the config folder in the server?
Posted 20 February 2013 - 02:15 PM
Other reason could be because you didn't install the mod well.
Posted 27 February 2013 - 11:18 PM
Posted 03 March 2013 - 06:38 PM
Posted 28 March 2013 - 01:09 PM
Now it appears Forge now has a variety of reason why it would spit out mismatch ID's between client and server:
The ID Mismatch from this thread comes from a world being loaded that has block id's either not being used due the mods being removed.
Another instance comes from the client and server config files for the mods being used not being the same, so your client and server config files need to match so the block ID and Item ID must match.
If your server is being upgraded and you remove any mods, the existing Block id's used by the mod not present anymore will cause problems when blocks from that mod has been placed in world, this could default to zero id entities and cause all sort's of weird problems, so as a precaution if you do remove a mod entirely use MidAs world id changer and change the block id that was used by this mod to something like dirt and you problem will be solved, you can also use that tool to swap out block id's and comes in handy when you have mods on block id's where minecraft is now using that same block id.
Now another instance where your client will spit out the mismatch error and dissalow you to connect is when the loading order of your mods aren't the same, now back in the days this would not have cause a problem but it does now, so make sure that the loading order is exactly the same, and example of this would be we had repower on the server using the original jar names, but on the client connecting to the server the redpower files were rename to have a y in front like yredpower.jar redpower loaded after mod x on client and before mod x on server and amazingly that cause a mismatch id and client could not connect why in the world that would be like that I have no idea but it had some implications.
Forge modloader has an extensive log file being generated now, but it won't always provide you with this type of information so i hope this helps someone in the near future.
Posted 08 June 2013 - 05:32 PM