<![CDATA[[Request] Nukes destroy .store contents of ruins/tombstones but not the objects.]]>Right now it's an odd edge case that you can't rely on ruins/tombstones because technically they can be deleted with a nuke. It would be better if the .store of them was cleared but the objects left behind.

]]>http://screeps.com/forum/topic/2847/request-nukes-destroy-store-contents-of-ruins-tombstones-but-not-the-objectsRSS for NodeMon, 12 Oct 2026 12:03:09 GMTMon, 28 Oct 2019 16:50:13 GMT60<![CDATA[Reply to [Request] Nukes destroy .store contents of ruins/tombstones but not the objects. on Invalid Date]]>Right now it's an odd edge case that you can't rely on ruins/tombstones because technically they can be deleted with a nuke. It would be better if the .store of them was cleared but the objects left behind.

]]>http://screeps.com/forum/post/14386http://screeps.com/forum/post/14386Invalid Date<![CDATA[Reply to [Request] Nukes destroy .store contents of ruins/tombstones but not the objects. on Invalid Date]]>My particular corner case. It would be nice if I could scan a room for Ruins every ~500 ticks to rebuild any lost structures. It would make my auto building code simpler. I can assume a room's Structures and Ruins completely describes my base.

Nukes erasing Ruins makes this not pratical and I am forced to track my base layout in Memory.

]]>http://screeps.com/forum/post/14387http://screeps.com/forum/post/14387Invalid Date<![CDATA[Reply to [Request] Nukes destroy .store contents of ruins/tombstones but not the objects. on Invalid Date]]>++ to all this. Ruins are a super useful input to my auto build/repair system, but they're significantly less useful if their timeToDecay can't be relied upon.

]]>http://screeps.com/forum/post/14407http://screeps.com/forum/post/14407Invalid Date