I think it might just be a generic risk warning? As in, if anchoring was disabled, there’d be no chance to input an unstable memory. But opening that door always allows for shady memories to get through, no matter how small that chance is, so the chance would increase compared to if the engine was offline?
@7101334 looks like some GHub submissions are rolling their way into anchoring, its awesome to see! Congrats y’all!
The memory tracker sheet was recently updated to accommodate the new format by the way, so if our awesome GHub Operators could help accumulate entries to mark and immortalize submissions here, that’d be super appreciated!
@ThatBomberBoi Here’s what I submitted ![]()
Thanks so much for sending over all of these! I’ll get em up on the tracker now, should help point down future anchors a lot! ![]()
I sent in a very obviously allusion-bait esque entry for 16/06/1616 as a test to see how ridiculous the anchored memories can be.
On the highly improbable chance this anchors, please remember that this entry is Operator-Submitted, to avoid any potential heart-attacks ![]()
lol you’re trying to break it aren’t you
Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should.
Can’t stop the CSD member inside of me from trying to science things out ![]()
System is barely holding together, and you already want to break it again
![]()
Have time today to submit something to the Memory Timestamps. Will be home tomorrow and back to my usual presence amongst Operators. Been lots of fun checking in every few hours and seeing all the memories submitted <3
Operator:
ToddUmptious/ETARC_Atlas-CSD - Window 4013
Timestamp:
1386463680
Memory Title:
Every Memory Procedural
Memory Value:
A vision for a Shared Dream is unveiled
Memory Quote:
My friends and I were still gripped with Minecraft fever and excited to see where procedural generation could take small indie studios and developers with the future of gaming. We dreamed of endless worlds not bound by a single atmosphere, the possibility of breaching them and exploring the depths of space. We had witnessed many false and early starts into this endeavour that never truly materialised. We thought it would be a decade off before technology would match our dreams. On December 8th, in the early hours of the AM, broadcast into our future from the past that was LA on December 7th, we learned how wrong we were. The dream was actually right around the corner. The Sky would no longer be the limit for No Man.
Memory Link:
I resubmitted a memory about XxioGames and his contribution to No Man’s Sky community in the new format based on developments in this thread.
Some new memories anchored.
The sheet says MAINFAM-53 but I believe this one was @ThatBomberBoi
This one says mainfam-17 which I gather is @YourBasicMaths
Another from @ThatBomberBoi
Seems they are coming through in sequence of submission from the good science being performed over on Discord.
Edit:
Still following the sequence now with this next one from @fort_wort_wort …
Next one is from Selfie Gek. Sean Sean’s Sean mod <3 A legendary moment in NMS Community history for sure.
@vector_cmdr submitted two for deleted blocs between this and the previous one, so it looks like those may definitely be completely irreplaceable as Archie suggested
More good Science-ing from Citizens on display.
Next one up is from @sheralmyst . Next step is to get your Daughter a Prime and turn them into an operator like the rest of us wasps ![]()
Not sure if it’s still going in sequence or not but jumped back a few entries on the sheet for this next one from @melanon68
Next one up is from @Rinha <3 Eerily relevant to recent ARG developments
@Selfie-Gek finally got Bacon on the Board and their LNF Meme History with the Holy Bacon Empire <3
So cool for everyone! ![]()
Thought we were done for today with such a huge gap, but we got another one ![]()
Memory of NMSE by @vector_cmdr
Had a go at submitting a personal memory for 2006, I tried adding it to the google sheet, but may have muddled things a bit in the title and value fields.















