Broken "decaying" memory in nexus

Bug report reference number: 2975553861

I've managed to enter and clear a one-health node without it collapsing. Here is the first stabilizer I came across:

clicking on that one sends you to the normal screen where you place a memory or open a portal back to the nexus.

The other stabilizers look like this:

clicking on these sends you the normal, place-a-memory screen.

Here's the memory in the Nexus view:


I could leave the memory without the area disappearing. I re-entered with the CTRL option, creating another instance and running the whole thing as normal, nothing amiss, disappeared after.

Hopefully this one isn't easily reproducible since it might be used to run juiced zones over and over.

Keep up the good work!

Kiwi

I think I've had a similar issue to this just prior to writing this. I had 2 spawned distant memories that I was able to redo over their supposed 1 charge. A memory that I manually placed oddly decayed while I was doing it while it had 3 charges. The memory says it still has 3 charges but I don't want to risk wasting charges. I don't suppose this might be some memory overflow issue or memories are inheriting/swapping charges?

The selected memory in the following picture decayed(the blue stuff was eating it inside the map itself) during the one time I ran it. It still says it has 3 charges.


This looks like a major bug as I don't know what will happen when I run my memories. I've only had this bug since that last patch.

Caught one of these bugged memories today.
Bug reference number: 1281875824

Distant Grim Sepulchre Memory
A spawned natural memory modifier node.
After running it and clicking the stabilizer that makes the whole physical map get consumed by the blue gunk, the memory stayed on the board, didn't change into the black hole image as decayed memories did, and the charge counter didn't go down.

The memory decayed after I ran it the second time.

The issue persists in that decay is not working correctly.