Tasks:Path Finding: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
== Requirements == | == Requirements == | ||
* A perfect or near-perfect path has to be found, when possible, from one point to | * A perfect or near-perfect path has to be found, when possible, from one point to another. | ||
* It should be able to handle goals in different altitudes, handle the y axis. | * It should be able to handle goals in different altitudes, handle the y axis. | ||
* It has to be quick and do not degrade the | * It has to be quick and do not degrade the frame rate in older machines. | ||
* NPC's should be able to handle collision with other NPC's or objects that were not supposed to be in their path, ie. blocked the path after the search was done, | * NPC's should be able to handle collision with other NPC's or objects that were not supposed to be in their path, ie. blocked the path after the search was done, | ||
* It should be able to load and save data so that it can | * It should be able to load and save data so that it can reconstitute at least ongoing pathfinding searches in the current map, after a game save/load. | ||
* It should be capable of following the player to wherever he goes so that the player can't find | * It should be capable of following the player to wherever he goes, so that the player can't find spots where he can attack without being wounded. | ||
* | * It has to be able to find items in the current map. | ||
== References == | == References == | ||
Adonthell 0.3 version of the pathfinding code in CVS | Adonthell 0.3 version of the pathfinding code in CVS | ||
Version 1.2 of the pathfinding code in CVS | Version 1.2 of the pathfinding code in CVS | ||
Revision as of 21:25, 13 April 2009
Overview
The pathfinding engine has the responsibility of providing NPCs the capacity to move from one point to another in the map. To do so it first needs to find a path between those two points, and then handle the movement of the character trough the path.
Dependencies
Mapengine implementation
Requirements
- A perfect or near-perfect path has to be found, when possible, from one point to another.
- It should be able to handle goals in different altitudes, handle the y axis.
- It has to be quick and do not degrade the frame rate in older machines.
- NPC's should be able to handle collision with other NPC's or objects that were not supposed to be in their path, ie. blocked the path after the search was done,
- It should be able to load and save data so that it can reconstitute at least ongoing pathfinding searches in the current map, after a game save/load.
- It should be capable of following the player to wherever he goes, so that the player can't find spots where he can attack without being wounded.
- It has to be able to find items in the current map.
References
Adonthell 0.3 version of the pathfinding code in CVS Version 1.2 of the pathfinding code in CVS