Any statement regarding the glitches and early cutoff time for last week's CGs?

Last night, the entire playerbase reported an extended period of time wherein no NPCs spawned in any Conflict Zones related to the pair of combat CGs that just ended. Furthermore, maintenance started an hour earlier than normal, effectively ending the CG right then and there despite it having an hour to go.

These issues dashed the hopes of a number of CMDRs hoping to acquire the unique rewards offered by the anti-Azimuth CG, including myself, who only had time late last night to finish them up. Time I had allocated more than enough of to finish before the prescribed ending time... had everything not gone wrong!

Can we expect any dev statement on the matter or any address of this at all, or are we gonna be sitting and spinning on this one? Can anyone else here vouch for what happened last night?
 
What time zone are you in? Daylight savings just ended in the US, so you need to adjust your conversion to game time
This is true. I'm in the eastern US and DST did turn over recently. But then, why did the maintenance time "shift" an hour back while the CG's listed end time did not? Maintenance started at the point in time when the CG was listed as having an hour remaining, thereby rendering that final hour of time invalid. No matter how you look at it, either maintenance started too soon or they effed up on the CG timer.
 
FDev uses GMT/UTC for the reason that it never changes time...
The move to 3 PM GMT start time means that for this CG you are having less time to take part now with the 3PM GMT start
You may have noticed that the forum topics actualy had the correct end time of 6AM GMT/UTC still not the 8AM end time that is displayed in the broken API timer..
The CG was meant to end at 6 AM GMT, The API timer was broken but Fdev decided or had to leave it alone and not adjust it so the CG running beyond 6am GMT was a bonus due to the API timer being set wrong..
10th November 3308 @ 06:00 UTC
So those wanting to play after 6AM GMT were not meant to be able to as the API time sent to sites like inara was actualy wrong but not fixed...
Then the server is down at 7am GMT/UTC but even it the server was to go down one hour early that would still be the correct time of 6 AM GMT...

So yes Fdev need to confirm that the end timer will work correctly next time but the end time of 8AM was allready stated as wrong on the forum topics...
 
Last edited:
So yes Fdev need to confirm that the end timer will work correctly next time but the end time of 8AM was allready stated as wrong on the forum topics...
I wouldn't get my hopes up that FDev will correct the expiry timestamp any time soon:
Titleexpiry timestamp
Protect Azimuth Deliveries from Anarchists2022-11-10 08:00:00
Disrupt Azimuth's Resource Campaign2022-11-10 08:00:00
Azimuth To Expand Operational Assets2022-11-10 08:00:00
Governor Chase's Xeno-Peace Megaship2022-10-27 07:00:00
Protect Delivery Transports in Andavandul2022-10-27 07:00:00
Operation Tyndareus Reacts to Thargoid Fleet2022-10-13 07:00:00
Defend the True Chapter Cultists2022-10-06 07:00:00
Seize the Far God Cult Megaship2022-10-06 07:00:00
Aisling Duval Charity Fundraiser2022-09-29 07:00:00
Protecting Deliveries in Cemiess2022-09-29 07:00:00
Defend Tekkeitjal from Thargoid Attack2022-09-22 07:00:00
Defend 42 n Persei from Thargoid Attack2022-09-22 07:00:00
Defend Chun Pindit from Thargoid Attack2022-09-22 07:00:00
 
Last night, the entire playerbase reported an extended period of time wherein no NPCs spawned in any Conflict Zones related to the pair of combat CGs that just ended. Furthermore, maintenance started an hour earlier than normal, effectively ending the CG right then and there despite it having an hour to go.

First part seems to be an Odyssey issue, as I was in Horizons and played the CZs right up to 10 min before server shutdown, then logged back in 25 min after shutdown and tried to accumulate enough bonds right up to the end at 0800 UTC.
The falsely set CG end times from the last few weeks (0700, now even 0800 UTC) are another issue altogether... normally they should be 0600 UTC, 1 hour before shutdown tick.

Second part: server shutdown for maintenance always happens at the usual (and never-changing) tick time of 0700 UTC, which is prominently displayed in-game on main cockpit interface. Daylight saving time change in any part of the world (including UK itself), is the issue of the users, not the company, especially if it is the usual deliverence (never was otherwise in all the three years I now play this game).

[Edit:] Because the cargo CG succeded, at least anybody will be able to obtain Mbooni permit in std game and buy the EnhPlasmaChargers there with mats, whereas the MCs are still unique. [/Edit]

Personal fun facts on the first part: I was top10% Anti-Azimuth CZ CG, and top100% Pro-Azimuth CZ CG (prviously alread handed in those 243k bond accidentially gained for Azimuth). Slighly dropped below threshold and slid back to top25% Anti-Azimuth as expected, and decided to try top75% pro-Azimuth anyway in the final hours. I dutifully "amassed" 5M about 0650 UTC and rushed back, but as many of you experienced before, accidentially to the station instead of megaship, so it didn't count for the CZ. After the tick I logged back in 0725 UTC and tried to get 5MCr again in remaining 35 min, managed only to get 2MCr anyway, went to Musashi this time, but docked 5 sec too late... So much for betraying my or my CMDR's convictions ;)
BTW: when arriving first in that system with my Explorer, I handed in 1t of Cobalt even against my in-game convictions so any participant have easier top75% or any other CG target they may have. This is a reminder or plea to deliver at least 1 unit of whatever (cargo, data, bounty, bond, ...) to any CG even if you are not interested in their rewards or outcome, just to help those who are.
 
Last edited:
Back
Top Bottom