Claim private command not working as expected #209
Merged
Conversation
This file contains 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
fix on = true, off = false.
|
I don't think this logic is right, is it? If the user enters /claimprivate true, it should make the claim private and trigger the event as is the current behaviour. Also inverting the Boolean there will double invert the toggle check. Is the current logic really not correct? |
|
The logic wasn't right. If you did /claimprivate on |
|
Could you maybe take a look at it again? 👍 |
WiIIiam278
approved these changes
Oct 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Old scenario
/claimprivate on = false
/claimprivate off = true
/claimprivate = always true
New scenario
/claimprivate on = true
/claimprivate off = false
/claimprivate = toggle