Leaderboard

On the surface the problem appears to be Mekanism doing something wrong, you can try using MC Edit to look around and delete/replace any Mekanism transmitter blocks (cables probably). If that doesn’t fix the problem, you can try some other things. You could also talk to the author of Mekanism (or create an issue on their issue tracker) and see if they can help you. If that doesn’t fix it you can try removing your coremods Extra Utils 2 appears to be broken, you could try removing it. Something to do with events appears to be going wrong in the mod wasteland. The mod Ores Core has a weird character in its name

You aren't handling client vs server. You need a !world.isRemote check.

I did say "very simple mod", your wrapper could inject some autogenerated models (I'M NOT RECOMMENDING OR SUPPORTING OR ENCOURAGING OR ENDORSING DOING THAT!) Depends what your trying to port, I just ported a 1.7.10 rendering based mod to 1.12.2 (it took me almost a year to learn the stuff required, but the mod was pretty high level). If I remember correctly, aside from the rendering changes 1.7->1.8 wasn't that big of a change, so you could probably go straight from 1.7 to 1.12.2. The best guide is learn to mod in 1.12.2, then take that experience and use it to port the old mod. Forge code doesn't change too much except when a new version comes out (they save up forge changes for new MC versions), but yeah me/someone has to write a new wrapper for every supported forge version (which should be every forge version)

Well its actually 100% possibly if you're willing define backwards compatible as rewriting the mod for every version. If your mod is very simple (just adds blocks & items etc.), you could also use/make a system (API) that handles all the registration & stuff while not externally changing from version to version (this still means you/someone else has to rewriting the mod for every version).

Have you tried running it without the gui? The one time I ran the server with a gui, it made things run slow, so if you haven't, try it without it.

I have no sympathy for you players who use Netease, their entire business model is bad and abuses the hard work that we here at Forge, and other modders do. If they want to start complaining that I don't produce Forge fast enough, then they can start helping out. But no they just sit back, toss DRM onto things, and just rake it in. It'll be done when it's done.

Well... I got a new result. Pressing F5 causes a new crash (I'm following Mekanism's example). Edit: Never mind, I loaded a new world, and it works. Mekanism, you are my lord and savior! (and thank you, Cadiboo)

williewillus is maintaining a primer on the 1.13 changes here: https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a It'll be significant work for modders but I'd say considerably easier than 1.7 -> 1.8 was.