Repository navigation
Make the protective feature configurable - #2489
Merged
Merged
Conversation
CarlosFdez
added this pull request to stack #2490
October 16, 2026 05:04
CarlosFdez
force-pushed
the
feature/protective
branch
from
October 16, 2026 05:05
5f2a7aa to
2cfaf9a
Compare
Contributor
|
Testing this, it works, but there is an undesireable thing. Might not really be easily fixeable, haven't really thought about it yet, but: This workflow:
|
Contributor
Author
|
Still waking up. I'll look into it. Good catch. |
CarlosFdez
force-pushed
the
feature/protective
branch
from
October 16, 2026 22:03
cc5bc49 to
3933ece
Compare
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.
Will add migration and SRD updates after this is confirmed good. This adds support for weapons with a protective value of 1.