| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INVALID_RAILTYPES, if it was accidentally tested, would match any railtype.
|
|
|
|
|
|
|
|
|
|
|
|
penalties differ.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Road vehicles shouldn't reverse all of a sudden.
|
|
the cost of a path exceeds max. penalty.
|
|
when the cost of a path exceeds max. penalty.
|
|
reverse.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
function.
|
|
|
|
|
|
Given any speed issue cannot be attributed to checking for _debug_NNN_level, removing this is a safe action
This fixes #6652.
|
|
when trying to find any safe position.
|
|
bug about never used NPF_FLAG_IGNORE_RESERVED flag
|
|
|
|
|
|
meant the same thing, but only one was used. Keep PATH_TOO_LONG since it has the better documentation.
|
|
waiting position from a waypoint.
|
|
finding code and remove need to return fake path distance. (juanjo)
|
|
too long condition, as destination should not be considered in the former case.
|
|
path and applying penalty.
|
|
integers.
|
|
path finder costs with tile distances, thus vehicles went to depots which were factor 100 too far away. (juanjo)
|
|
segments with different railtype in the YAPF cache. (JGR)
|
