feat: re implement onMovementStep to be able to affect actor movement #455
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 a follow up from #276 which had certain valid criticism. Read the criticism on that in order to better make sense of the approach taken here.
Also note that the current
onMovementStepin MSU is completely useless and in-fact misleading. So this PR should be considered afixas well (or perhaps primarily a fix).This makes the function actually useful. It allows skills to stop an actor's movement at a particular tile based on conditions defined in the skill's
onMovementStepfunction. Note that onMovementStep is called before moving to a tile. As long as all skills' onMovementStep returns true or null, the movement is valid. Otherwise:Note: Only the first skill that returns a movement stopping condition is considered. Therefore, skill order is important.