So i want to send a packet from the server the the client and when receiving the message i need the client world. But when starting a server the server crashes because the Minecraft class does not exist on the server. But the message should just be received on the client side. Now i don't really know how to solve the problem.

MessageHandler:

public class CPacketSyncEntitySpawnerHandler implements IMessageHandler<PacketSyncEntitySpawner, IMessage> {

	@Override
	public IMessage onMessage(PacketSyncEntitySpawner message, MessageContext ctx) {
		World world = Minecraft.getMinecraft().world;
		
		TileEntity tileEntity = world.getTileEntity(new BlockPos(message.getX(), message.getY(), message.getZ()));
		if (tileEntity instanceof TileEntityEntitySpawner) {
			TileEntityEntitySpawner t = (TileEntityEntitySpawner) tileEntity;
			t.setEntityID(message.getEntityID());
		}
		return null;
	}
	
}

 

And that is how i registered my Message:

CrystalicVoid.CONNECTION.registerMessage(CPacketSyncEntitySpawnerHandler.class, PacketSyncEntitySpawner.class, 0, Side.CLIENT);

 

I also tried to work with the proxy:

World world = CrystalicVoid.proxy.getWorld(message, ctx);

But then in singleplayer it uses the ClientProxy.

Edited March 9, 20196 yr by Meldexun

The problem is that i want to send a packet from the client to the server and then when the packet is received on the server in need the world of the server. But when i send the packet in singleplayer it always picks the world of the client and not of the server when using SidedProxy. It seems logical but doesn't achieve what i want.

My MessageHandler:

Spoiler

public class PacketSyncEntitySpawnerHandler implements IMessageHandler<PacketSyncEntitySpawner, IMessage> {

	@Override
	public IMessage onMessage(PacketSyncEntitySpawner message, MessageContext ctx) {
		World world = CrystalicVoid.proxy.getWorld(message, ctx);
		
		//do stuff
		return null;
	}
	
}

 

 

My ClientProxy:

Spoiler

public class ClientProxy implements IProxy {
	
	@Override
	public World getWorld(PacketSyncEntitySpawner message, MessageContext ctx) {
		return Minecraft.getMinecraft().world;
	}
	
}

 

 

My ServerProxy:

Spoiler

public class ServerProxy implements IProxy {
	
	@Override
	public World getWorld(PacketSyncEntitySpawner message, MessageContext ctx) {
		return ctx.getServerHandler().player.world;
	}
	
}

 

 

This should work with a dedicated server and a dedicated client. But in singleplayer it always gives the world of the client side and not of the logical server side.

Edited March 9, 20196 yr by Meldexun

So now i got this:

Spoiler

	@Override
	public IMessage onMessage(PacketSyncEntitySpawner message, MessageContext ctx) {
		World world = null;
		if (ctx.side.isClient()) {
			world = CrystalicVoid.proxy.getWorld(message, ctx);
		} else if (ctx.side.isServer()) {
			world = ctx.getServerHandler().player.world;
		}
		
		//do stuff
		return null;
	}

 

And now it's working.

When received on a client side it now uses @SidedProxy because using Minecraft#getMinecraft()#world directly would obviously crash the server.

And when received on a server side i doesn't use @SidedProxy because in singleplayer it would give me the the world of the client and not of the logical server.

Maybe there is a better solution?

Edited March 9, 20196 yr by Meldexun

@SidedProxy distinguished between physical sides. You seem to want to distinguish between logical sides. Also, any interaction with minecraft objects from a packet thread needs to be done inside of a scheduled task.

11 hours ago, Cadiboo said:

@SidedProxy distinguished between physical sides. You seem to want to distinguish between logical sides. Also, any interaction with minecraft objects from a packet thread needs to be done inside of a scheduled task.

That's why i asked for help. And i will look at scheduled tasks. Thanks.

 

40 minutes ago, diesieben07 said:

Your message handler knows the side it is received on. Just access the server world directly, do not use your proxy for that. Your proxy should have a getClientWorld method, which throws an exception on the server.

Isn't that what i'm doing in my latest post? When the packet is received client side (what i check with ctx#side#isClient()) then i use my proxy and when recieved on server side i directly access the world.

4 minutes ago, diesieben07 said:

You do not need to check which side it's received on. Packets should only go one way.

But i need to send it both ways.

I have a block with a tileentity and a gui that opens when the block is right clicked. When the tileentity is loaded on client side it sends a packet to the server which requests that the data from the server tileentity is send with a packet to the client.

And then when pressing DONE in the gui it sends a packet with the data from the gui to the server.

That seemed to be the most efficient way.

8 minutes ago, Meldexun said:

tileentity is loaded on client side

Why do you need to send a packet when the tile entity is loaded? Please elaborate.

If you only want to get data from the server whenever the GUI is opened, you probably wouldn’t need two packets (depending on your needs, you might not even need packets at all).

 

If you need to send data to both sides, use two packets.

Edited March 10, 20196 yr by DavidM

23 minutes ago, DavidM said:

Please elaborate. 

I need the data for opening the gui. It should display the data from the server.

21 minutes ago, diesieben07 said:

Vanilla already has a perfectly adequate data-syncing mechanism for tile entities.

I have read that i should create my own packet and handler to sync my tile entity most efficiently. And my tile entity should just sync when someone interactes with it. I think vanilla always syncs the tile entities and that would create much network traffic (i just think so. Correct me when i'm wrong)

 

21 minutes ago, diesieben07 said:

If you treat them the same, you enable cheating.

It should be kind of cheating. The block is creative only and the client should say "This is the new data, use it from now on"

Edited March 10, 20196 yr by Meldexun

1 hour ago, diesieben07 said:

Okay. So then: When the TE is right clicked (or whatever the interaction is), send a packet from server to client which contains the data. The client can then open the GUI. 

But then it always sends a packet from server to the client when the block is right clicked. When you right click the block it 3 times in a short period of time it sends 3 packets.

Currently it sends only a packet when the tile entity is loaded. So it sends just 1 packet.

1 hour ago, diesieben07 said:

Except if you use the same packet the packet can be sent by survival clients as well. For blocks that are thousands of blocks away. 

I don't understand how a new second packet solves this issue.

I could check when the packet is received server side if the sender is in creative mode.

1 hour ago, diesieben07 said:

that is the same as vanilla syncing then.

I thought vanilla sends more packets. But that doesn't matter. You are right. I will change it so it only sends a packet from server to client when the block is right clicked. Often opening the gui will cause much traffic but when not opening the gui it causes zero traffic. Seems the best option.

It looks like i have to open the GUI server side. I'm using a GuiHandler and when calling player#openGui at the end of my packet handler on the client side it seems to create a broken gui.

So what i now try to do is:

When the block is right clicked on server side it will send a packet to the client which tells him to update the tile entity with the data sent from the server. As an answer the client then sends a packet which requests the server to open the gui. When received on the server it checks if the player is in creative mode and then opens the gui.