Record history of cost changes in pathfinder #1680
Labels
area: simulation
Involved in the game mechanics and simulation
good first issue
Suitable for newcomers
hacktoberfest
For newcomers from Hacktoberfest event
lang: c++
Done in C++ code
nice new thing ☺
A new feature that was not there before
Required Skills: C++
Difficulty: Hard
At the moment, changes to the movement cost of cells in the openage pathfinder always overwrite the old values. The old values are not saved anywhere, so going back to a previous state of the grid is currently not possible. Ideally, the grid should support going back in time, so we can roll back changes e.g. for multiplayer matches.
openage already provides the curve data types for storing values over time, so changes could be recorded using the same methods. An array curve (see #1678) would probably be the best option for storing values for a grid.
To try out the current pathfinder, check out pathfinding demo 1 by running the following command:
Tasks:
CostField
implementation. The cost record should use curve. For performance reasons, the recorded values should be stored separately from the current cost values (so not in thecells
vector).CostField
, e.g. setting a cell value.Further Reading
openage::path
pathfinding moduleThe text was updated successfully, but these errors were encountered: