Added "EXACT_" optional prefix to RTS's ON_CONDITION flag #578
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
dashodanger
added
needs testing
|
Looks good; appreciate the PR. I'll continue to update the changelog as these are folded in. |
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.
Added "EXACT_" optional prefix to RTS's ON_CONDITION flag.
Returns true only when value exactly matches the value in brackets (unlike the default "greater or equal").
Should be mostly useful with counters, but can also be used to trigger something when player has exactly 4 shells/30 health/50 armor/etc left.
Works with all numerable conditions: health, armour, ammo, power (seconds left), inventory and counter.
Examples:
ON_CONDITION EXACT_AMMO2(4)
ON_CONDITION EXACT_HEALTH(25)