You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
my request is this: in a strategy where new players get one of the multiple spawns set in a local world (on first join: spawnLocalRandom strategy), to have a new command to disable a spawn from future to be get by new players, but to remain recorded for existing players. In this way there were a way to disable overpopulated spawns without issues with existing players.
Thanks.
ps: in my humble opinion, i suggest to create a command like /spawninfo to visualize details about a spawn (e.g. if active or not) and a /spawnenable and /spawndisable command.
The text was updated successfully, but these errors were encountered:
This is actually possible already using some of HSP's strategies, though not as straightforward as just flipping on a flag. There might be an example for this in the examples, I don't remember. I know this works because this is the last feature I added and used on my server before I shut it down a few years ago.
Hello,
my request is this: in a strategy where new players get one of the multiple spawns set in a local world (on first join: spawnLocalRandom strategy), to have a new command to disable a spawn from future to be get by new players, but to remain recorded for existing players. In this way there were a way to disable overpopulated spawns without issues with existing players.
Thanks.
ps: in my humble opinion, i suggest to create a command like /spawninfo to visualize details about a spawn (e.g. if active or not) and a /spawnenable and /spawndisable command.
The text was updated successfully, but these errors were encountered: