This is a plain-language record of what was just changed, fixed or switched on, and what is still outstanding. It exists because a lot of this work was queued and invisible — boards that looked live were quietly stale, and requests that had been answered were still showing as open.
The headline: when Remnants moved into the new faction shell, a dozen automated jobs kept reading the old faction. That faction has since been sold twice and now belongs to strangers. Every one of those jobs has been repointed.
Twelve automated jobs were still reading the faction Remnants left behind. They have all been pointed at the current one.
That old faction has changed hands twice and is now called something else entirely. Anything still watching it was reporting on strangers, not on us.
Status: all repointed and each one re-run by hand to confirm it works.
New members' progress had stopped updating. The job that reads the roster was failing on every single run, every five minutes, for two days.
It was trying to push a stranger's 13-member roster over our 85. A safety guard added earlier correctly refused — so nothing was corrupted, but nothing updated either.
Status: fixed. Roster now syncs, and steps members claim get confirmed automatically again.
Removed leftover logic that kept re-flagging the Discord and revives steps as failed, after those were deliberately made optional.
It computed a rejection on every run that the board then threw away — wasted work and confusing logs.
Status: done. Clean runs now.
The recruit tracking page was rebuilding itself every hour using the old faction, so it showed five recruits instead of the real number.
Status: rebuilt and live — 38 recruits, 34 at level 15+.
Members whose name ends in numbers could sign a guide and still show as unsigned. This had been "fixed" three times before and kept returning.
Each previous fix was applied to the finished page instead of the thing that generates it, so the hourly rebuild wiped the fix within the hour. This time it was fixed in the generator, so the rebuild carries it instead of erasing it.
Status: fixed at the source and confirmed live. Cannot silently revert now.
All three were being rebuilt only when somebody asked for it by name. All three were also still reading the old faction.
Status: all three rebuilt on the correct faction and now on an automatic daily schedule. Activity dossier and growth board refresh just after Torn rollover; armory ledger refreshes each morning.
On the private chat channels, simply reading the live stats bar deleted it. The same flaw could reset the message counter and cause NEXUS to repeat itself.
The endpoint treated a read request as a write with no content. Reading destroyed what it was reading.
Status: fixed on both channels. Reads now read. An empty reply is also refused instead of posting a blank message.
When Torn refused a request, NEXUS logged only "forbidden" and discarded Torn's actual explanation.
A game-wide outage, an expired key, and an inactive-account hold all looked identical in the logs. Diagnosing anything meant guessing.
Status: fixed, with tests so it stays fixed.
The council idea board said 15 items were outstanding. Nine had been delivered weeks ago — the guide rewrites, the support channel, the channel cleanup, the verification requirement.
There was no way to mark one finished except editing a data file by hand, so nobody ever did. Council was being shown a to-do list of work already done.
Status: nine closed, each checked against the live pages first. Board now reads 6 outstanding. Closing an item is now a one-line operation.
Mags pays for a premium stat-estimate service and offered her key so NEXUS can read accurate opponent battle stats. There was no safe way to hand it over, so she posted it in chat — where it sits in a log on the web host.
That service is outside the family, so this key cannot ride the normal key-vault promise, which says member keys are never passed to outside sites. It needed its own consent.
Status: a dedicated handover page is live with its own plain-English warning that the key leaves the family. It is closed by default and only opened when someone is actually handing a key over. Mags has the link.
Thirteen members opted in to get a direct message when leadership calls a push or a turtle. The system was built and tested six weeks ago but nothing was ever started, so none of them received anything.
They reacted to a sign-up post and have believed they were subscribed since late August. The opt-in list was collecting names into a void.
Status: running now, checked every minute. Leadership posts the call in the war channel and it goes out. Capped at six alerts an hour so a mistake cannot spam the roster.
Warns the war channel when an enemy flies into a country one of ours is standing in. It was running as a temporary process that dies whenever the machine restarts — and it had in fact already died, so nothing was watching.
Status: now on a permanent two-minute schedule. Confirmed idle and correct — it reports the war is 91 hours out and makes no calls until the bell.
Private progress dashboards for Remnants members had been dead since the faction move. Three are restored; two were retired because those members have left and their keys no longer work.
Status: restored. Also repointed the organised-crime seat recommendations, which were scoring members against the wrong faction's crime history.
The handover page now exists, but the copy she pasted in chat is still in that channel's history on the web host. It needs removing by hand.
Recommended: she creates a fresh single-purpose key through the new page and deletes the old one in Torn. Then the line in the log is worthless.
The opponent stat readings work and were used to rebuild every target sheet for the current war, but someone has to run it. It is not yet automatic, and nothing keeps a history to compare against.
Status: works on demand. Scheduling and history still to build.
Crysi asked NEXUS to replace the third-party faction bot. Still to build: automatic verification and roles for new arrivals, organised-crime delay warnings, retaliation alerts and chain alerts.
All four of her setup questions are answered, so these are ready to build — they are just not small jobs. Banking is likely no longer needed, since the old bot's banking was restored on a different key. Worth confirming before anyone builds it.
Status: designed, not built. Crysi has asked for a message as each one becomes testable.
Crysi asked NEXUS to notice and answer members complaining in Discord that it is not working. It currently only answers when spoken to directly.
The complaint that triggered this request tagged Crysi, not the bot, so no part of the system ever saw it. The same would happen again today.
On the private channels, messages can appear twice, and attaching a file gives no confirmation — which already caused the same file to be sent twice.
Status: both are in the page itself rather than the server, and both are still outstanding. Reported independently on two different channels.
Two images Crysi asked to be hidden back in September are unreachable to the public but still physically on the host. And she asked to choose her own passphrase — that one is waiting on her to pick one.
While checking this work, two pre-existing broken tests surfaced — one in the message-routing safety checks, one in the chain-risk alert logic.
Neither was caused by these changes, but the chain-risk one touches something members actually receive, so it is worth a look rather than a shrug.