Very minor outfit backend stuff #2850
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
About The Pull Request
This has zero gameplay impact, nor would anyone even notice this except if you pay attention to some admin messages.
If you skip defining a type for a child type of a child type, byond will infer that skipped type as being an exact copy of the original type, which in this case (subtypes of the Naked outfit in the admin equipment selection) leads to extremely minor, effectively unnoticable jank.
This properly defines outfit types that were skipped, which remain unpickable (due to being basetypes).
Why It's Good For The Game
Fix man good.
Testing Photographs and Procedure
Regrettably, this is tested.
Changelog
🆑
admin: Equipping the Naked outfit now equips the real Naked outfit.
/:cl: