Forums » General
Confirmation of Helios persistent event?
This now includes two new Persistent Events that are spawning on Saturday (Feb 22nd) for the first time. One in Helios a little after 1pm Central, and the other in Ukari around 5pm Central, after which spawns will become randomized.
It's been about an hour and 15 minutes so far. Can you confirm the Helios persistent event has been implemented or if it's been cleared by a player? Myself and others have yet to see the blinking square on the nav map to indicate the event may be spawning soon, nor have we encountered any unique bots.
Thanks!
It's been about an hour and 15 minutes so far. Can you confirm the Helios persistent event has been implemented or if it's been cleared by a player? Myself and others have yet to see the blinking square on the nav map to indicate the event may be spawning soon, nor have we encountered any unique bots.
Thanks!
My apologies, but apparently there have been problems with the Events not spawning at the expected times. This is either something not quite right in the Event system, or I misunderstood how it was supposed to work. In either case, they didn't show up properly, based on the times I put in the Newsletter.
I did manually spawn the second Event at 5pm, and we played through that one successfully. I wasn't around earlier for the 1pm Event.
We do know the spawning system works in general, as my OG "Test Event" (single mining bot you can attack) has been running for many months in production. But, something may be off on the timing or repeat-rate system.
The overall Persistent Event mechanism is still in active development, so please pardon some rough patches while we figure out various issues. It should be pretty cool, once we sort everything out.
I did manually spawn the second Event at 5pm, and we played through that one successfully. I wasn't around earlier for the 1pm Event.
We do know the spawning system works in general, as my OG "Test Event" (single mining bot you can attack) has been running for many months in production. But, something may be off on the timing or repeat-rate system.
The overall Persistent Event mechanism is still in active development, so please pardon some rough patches while we figure out various issues. It should be pretty cool, once we sort everything out.
Apparently, while the Persistent Event scheduling was internally documented and stated to be in UTC, it was actually in CST. No one realized that until this went awry. So.. now we know.