Magneticraft

Magneticraft

8M Downloads

Crash server 1.12.2

TheTestMod opened this issue · 17 comments

commented

java.lang.NoClassDefFoundError: com/cout970/modelloader/internal/CustomModelLoader

Full crashlog: https://pastebin.com/bF8hGcK2

commented

Use ModelLoader 1.1.3, 1.1.4 has a bug and doen't work on servers. both versions work perfectly with magneticraft

commented

Thanks!

commented

One moment:
MC (Client) need the ML 1.1.5 (so that MC can start up), BUT the server only work with ML 1.1.3 = Result = I can't connect to the server, because v1.1.3. Häääääääää

PLS HELP xDD

commented

The latest version of Magneticraft ONLY requires modelloader in the CLIENT you don't need modelloader in the server anymore.

commented

Edit: without the modelloader, my server crash all the time. (at the start up)
(this crash is also in the linked issue from NillerMedDild)

crash-2018-11-08_16.46.44-server.txt

commented

oh, I see the problem, a multiblock is using a function from the library in the server

commented

Ahhhh, I try it. ^^

commented

Please reopen this, I am facing the exact same issue

commented
commented
commented

Just add the ModelLoader jar into the server

commented

Doesn't work even with 1.1.5 @cout970

commented

Some versions ago, ModelLoader as loaded in the server and the client, but it's only purpose is to load models for the client, so I changed it to be client side only, then I got people complaining that Magneticraft wasn't loading on the server, that was because ModelLoaded adds a bunch of vector and matrix utilities and Magneticraft was using some functions on the server side. In this new release I added an annotation to make forge load only the utilities in the server, the rest of the library is only loaded in the client.
That's why you get that the library is disable in the server.

commented

The server says "Disabling ModelLoader as its client side only" (not a 1.1.6 new issue, appears since long time ago)
I'll still run the server with it, but why does this appear?

commented

Fixed with 1.1.6, gonna close #152

commented

ok, so just put it there and let it go, got it and thanks :D