[✅API BACK-COMPAT] Fixed TileCondition functionality #177
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.
Problem:
TileCondition
(used byQueueTask.waitTile(Tile)
does not work correctly.Symptom:
Tile
properties that are used inTile.sameAs(Tile)
areval
thus cannot be changed. When aTile
was passed toTileCondition
assrc
. It seems as though the intention was forsrc
to update as a reference the properties update, but the properties will never update (because they areval
), thus renderingTileCondition
useless.Solution:
TileCondition
now takesPawn
andTile
(TileCondition(Pawn, Tile)
), and sincePawn.tile
is avar
it means that it changes asPawn.tile
changes, and it allowsTileCondition
to work as expected.QueueTask.waitTile(tile: Tile)
has been changed toQueueTask.waitTile(tile: Tile, pawn: Pawn = ctx as Pawn)
to keep backwards compatibility and preserve previous functionality while also giving the developer a bit more control over whichPawn
they want to reach the tile before continuing the logic.