[1.8][Nevermind] player.openGui vs sending packet.

[Ernio]

So I kinda touched piece of code I wrote long ago.

 

Anyway:

player.openGui, when called on: (logical side)

* Client = will ONLY call #getClientGuiElement

* Server = will call #getServerGuiElement and send packet to client that will call #getClientGuiElement.

 

Yeah, all cool, so what's the problem?

 

Try calling player.openGui in PlayerEvent.PlayerLoggedInEvent.

 

Logically - it SHOULD open gui on client (given client has gui assigned to proper id).

It doesn't.

At first i though that maybe someone forgot about thread safety, but nope (OpenGuiHandler) - it is there.

 

So question arises:

Why does this work:

@SubscribeEvent
public void onPlayerLoggedIn(PlayerEvent.PlayerLoggedInEvent event)
{
Network.sendTo(new PacketSendGui((byte) 1), (EntityPlayerMP) event.player);
}

@Override
public IMessage handleClientMessage(final EntityPlayer player, final PacketSendGui message, MessageContext ctx)
{
Minecraft.getMinecraft().addScheduledTask(new Runnable()
{
	public void run()
	{
		player.openGui(RoAMain.instance, message.id, player.worldObj, (int) player.posX, (int) player.posY, (int) player.posZ);
	}
});
return null;
}

And this doesn't:

public void onPlayerLoggedIn(PlayerEvent.PlayerLoggedInEvent event)
{
event.player.openGui(Main.instance, 1, event.player.worldObj, (int) event.player.posX, (int) event.player.posY, (int) event.player.posZ);
}

 

I mean - it's literally same routine.

 

<Looks at Guru diesieben>

[Ernio]

http://images-cdn.9gag.com/photo/azbp0MB_460sa_v1.gif[/img]

 

Jesus christ. I totally missed that for the packet to actually be sent server->client - you need to NOT return null o server...