Hi,

 

world.isRemote should be set to false in a single player game, right ? Because I'm having an issue here :

 

@SubscribeEvent
public void onWorldLoad(WorldEvent.Load event) {
World world = event.getWorld();

if (world.isRemote) {
	// Executed even in single player
}
}

 

Is it normal ?

Client side != Singleplayer!

 

In singleplayer there is still a server running, only accessible for you unless you open to LAN.

World#isRemote

is true on the

client

side (rendering side), and

false

on the server side (logical side).

Forge's documentation explains sides in more detail here.

Then how can I test if the world is not local.

Then how can I test if the world is not local.

 

What exactly do you mean by that?

I think I found what I want :

 

Minecraft.getMinecraft().isSingleplayer()

 

With that I can now if this is a single player game.

You can only use that on the client side, as the

Minecraft

class is client-side only.

Yeah, but that's the point. I wanna know, on the client, if this is a single or multiplayer game.

Why? This sounds like a terrible idea to me.

 

Without context obviously ...

I synchronize settings between dedicated server and clients, hence the 'not singleplayer' test.

This is different.

Some blocks can be deactivated from the config file. If they are, so are the associated recipes. If a dedicated server deactivate blocks, the connected client should also deactivate them, because if not, the recipes will still show, but the result cannot be obtain. This is ugly.

There might be other issues I'm not thinking about, but with this, the client is always configured the same way as a dedicated server, except for client only settings but there is only one for now.

It's tricky simply because there is no clean way to intercept that the integrated server has been opened to LAN. I searched for a few minutes and saw nothing: The IntegratedServer#shareToLAN method is called from the button or the command, but I didn't see any way to "register a listener" or something like that.

Like you said, it's simpler to always send it. The client can just ignore it.