I aided a player on our server two nights ago with a Yeti Purge. After simulating it on my vanilla PvP server, I find the site doesn’t seem to matter. You’ve built in a very approachable, and very stable/flat location, same as them.
Player R had been watching his meter so he knew he was going to get it. With a clan name starting in C, it was assured to happen. 2 minutes past Purge time, I asked him to check his Event Log. It said a purge had started.
Here’s where he deviated from what I did on my private server: he logged out, then stayed off until well past what would’ve been the 10-minute warning. When he came back, it said “Purge ended.” His bar was still full. We waited another 10 minutes, during which time I visited the base of another purge-eligible player, Player S, who was offline.
Player R reported to me the banner was on his screen, Yeti purge. He got the two waves and it was defeated. Player S later reported his Event Log showed a purge had begun and ended in rapid succession.
TLDR: this purge, if bugged, will try to skip to the next eligible clan. This can place it in a state of bouncing between you two or more, such that you’re getting start and end, regularly. My advice is to watch your Event Log. If it reports the purge has started, yet there’s no banner or map marker, log out and back in quickly.
I haven’t published that Purge interaction yet(i), but I DO have a recent Locust Purge that was resolved with a relog.