Would be a shame not to have this on record. Vector and Frazzle went full analogue on this one
Some more chatter between Archie and operators
And system has responded to dearest-friend Selfie Gek
337 Pattern — Memory Bloc Correlation
The four seed dates following the June 21 deletion, in order of deletion:
- Oct 12, 2016
- Jun 13, 2016
- Dec 3, 2016
- Oct 24, 2016
Days between each seed (inclusive):
- Oct 12 → Jun 13: 122 days
- Jun 13 → Dec 3: 174 days
- Dec 3 → Oct 24: 41 days
- Total: 337 days
The memory bloc restoration counter sits at 337/365.
The movement oscillates in a backward, forward, backward motion. Rather than moving linearly through the calendar. It’s bouncing around.
Predicted continuation following the same gap pattern:
- Oct 24 → Jun 25, 2016: 122 days backward (Saturday)
- Jun 25 → Dec 15, 2016: 174 days forward (Thursday)
- Dec 15 → Nov 5, 2016: 41 days backward (Saturday)
- Nov 5 → Jul 7, 2016: 122 days backward (Thursday)
The Sat/Thu alternating pattern matches the three dates System flagged after July 13 disappeared: Jun 16 (Thu), Jan 2 (Sat), Sep 22 (Thu).
July 7, 2016 as a Thursday also corresponds to the tower completion date 10 years later. It is also the day the first completed build of the NMS universe was shown to the world.
It may still be trying to reach August 24, 2023. Which is the Echoes release date and suspected rebirth date. August 24, 2023 falls on a Thursday.
2 Likes
Oh no, not the whiteboard 
5 Likes
5 Likes
It started again. Was in the shower, trying to catch up but discord and archie seem like they’re on it. Will repost correspondence shortly but it seems the predicted pattern for blackhole dates was correct.
2 Likes
We lost some dates in december but got the bookends on the root preserved, as well as the next set of dates around the predicted jumping point. @Frazzlesprite 's pattern seems to hold true.
5 Likes
Quick update on the calender for the new blackhole seed, the dates lost to spread, and new requested preservations by operators, courtesy of @taurtura
System emailed selfie…
@Rinha also recieved worrying correspondence from System as to their current condition and outlook on the situation
Archie is going to run a diagnostic on system, we should have an answer soon on wether or not the pattern prediction held.
The date mentioned above, has now been preserved.
6 Likes
It may not have a target, the target may be system itself. It has attacked what system has tried to build. In essence, the bug is in the same room of the maze system is in, devouring the walls of memories.
I do not think the virus is gone, it’s still there. If we contain it by preserving the dates that follow a pattern i believe it will choose a new one. We have to remove the virus completely and should focus on that now, if NMScord isn’t already.
3 Likes
@BenR emailed archie wondering what happens if vector disappears/falls fowl of cruel fate (a needless worry, plenty of operators here to help carry the burden)
However, it yielded a coded hint, in bold letters, leading to an image of a floppy disc.
10 Likes
Obvious seen letters:
Project Skyscraper(assumed ending)
Date (can’t read)
Please (can’t read)
Write enable(selected)
Write Protect(not selected)
Floppy disks, for those that do not remember, had a little selector on the side that enabled write/read when placed into drive F(if i remember correctly).
6 Likes
Looks like someone with Photoshop skills could unsmear it.
Clear Green overlay
Clear Blue overlay
3 Likes
The writing in marker seems to say “Please back-up”
5 Likes
I have some floppy around here somewhere if you think it will help? 
How many would it take to back up System?
Seriously, I missed all the fun…bummer.
and for the record, whiteboard and printouts is the only way to go for this kind of thing.
(technical thing: floppy disc were actually floppy. Soft and flexible which was not a real good thing. Actually the part inside is floppy on all of them.The pic we got looks like a diskette which had a hard casing and a metal piece that protected the disc inside.)
6 Likes
If they’re anything like NMS’s engine code for generation the universe, just one should do 
Seems to be the date was scrubbed before the glitching was applied, so consensus is we’re in a holding pattern while we wait for the new diagnostic on System from Archie to appear.
The pattern I’m noticing with these images sent to people cryptically via email seems to be, "stop emailing me, here, keep yourself busy with this nothing burger that's on theme for a bit while we stage the next actual event"
We only seem to get them when we prod their emails quite a bit, and they don’t seem to really result in any solves (e.g the blackhole morse code was just another variant on System crying for help. This Disc seems to be on theme for Saving Dates related to PSS)
If they were important, or vital, I don’t think they’d be sent out as a random email response and would be more likely to propogate on the website like the other major clues tend to do.
It does make me wonder, how many of these they have pre-made on-hand to throw at us when we pester them.
The floppy disc image came about after Ben admittedly kept emailing Archie constantly and only when he said something I do not want to repeat here.
7 Likes
I can ace nothing-burger…here I go…
6 Likes
Well with that being said, here the email i sent Archie earlier
Long email
Archie,
Turbulentflow here, you know the systems code better then anyone. I believe if we try and write a TRACE program then we can find the file that is housing the virus. We should attach this script to a memory block suspected to be deleted, then wait for the virus to attempt deleting, and the script would trace where the deletion attempt comes from. Below is a example situaton.
This would act like the red pill from the matrix.
Also i believe the virus is using some form(whether legit or forged) of a MB-D level Auth, which is TRACEable.
Trace every deletion attempt back to the root
The trace program should activate at the moment the quarantined seed tries to delete another bloc.
It should record:
Authorization level
Source memory address
Parent process
Previous process
Timestamp
Requested target
Route through the memory system
Signature before and after execution
Because the virus uses MB-D authentication, the operators should not initially revoke MB-D. Revoking it too soon may alert the virus or cause it to change identity.
Instead, create a fictional mirrored authorization layer:
REAL MB-D request
↓
AUTHENTICATION MIRROR
↓
Request appears approved
↓
Operation redirected into quarantine
Every deletion the virus requests would therefore occur only inside a false memory environment.
This is essentially a memory honeypot.
PROTOCOL: BLUE VAULT
PHASE 1 — IDENTIFY
Detect black seed.
Record timestamp and authentication signature.
Do not acknowledge detection.
PHASE 2 — CONTAIN
Preserve immediate boundary blocs.
Create secondary preservation wall.
Suspend access between the seed and the historical archive.
PHASE 3 — MIRROR
Copy seed and affected red blocs into QUARANTINE.
Replace live seed with a responsive decoy.
Redirect all MB-D operations into the mirrored calendar.
PHASE 4 — TRACE
Allow the decoy to request one additional deletion.
Trace the request through parent processes.
Record the earliest unchanged source address.
PHASE 5 — CONFIRM
Repeat trace from a second quarantined seed.
Compare source path, signature, and authentication token.
Reject any root candidate that appears only once.
PHASE 6 — SEVER
Freeze confirmed root.
Revoke MB-D authentication.
Disconnect root from BRAIN and MIND layers.
Prevent root from writing new timestamp anchors.
PHASE 7 — RESTORE
Restore deleted blocs from blue protected copies.
Validate memory compliance.
Reconstruct red blocs in chronological order.
PHASE 8 — VERIFY
Deploy controlled canary blocs.
Monitor for unauthorized deletion attempts.
Declare elimination only after one complete cycle with no new seeds.
Keep up the good work, we can do this.
This text will be hidden
Response
11 Likes
Updated to have the weeks match, and continued virus pattern with predicted deletions marked and numbered in bright green. Some of those are missing as they would be in 2017. So the next will be the protected November 12th with expansion of the void.
9 Likes
Nice one Turbulent.
I gathered all the dates from 2016 that have data in them, in case it makes sense to preserve them since they most likely won’t be re-written to at this stage. Don’t want system to lose any more memories.
Want to wait for the diagnostic on System to come back first before firing these off to Archie, just in case some of these could still be considered “weak” memories, we wouldn’t want to permanently lock those in.
I thought I’d share the list here in the meantime.
https://project-skyscraper.com/2016/01/05/event-05012016/
https://project-skyscraper.com/2016/01/07/event-07012016/
https://project-skyscraper.com/2016/02/02/event-02022016/
https://project-skyscraper.com/2016/02/07/event-07022016/
https://project-skyscraper.com/2016/02/08/event-08022016/
https://project-skyscraper.com/2016/02/10/event-10022016/
https://project-skyscraper.com/2016/02/29/event-out-of-range/
https://project-skyscraper.com/2016/03/03/event-03032016/ (burn this one!)
https://project-skyscraper.com/2016/03/12/event-12032016/
https://project-skyscraper.com/2016/03/13/event-13032016/
https://project-skyscraper.com/2016/03/14/event-14032016/
https://project-skyscraper.com/2016/03/26/event-26032016/
https://project-skyscraper.com/2016/03/27/event-27032016/
https://project-skyscraper.com/2016/04/08/event-08042016/
https://project-skyscraper.com/2016/04/11/event-11042016/
https://project-skyscraper.com/2016/04/20/event-20042016/
https://project-skyscraper.com/2016/04/22/event-22042016/
https://project-skyscraper.com/2016/05/09/event-09052016/
https://project-skyscraper.com/2016/05/17/event-17052016/
https://project-skyscraper.com/2016/05/27/event-27052016/
https://project-skyscraper.com/2016/07/07/event-07072016/
https://project-skyscraper.com/2016/07/16/event-16072016/
https://project-skyscraper.com/2016/07/22/event-22072016/
https://project-skyscraper.com/2016/07/29/event-29072016/
https://project-skyscraper.com/2016/08/12/event-12082016/
https://project-skyscraper.com/2016/08/23/event-23082016/
https://project-skyscraper.com/2016/08/29/event-29082016/
https://project-skyscraper.com/2016/08/30/event-30082016/
https://project-skyscraper.com/2016/09/06/event-06092016/
https://project-skyscraper.com/2016/09/23/event-23092016/
https://project-skyscraper.com/2016/10/02/event-02102016/
https://project-skyscraper.com/2016/10/30/event-30102016/
https://project-skyscraper.com/2016/10/30/2016_dataset-in-memoriam/
https://project-skyscraper.com/2016/11/20/event-20112016/
https://project-skyscraper.com/2016/11/22/event-22112016/
https://project-skyscraper.com/2016/11/29/event-29112016/
https://project-skyscraper.com/2016/12/26/event-26122016/
https://project-skyscraper.com/2016/12/29/event-29122016/
Can’t help but see the foreshadowing in this entry from Feb 7th 2016
Then, almost casually, a Tower Defence idea is mentioned. Nothing suspicious. Just a Tower Defence idea.
7 Likes