I have the range set to 128: I:MegaTorchRange=128 on my SMP, but they spawn very close none the less. :/

• Minecraft 1.11.2
• Forge 13.20.0.2304
• TorchMaster 1.3.3.37

I just checked and the client has the option set to 32, does that matter?

This should only happen if the torch is not chunk loaded.

I'm always close to my home where the torch is.

I'm not sure what the issue could be. Some mods might cause additional spawns that dont use CheckSpawn, but i dare to say this is not the issue in your case.

Please try chunkloading the torch chunk if possible.

Also: Mobs are not allowed to spawn inside the radius, but they can still walk inside. This might also be an issue.

I use very few mods, where Botania is the only 'game changing' one. And I don't have any chunk loaders.

And that I'm aware of, but they usually don't walk around that much. The range is 128, so I find it unlikley they'll walked that far in a few minutes. :/

Is there any downsides to a larger range? Like performance? I could try to max it out.

no, range does not affect performance at all, just make sure the torch is always loaded. I think the default range is 10 chunks (160 blocks). Setting the radius higher wouldnt have an effect since a player cant load more chunks by default. You could also try placing more torches (a bit spread out) to increase the chance that a torch is loaded.

@Hund any news on this?

Uhm. I added a chunkloader to my world as a temporary solution.

When I go to the Nether and come back, it's like there's a delay on the torch (that's close to the portal) when the chunks gets loaded again and mobs has a chance of spawning? Keeping the area chunkloaded helps though.

this might be the issue. The delay is related to chunkloading sadly.
When a player moves to a new dimension, the chunk system loads the closest chunks first. If those chunks do not contain a torch, mobs will be allowed to spawn until the torch is loaded.

If you move the torch to the portal, mobs shouldnt be able to spawn when moving between the nether and the overworld. Sadly, there is still a chance of spawning when logging into the world while not being close to the portal.

There is a way to fix this, but it requires a fair amount of refactoring. I'm still not sure how to persist the torch information across world reloads/server restarts, among some other issues like the new burnout feature. But this I will handle in #23

Feature implemented in the v1.12 version of the mod. Earlier versions of MC will still require a chunkloader.