vilu Posted January 5, 2015 Posted January 5, 2015 I'm using SimpleNetworkWrapper to send packets that implements IMessage. Everything worked fine on 1.7.10 but now if I send packet from client side to server, I can see from console that it's the client that handles packet when its handler is registered to be on server-side. So here is some code. @EventHandler public void preInit(FMLPreInitializationEvent event) { network = NetworkRegistry.INSTANCE.newSimpleChannel(Info.modChannel); network.registerMessage(BlockPacket.HandlerServer.class, BlockPacket.class, 1, Side.SERVER); network.registerMessage(BlockPacket.HandlerClient.class, BlockPacket.class, 2, Side.CLIENT); } BlockPacket.ServerHandler: public static class HandlerServer extends BlockPacket implements IMessageHandler<BlockPacket, IMessage> { @Override public IMessage onMessage(BlockPacket message, MessageContext ctx) { int receivedInt = message.someInteger; System.out.printf("BlockPacket.HandlerServer.onMessage: Received integer was %s", receivedInt); return null; } } I'm trying to send packet from GUI: modname.network.sendToServer(new BlockPacket(1234)); and then I can see from console that it's send and received but: [modname-CLIENT] BlockPacket.HandlerServer.onMessage: Received integer was 1234 Let's say I want to send packet from a gui to the server, and there are values I want to set to the tileentity. If I set those values by using received packet it will update only client side tileentity, not server side as it should. So any ideas how to fix this? And this same thing happens for all packets sent to server handler. Quote
vilu Posted January 5, 2015 Author Posted January 5, 2015 BlockPacket.ServerHandler: public static class HandlerServer extends BlockPacket implements IMessageHandler<BlockPacket, IMessage> { @Override public IMessage onMessage(BlockPacket message, MessageContext ctx) { int receivedInt = message.someInteger; System.out.printf("BlockPacket.HandlerServer.onMessage: Received integer was %s", receivedInt); EntityPlayer player = ctx.getServerHandler().playerEntity; if(player != null) { Container container = player.openContainer; if (container != null && container instanceof SomeContainer) { //Note: IGuiHandler returns SomeContainer that extends Container for server. BlockPos pos = ((SomeContainer)container).getTileEntity().getPos(); TileEntity te = player.worldObj.getTileEntity(pos); if(te != null && te instanceof BlockTileEntity) { ((BlockTileEntity)te).setDataFromPacket(receivedInt); } else { System.out.printf("BlockPacket.HandlerServer.onMessage: No tileentity found at %s", pos.toString); } } } return null; } } and console says: [modname-CLIENT] BlockPacket.HandlerServer.onMessage: Received integer was 1234 [modname-CLIENT] BlockTileEntity.setDataFromPacket: Got data 1234 but if I run exactly the same code (except blockPos, it were x y z coordinates) in 1.7.10 console says: [modname-SERVER] BlockPacket.HandlerServer.onMessage: Received integer was 1234 [modname-SERVER] BlockTileEntity.setDataFromPacket: Got data 1234 Quote
vilu Posted January 5, 2015 Author Posted January 5, 2015 I was thinking the same, but it's weird because there are lot of cases that logger recognizes server as it should. After I did some debugging I see that tileentity losts given data after changing associated block metadata... Quote
vilu Posted January 5, 2015 Author Posted January 5, 2015 Sorry it was typo. Just quickly renamed some parts of code. It doesn't extend BlockContainer, the tileentity of block instead does. I didn't remember that BlockContainer actually exists. I'll edit my posts. Quote
vilu Posted January 5, 2015 Author Posted January 5, 2015 Well, no specific reason why =D Actually its much efficient and easier way to do all those things I do.. just never thought it. I think that there were some case that I had problems with containers or something and therefore I made sure that Container would never return null value for getTileEntity() or something. And I just left it like that so, that's the background story behind. But back to the problem. I did more digging and I've noticed that every time I set blockstate (aka. metadata) tileentity resets. Something like this: worldIn.setBlockState(pos, previousState.withProperty(POWERED, Boolean.valueOf(powered)), 3); worldIn.notifyNeighborsOfStateChange(pos, worldIn.getBlockState(pos).getBlock()); Quote
vilu Posted January 6, 2015 Author Posted January 6, 2015 That worked! Thank you so much So it was, just like you said, the logger messing up sides. Packet were handled in server-side just like it should be. It just looked like it is the client that receives server-side packet because tileentity did reset everytime when its metadata (blockstate) changed. I added console debug print to onBlockActivated and checked what it prints after sending packet and it did show same nbt tag compound for both sides. Then I changed current blockstate with one Boolean property and checked nbt tags again so then it reset tileentity. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.