[MIRROR] Adds a var to determine if anomaly-locked MOD modules can have cores uninstalled #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mirrored on Skyrat: Skyrat-SS13/Skyrat-tg#24556
Original PR: tgstation/tgstation#79171
About The Pull Request
Title. The
core_removable
var on theanomaly_locked
MOD module typepath now determines if a core can be removed post-installation. This isn't used anywhere, at the moment, but could be used to, say, prevent a space-loot MOD module's core from being removed for other purposes.Adds
/prebuilt/locked
subtypes to the currently present and defined anomaly-locked modules, which have this var enabled, and puts them nowhere else.Why It's Good For The Game
Another way to control distribution of anomaly cores - making people commit to having a limited-supply item installed in a thing, or something like that.
For habitual Github-readers, this is unused, at the moment, just something that could be used by another coder down the line or something.
Changelog
🆑 Hatterhat
add: Anomaly-locked MODsuit modules can now be varedited to have unremovable cores, or can be spawned with this functionality by using the /prebuilt/locked subtype.
/:cl: