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.
This corrects
ChronoshiftPower
to support multipleChronoshiftable
s (rather than crash by callingActor.Trait<Chronoshiftable>()
) as well as separating the return-to-origin timer by makingChronoshiftable
aPausableConditionalTrait
withPauseOnCondition
controlling the timer. The indicator bar will not show until the timer has started running. HavingRequiresCondition
control both eligibleChronoshiftable
forChronoshiftPower
and the return-to-origin timer can cause conflict when the actor is not supposed to be chronoshiftable but should automatically return to origin.Example Test:
This test requires being within 25 cells to try teleporting and within 12 cells to not explode; the teleportation range also pauses the return-to-origin timer. This patch also includes a
testing
SOURCE
for--update-mod
. Running--update-mod
in this patch will create extraPauseOnCondition
since that is a new field forChronoshiftable
.Apply the follwing patch which is also committed to https://github.com/atlimit8/OpenRA/tree/fix-multiple-Chronoshiftables-testing: