General Category > General Discussion

stop-npc-spawning=False = No NPCs on newly created world.

(1/1)

D1G1T4L3CH0:
When starting a newly created world for the first time when the configuration file has stop-npc-spawning=False, NPCs don't spawn of course, but they don't show up after npcspawns is back on.

This could be accidentally done and would require spawning an old man in the wrong place (he wouldn't have a home spawn near the dungeon), and the guide won't be available unless spawned also.

This isn't really a bug but I think it could be prevented with a small warning on the console before creating a new world if stop-npc-spawning=False is detected. But probably there's some easier/better way to avoid this.

DeathCradle:
I think the notification would be suiting, as disabling spawning they would have to have done so via the config anyway which implies they do actually want it off?

D1G1T4L3CH0:
Yeah that's true. However only reason I had it on is because I was using an old properties file after updating my server.

Also, if a user chooses to turn it on, they may not be aware that after creating a new world with it on, they will have no npcs even if they turn on npcspawns later. Maybe they want to allow their players to get a house built before having to deal with spawns...

Another solution would be to keep intact, the spawn location(s) of the Old Man (and guide?). That way if an old man is spawned later, it will (will it?) have a home already that it should teleport to when out of the character's view.

EDIT: Maybe just comment the line right above that option in the config file. To let the user know the Old Man and Guide NPCs will not spawn and will have to be manually spawned later. Also the Old Man will not call a dungeon home.

Navigation

[0] Message Index