Hey all, for those wanting to do some bug testing with the Purge, I’ve got some inside info’s. Looks around to make sure nobody is looking. Alright so…whispers… here’s what you can do if you want to try some admin commands.
First, some back end info!
As your Purge Meter fills up, the server periodically checks to see if anybody on the server (or single player) is Purge eligible. If not, then it goes back into it’s slumber. How often it checks is determined by the Sever Setting, “Purges Per Day.” The higher this setting is, the more often the server will check. This could impact your vanilla testing, so that’s why I added this note here.
There also might be a random variable in here, as sometimes a Purge will take a while to start, while other times when at high speeds (see below) I would have a Purge start RIGHT after an active one finished on it’s own.
Screenshot below is for reference on what I refer to. The actual settings used in the screenshot are there just for testing purposes (I wouldn’t actually recommend you put a threshold of 250 lol).
Additionally, for Single Player, the Player must be within range of the base (unknown max distance) in order for the Purge to trigger. You can have multiple bases (say one in the desert, and one in the north) but the Purge will always trigger to your immediate area. For servers, the Purge doesn’t have this requirement. You could be farming in the Mounds and get a Purge at newb river.
I haven’t tested on a server yet to see if its the same situation as far as having a player (or clan) own multiple bases. The server will trigger a purge if a player isn’t in range of the base, I am just not sure about multiple base situations (yet). So server peoples, get to testing!
Now then, for the admin commands.
These two commands work as they indicate. They will fill your Purge Meter to the top, and empty it to the bottom.
Please note: In Single Player, these two commands are currently bugged in that they VISIBLY don’t show to be working when IN A CLAN. Behind the scenes they are doing what they are supposed to, but you the player won’t physically see the meter move. When NOT IN A CLAN these two commands work correctly on both ends. Server wise, I haven’t tested it out yet to know if its updating the meters correctly (again, visually only).
These two commands do the same as the two previous, fill and empty. They work correctly in or out of a clan in Single Player. For Single Player testing, its best to use these.
This command will start the next available Purge. It does NOT happen immediately after typing this in. It will initiate on the next server check. On average, at vanilla speeds this took about 5 minutes for me. It is possible to type in a specific Purge Event and Wave Number as well. Sol_Aegis wrote a post that is still relevant if you want to test out specific Purge Events. The list given of course only includes the “old” Purge Events. A new list will need to be made after testlive moves over to live.
To summarize, to spawn say, an Exile wave, you would type:
Note: You will know if this command worked correctly if you look at your Purge Meter and notice it has emptied. If it has NOT emptied, try again as it sometimes it took me two attempts to get it to initiate.
This command will initiate the next wave in the sequence. If it’s on the final wave, the Purge event will end.
As advertised, this will end the Purge and the enemies will run away.
Want to become a god? Initiate slomo 10. This will speed everything up x10. This is especially helpful when you want the Purge to start without using the StartPlayerPurge command. Slomo 1 will return speeds to normal.
I had troubles getting the Purge to initiate prior to using any admin commands in Single Player. Once I got 1 Purge to start (using admin commands), then it seemed to open the flood gates. Alternatively, it could have just been more visible under slomo 10 conditions (I went through several day and night cycles and had numerous “natural” Purges).
That’s what I got for now, I’ll update the post with additional information as needed.