Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Disconnection From Server When Placing Modded Block


Recommended Posts

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 by octa
Link to post
Share on other sites

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.

Link to post
Share on other sites

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.

Link to post
Share on other sites

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.

Link to post
Share on other sites

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?

Link to post
Share on other sites
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.

  • Thanks 1
Link to post
Share on other sites

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 by octa
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • So I had no clue what topic to put this under because its not really modding with forge but modding forge itself. So I have terrain generation mods that are only server side and Bungeecord that has Geyser packet translator so people on bedrock edition can play as well, but when a bedrock player connects it gets a unknown packet error. I tested the proxy on a Spigot server verifying it was forge. With no mods installed I still get the error. I got a wireshark log of it all and I found the packet where it aborts the connection due to the invalid packet but I have no clue how to stop it. When I still had the mods installed I disabled the forge handshake protocol but it did not fix the issue. If you know what part of forge is doing this or a way to fix it all together that would be awesome. I know modifying forge can end really baddy (definitely the handshake protocol) but I think that is my only fix here. Im open to any suggestions tho. I have run out of ideas to fix it so any help would be nice. Also it seems the packet id causing the connection error is 0xFE but im not sure cause the client also sends back a packet with that ID. I have a whole bunch of info collected so if you need any more information on the issue, I willing to give it, just not the ips on the wireshark log.
    • Okay, I got it working correctly now, but I'm not sure how to make it work with multiple blocks.   My Block Code:   package expanded.blocks; import javax.annotation.Nullable; import expanded.VanillaBuildingBlocks; import net.minecraft.block.BlockState; import net.minecraft.block.RotatedPillarBlock; import net.minecraft.entity.player.PlayerEntity; import net.minecraft.item.ItemStack; import net.minecraft.util.math.BlockPos; import net.minecraft.world.World; import net.minecraftforge.common.ToolType; public class CustomLog extends RotatedPillarBlock {            public CustomLog(Properties properties) {         super(properties);     }      @Override     @Nullable     public BlockState getToolModifiedState(BlockState state, World world, BlockPos pos, PlayerEntity player, ItemStack stack, ToolType toolType) {         return toolType == ToolType.AXE ? VanillaBuildingBlocks.acacia_log.defaultBlockState() : null;     } }
    • ? Registering the block and overriding a function inside the class are two completely different things
    • Ya but I'm not sure how I would actually add/implement it into the class correctly, and then registering the block correctly in my register class.
    • This tutorial from 1.12.2 is as easy as anyone could possibly explain it, it hasn't changed much til now except some slight changes here and there for you to figure out, it's pretty straightforward (https://www.planetminecraft.com/blog/forge-tutorial-capability-system/). Obviously instead of mana you'd just replace it with whatever else you're doing. All a capability is in essence is the ability to serialize/deserialize standard data types to an entity. When the player dies the game creates a new instance of a PlayerEntity object so your data won't automatically "transfer" over to that new object unless as you say, you copy the data over in an event hook. After you have this set up, if you want to access the data you store in player capabilities you create a class with a static get function that retrieves it.
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.