3. Writing to inactive segments

Writing to inactive segments


  • What's devs standpoint on writing to inactive segments?

    As I understand from documentation, I'm supposed to activate up to 10 segments so I can read from them and they'll automatically be saved at the end of the tick. However the way it is implemented makes it possible to:

    1. Write to a segment without activating it in previous tick. Up to 10 segments can be saved.
    2. Activate 10 segments, read whatever is stored in them, then for (let key in RawMemory.segments) delete RawMemory.segments[key]; and then write to up to 10 different segments.

    I see it as an unharmful undocumented behaviour, similar to memhack, but it also could be considered an exploit.