Update of patch #1379 (project wesnoth):
Status: None => In Progress
Assigned to: None => crab
_______________________________________________________
Follow-up Comment #1:
since the time that EasyCoding task was written, pathfinding implementation
was cleaned up, and move_left really contains 'movement left' now. so, the
patch in this form is not necessary. but, the patch exposes some issues in AI
code where it uses it in the old way.
so, the following must be done to solve the issue:
readonly_context_impl::suitable_keep must be fixed to treat move_left as
'movement left' (i.e. it should search for keep for which move_left is
maximum, cost_to_loc should be renamed to move_left_at_loc,
cost_to_best_free_keep should be renamed movement_left_at_best_free_keep )
the issue 'if current castle is full, go to the other one' you raised at IRC
is valid. adding logic to handle that is welcome, too.
The semantics of suitable_keep is:
"return a keep where we can recruit. If there is a choice of keeps, prefer a
keep where we can recruit this turn."
default_ai_context_impl::suitable_keep and
default_ai_context_proxy::suitable_keep are accidentally duplicated code and
should be removed.
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?1379>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
