Conversation
- Consolidate position calculation utilities and introduce a configurable prediction delay via `ai_route_position_prediction_delay`. - Implement a wait mechanism in the attack loop for targets predicted to enter range or line-of-sight shortly. - Refine meeting position calculations with improved reachability lookups and support for `route_avoidWalls`. - Fix boundary conditions in `get_lockMap_cell` to prevent selecting cells on the map edge. - Clean up redundant path initialization when loading maps or using skills.
- Add specific avoidance configuration for monster 1368 and update portal penalty settings. - Reduce AI route adjustment timeouts for more frequent path updates. - Fine-tune position prediction, target wait delays, and meeting position reachability lookups.
alisonrag
approved these changes
Mar 28, 2026
alisonrag
approved these changes
Mar 28, 2026
This file contains hidden or 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
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.
Ready for testing / review
Reworked my old plugin to use config.txt key, dynamic route_step for obstacle avoidance, rich configuration.
Still needs more work
V1: https://youtu.be/82owECOWyXA
V2: https://youtu.be/3H4T1wneXaE
V3: https://www.youtube.com/watch?v=TeB6qx2pg5c
V4: https://www.youtube.com/watch?v=cMHPemgh4iw
V5: https://www.youtube.com/watch?v=QROjEMqUw1k&t=12s
V6: https://www.youtube.com/watch?v=ik8CJaTEbtQ
This is actually making me rework a bit of the pathfinding algorithmn, the route logic and the position calculation logic.
Implemented a new function to calculate the character position, this are the test results:
This first test is the comparison between the prediction of old and new methods at the movement a movement packet arrives, so it is basically a check to see if we are calculating right.
The old function had a 75.53% correctness rate over 2624 moves, with an average error of 0.245 cells
The new one has a 99.77% correctness rate with an average of 0.002 cells of error
And this is the same comparison, but made at the movement a movement packet is sent, instead of when it arrives, so we are kinda predicting the future here, so it won't be exact.
Old one had a 15.23% match rate with avg error of 0.860 cells
New one has a 57.31% match rate of avg error of 0.427 cells