Disconnection From Server When Placing Modded Block

[octa 0]

I'm playing around with making my own mod. It works fine in Singleplayer but when I test it on a server my client gets disconnected with error message Internal Exception: io.netty.handler.codec.EncoderException: java.lang.NullPointerException (there is no further stack trace) when I place the Portal Base block. I can reconnect just fine, but will get disconnected again when I place another of those blocks.

I haven't found much about this specific issue. Any help would be appreciated.

Code: https://github.com/eddie1101/PortalTest/

 

logs: (Though they're not very helpful, is there some way to make the error more verbose? A stack trace would really help)

Server: https://pastebin.com/JN6gnQyx

Client: https://pastebin.com/AWVavatz

 

Thanks in advance.

 

Edit: Attached .jar if you want to try to reproduce

basicportals-0.1.jar

Edited January 27 by octa

[diesieben07 7775]

Your repository is not complete, the gradle wrapper and build.gradle should be included to make it usable. The MDK comes with a properly configured .gitignore file for a reason.

 

Start the game with the system property forge.logging.mojang.level=debug to see the stacktrace.

[octa 0]

Repo is fixed. How do I run my client with system properties? It works on the server but when I add it to JVM arguments in the launcher's installation settings the game crashes.

[diesieben07 7775]

Your repository crashes for a different reason: You have two items with the same name.

Additionally, you are not registering your registry entries properly. You need to either use @ObjectHolder or DeferredRegister.

[octa 0]

Woops. Fixed the item names.

According to the docs, RegistryEvent.Register is a valid way of registering entries, so I'll stick with that since I know it better.

The repo should build now, so back to my original question: Why when placing a Portal Base does the client get disconnected from the server?

[diesieben07 7775]

33 minutes ago, octa said:

According to the docs, RegistryEvent.Register is a valid way of registering entries, so I'll stick with that since I know it better.

That is fine, but then you must use @ObjectHolder instead of manually assigning fields.

 

37 minutes ago, octa said:

Why when placing a Portal Base does the client get disconnected from the server?

It crashes because your TileEntityPortalBase creates an SUpdateTileEntityPacket with a null BlockPos.

[octa 0]

Oh, that makes sense. Do you have a suggested way of initializing that BlockPos? I can't think of anything other than assigning a symbolic value which gets verified before use, but that seems clumsy.

Edit: Nvm, I was trying to return some nbt data instead of the tileentity's actual position. Thanks for the help.

Edited January 27 by octa

[diesieben07 7775]

It makes no sense to return any position there but the TEs own, which you can get via TileEntity#getPos.