A common example is pathing from storage to a remote source. The user should be able to provide a key for the path (e.g., combination of room name + source ID) as well as the source and destination RoomPositions.
Optionally, two paths should be generated, a primary (for roads) and a secondary (for avoiding the roads, including none of the positions on the primary). Typical PathFinder options should be forwarded.
A creep should be able to follow either path, forward or backward, automatically approaching the path if necessary.
A common example is pathing from storage to a remote source. The user should be able to provide a key for the path (e.g., combination of room name + source ID) as well as the source and destination RoomPositions.
Optionally, two paths should be generated, a primary (for roads) and a secondary (for avoiding the roads, including none of the positions on the primary). Typical PathFinder options should be forwarded.
A creep should be able to follow either path, forward or backward, automatically approaching the path if necessary.
POI paths should be cached in Memory by default.