Skip to content

Borg Storage Module Expands Itself #1993

@Ray3424

Description

@Ray3424

What happened?

When placed in storage (whether apartment storage specifically or any form of saved storage), cyborg storage modules page themselves between uses, gaining an additional inventory space that is empty. Each time this is done, the paging appears to increment by 1.

This may actually occur any time a module is reinstalled, but I've mostly noticed it with storage modules I've used for a long time.

This causes the original storage space to be pushed to the second use of the module (install module, activate module, deactivate module, activate module) but the first usage still has a totally separate and complete storage space.

I'm unclear if this has more specific triggers; I usually have it happen after respawning at a future time and installing the module on a 'new' cyborg. I've seen other cyborgs describing this in OOC however, so I don't believe it's particularly isolated or difficult to reproduce, and it's happened to me for several shifts.

What should have happened?

The cyborg storage module should have one page only and not require multiple activations to get to the saved inventory.

Steps to reproduce

  1. Spawn as a cyborg.
  2. Install a storage module, place an item inside as a point of reference.
  3. Uninstall the storage module and save it in a relevant item-saving container.
  4. Unload and re-load the container.
  5. Reinstall the storage module.
  6. The storage module will now have a blank inventory, and can be deactivated and reactivated to get to the original inventory. This can actually occur more than once; typically I dispose of storage modules once they hit three pages since I'm not exploiting and getting to my original inventory is annoying.

Severity

Moderate (feature partially broken, workaround exists)

Game version / build

N/A - Live, do not have a local instance to test on.

Server / Round ID / Timestamp

N/A

Relevant logs / screenshots

N/A

Submission checklist

  • I have searched for existing issues and this is not a duplicate
  • I can reproduce this bug consistently with the steps above
  • I understand that bug fixes will be tested locally before PR and tested again before merge

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions