Unedited, locally-built CraftTweaker NPEs on a server

Question

Unedited, locally-built CraftTweaker NPEs on a server

Baughn opened this issue 7 years ago · 6 comments

Baughn commented 7 years ago

Issue Description:

Unedited, locally-built CraftTweaker NPEs on a server.

What happens:

On building and running a server from source:

git clone https://github.com/CraftTweaker/CraftTweaker.git ct --recurse-submodules
cd ct
gradle assembleMC1120
cp build/libs/CraftTweaker2-1.12-4.1.7.jar /path/to/server/mods/
<run server>

The server crashes with an NPE in JEI integration.

What you expected to happen:

Fewer crashes.

Script used (Please Pastebin or gist your script, posting an unpasted or ungist'd script will automatically close this issue):

None.

Minetweaker.log file (Please Pastebin or gist your file, posting an unpasted or ungist'd file will automatically close this issue):

http://ix.io/19CB

Affected Versions (Do not use "latest"):

Minecraft: 1.12.2
Forge: 1.12.2-14.23.3.2655
Crafttweaker: 6454933

Your most recent log file where the issue was present:

https://madoka.brage.info/crash-reports/crash-2018-05-07_00.42.19-server.txt

Baughn · Answer 1 · 2018-05-06T23:48:52.000Z

Then please push? I can't try to debug my other issue without working code.

jaredlll08 · Answer 2 · 2018-05-06T23:48:09.000Z

Fixed in dev, possible I didn't push, but it is fixed.

jaredlll08 · Answer 3 · 2018-05-06T23:51:50.000Z

done, what is your other issue?

Baughn · Answer 4 · 2018-05-07T10:51:38.000Z

A string too long error on login, which I think is provoked by using crafttweaker in a heavily modded setting with plenty of scripts. I wanted to confirm that before reporting, though.

jaredlll08 · Answer 5 · 2018-05-07T10:54:19.000Z

We don't send any data from the server to the client or vice versa in 1.12, so I doubt it is us.

…

On Mon, May 7, 2018, 12:51 Svein Ove Aas ***@***.***> wrote: A string too long error on login, which I think is provoked by using crafttweaker in a heavily modded setting with plenty of scripts. I wanted to confirm that before reporting, though. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#536 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFS9xe2h8iQ7hAdwfQqTOMPaLzAL681Kks5twCc6gaJpZM4T0PxG> .

Baughn · Answer 6 · 2018-05-07T18:01:33.000Z

Oh, but you do. Via chat.

I had a suspicion it was that, and it seems to have been borne out; commenting out all the chat commands fixes the bug. Well, since I've got this open anyway, I'm going to see if I can't make my bug report in the form of a PR.

Share to