Anyone who tries to log into my ATM9 server after the 0.1.11 update gets this same error upon Loading Terrain

I tried a combination of restarts for the clients and server and still get the error.
I tried generating a new world and the issue was not there.
I couldn't see anything in the logs that called out a specific reason for the disconnection.

Same Problem for me, my console on the server says after this:
[20:21:22] [Server thread/ERROR] [sophisticatedcore/]: Item thermal:satchel is set to not be affected by stack upgrade in config, but it does not exist in item registry
[20:21:22] [Server thread/ERROR] [sophisticatedcore/]: Item ars_elemental:caster_bag is set to not be affected by stack upgrade in config, but it does not exist in item registry
[20:21:22] [Server thread/ERROR] [sophisticatedcore/]: Item ars_elemental:curio_bag is set to not be affected by stack upgrade in config, but it does not exist in item registry

client latest.log: https://mclo.gs/BpPZiQS
client debug.log: https://mclo.gs/P6bQlbP

Same for me: #507

Same for me: #507

Interesting that it's just you, everyone trying to connect to my server has the same error.

On a brand new world on version 0.1.11, craft map, right-click with map, crash. So definitely something to do with maps. But this doesn't explain why I can't load in on the previous world. I checked my inventory in NBTExplorer and I don't have a map on me

on my server one of our players has the item in his base on a item frame and when anyone goes near that chunk it boots everyone out with that error

on my server one of our players has the item in his base on a item frame and when anyone goes near that chunk it boots everyone out with that error

I wouldn't even know how to go about searching for something like that. I kind of knew that playing a beta pack might come with these risks though. So not the end of the world if we have to start anew.

I deleted the map data from the world/data/ folder and that seemed to work and allow me to log in
pic from my 0.1.9 just to show the files:

This was fixed with the 0.1.12 update

Issue has re-occurred for 0.2.4

@rmccarthy1504 is it the same error as shown before?