Apocalypse impending/CTE email notifications

[SherpDaWerp]

Both numbers can always be found in the FAQ; they're always correct so you don't need to ask admin.

https://www.nationstates.net/page=faq#technical

Currently it's 49 days for regular nations and 81 days for vacation mode. These numbers will continue to slowly decrease over time.

The FAQ currently says that nations get deleted after 0 days of inactivity, so I feel like the FAQ isn't always correct.

Apologies, this was my error - it's corrected now. [v]'s point was more that the FAQ pulls the same constant as the CTE timer does, so whatever the FAQ says is what the CTE timer will also be using.

[Dengist China]

Both numbers can always be found in the FAQ; they're always correct so you don't need to ask admin.

https://www.nationstates.net/page=faq#technical

Currently it's 49 days for regular nations and 81 days for vacation mode. These numbers will continue to slowly decrease over time.

The FAQ currently says that nations get deleted after 0 days of inactivity, so I feel like the FAQ isn't always correct.

Nah mate, it's correct. The second you close your computer, your nation will self-delete.

[Nolrem]

Apologies, this was my error - it's corrected now.

Out of sheer curiosity was the CTE timer using 0 days inactive as its standard earlier, and if it was is it possible to tell if anyone lost their nation as a result of being inactive for 0 days?

[SherpDaWerp]

Apologies, this was my error - it's corrected now.

Out of sheer curiosity was the CTE timer using 0 days inactive as its standard earlier, and if it was is it possible to tell if anyone lost their nation as a result of being inactive for 0 days?

I'm not aware of any nations CTE'ing due to this, as nations do not (naturally) CTE except during update, and based on the various times of things starting and ending, it is impossible for update to have "read" the incorrect value.

[Durmengrad Prime]

Both numbers can always be found in the FAQ; they're always correct so you don't need to ask admin.

https://www.nationstates.net/page=faq#technical

Currently it's 49 days for regular nations and 81 days for vacation mode. These numbers will continue to slowly decrease over time.

It seems like today, they were simply sent straight back to normal instead of continuing to slowly decrease. As a result, there are a milluon nations CTEing and regions that are supposed to update at 30 minutes after update start updating at 2 hours and 30 minutes after update start.

Will major end before minor starts? :thinking:

[Anakona]

Both numbers can always be found in the FAQ; they're always correct so you don't need to ask admin.

https://www.nationstates.net/page=faq#technical

Currently it's 49 days for regular nations and 81 days for vacation mode. These numbers will continue to slowly decrease over time.

The FAQ currently says that nations get deleted after 0 days of inactivity, so I feel like the FAQ isn't always correct.

Considering that about 10 thousand nations have expired in an update that still has yet to end, something tells me they modified something very recently.

[[violet]]

Oof, we accidentally reset the timer and didn't notice before update. So we have forcibly jumped back to the default. Apologies for the inconvenience.

[Varanius]

“Oof”

[Gagium]

[Anakona]

As compensation, we deserve a "I Survived the Not-All-That-Great Accidental CTE Timer Reset of 2026" badge.

[EA Corporations]

The update seems to have gotten stuck at Lazarus for almost the past hour; I wonder what's the longest a region has ever taken to update.

[Flanderlion]

Oof, we accidentally reset the timer and didn't notice before update. So we have forcibly jumped back to the default. Apologies for the inconvenience.

So this means we're back to normal? I think that's probably the best way to do it for future incidents - extension for a bit, but then back to normal suddenly rather than having the protracted process of returning it.

[Rhaza]

Oof, we accidentally reset the timer and didn't notice before update. So we have forcibly jumped back to the default. Apologies for the inconvenience.

"Oof" as like 10% of everyone's WAs cry out in pain before being extinguished

[Durmengrad Prime]

Oof, we accidentally reset the timer and didn't notice before update. So we have forcibly jumped back to the default. Apologies for the inconvenience.

So this means we're back to normal? I think that's probably the best way to do it for future incidents - extension for a bit, but then back to normal suddenly rather than having the protracted process of returning it.

It causes a 10 hours long update though. IMO a better way would be the times going down one day every day until it's back to normal.

[-Astoria-]

So this means we're back to normal? I think that's probably the best way to do it for future incidents - extension for a bit, but then back to normal suddenly rather than having the protracted process of returning it.

It causes a 10 hours long update though. IMO a better way would be the times going down one day every day until it's back to normal.

Like with one of those [blank]-day tickers?

[Ci Arovannea]

>oopsy daisy
>destroys a tenth of ns

classic admin move

[Emodea]

[violet] why

[EA Corporations]

The world population fell a staggering 35,000 in one update, including 6,000 from Chicken Overlords alone.

[Kractero]

The world population fell a staggering 35,000 in one update, including 6,000 from Chicken Overlords alone.

Do not worry, the core service that Chicken Overlords provides by gatekeeping stats, slowing down update, and being useless is coming back online with the refounding of the Wombles.

[Dengist China]

The world population fell a staggering 35,000 in one update, including 6,000 from Chicken Overlords alone.

Do not worry, the core service that Chicken Overlords provides by gatekeeping stats, slowing down update, and being useless is coming back online with the refounding of the Wombles.

God forbid that these exceptionally valuable services are kept from the public! We must Make Nationstates Slow Again!

joking, obviously. I never liked Chicken Overlords, their ROs have some interesting histories

[Rulapanga]

This was frustrating. It looks like the Vacation mode and CTE email notifications were turned off for most of my nations, resulting in a few CTEs. I wish it had been made known that a reset would do that so I could have been proactive and avoided this situation now.

EDIT: Or the CTE process was sped up also? Not clear on what happened, but it was not good.
I definitely lost all my safeguards to keep my nations from CTEing, short of manually logging in to check on them all and fix their settings.

[Orcuo]

This is the equivalent of the president accidentally pressing the big red button and wiping out the entire French countryside.

[Durmengrad Prime]

This was frustrating. It looks like the Vacation mode and CTE email notifications were turned off for most of my nations, resulting in a few CTEs. I wish it had been made known that a reset would do that so I could have been proactive and avoided this situation now.

EDIT: Or the CTE process was sped up also? Not clear on what happened, but it was not good.
I definitely lost all my safeguards to keep my nations from CTEing, short of manually logging in to check on them all and fix their settings.

What happened was an unplanned accident. Admins didn't notice that they had reset the times until update and CTEing had already started.

[Ciconia Nigra]

This was frustrating. It looks like the Vacation mode and CTE email notifications were turned off for most of my nations, resulting in a few CTEs. I wish it had been made known that a reset would do that so I could have been proactive and avoided this situation now.

EDIT: Or the CTE process was sped up also? Not clear on what happened, but it was not good.
I definitely lost all my safeguards to keep my nations from CTEing, short of manually logging in to check on them all and fix their settings.

Same here.

This took out about 85 of my puppets in all.

I may not be super-active with those puppets, but having this happen TWICE in less than two months is getting beyond frustrating. It´s demotivating and angering.

[Dragorge]

Oof, we accidentally reset the timer and didn't notice before update. So we have forcibly jumped back to the default. Apologies for the inconvenience.

So this means we're back to normal? I think that's probably the best way to do it for future incidents - extension for a bit, but then back to normal suddenly rather than having the protracted process of returning it.

How about we try to avoid accidents, and not compound them by more OOFs?