| Age | Commit message (Collapse) | Author |
|---|
|
support and users for testing.
|
|
It serves no real purpose except causing confusion
|
|
confusing code
|
|
EnsureNoVehicleOnGround() to make more clear what it does
|
|
ROAD_{NORMAL,CROSSING,DEPOT} to ROAD_TILE_* for consistency
|
|
RAIL_TYPE_{NORMAL,SIGNAL,...} have nearly the same name, rename RAIL_TYPE_* to RAIL_TILE_* of extra clarity
|
|
Sorry
|
|
handle success/failure can fail if a recursive call fails but doesn't set the error message, thus resulting in an old, possibly erroneous being used (see FS#130 prior to r4585). Now properly reset the global variable _error_message in these cases.
|
|
command did not return the appropiate error message of invalid-slope when building road.
|
|
There's exactly one implemented function (unbarring a level crossing) and one place where it can be triggered (a train leaves a level crossing)
It's a bit overkill, so just handle this one case where it can happen
|
|
|
|
(STR_1[08]00_LAND_SLOPED_IN_WRONG_DIRECTION) - one just contains two redundant words
|
|
appropriate enums
|
|
with the remove-tool (r4348 surfaced this). In CmdRemoveRoad tiletype was not checked for ownership. Intorudce IsLevelCrossingTile() which checks if a tile is a crossing without knowing the type. Suggested by peter1138 and Tron.
|
|
coordinates of the tile to operate on - to a TileIndex
Remove DoCommandByTile(), because now it does the same as DoCommand()
|
|
declaration)
|
|
Last occurence of FindLandscapeTile in the tile-specific functions gone. Thanks to Tron for doing lots of work in this direction
|
|
ground types (including roadworks).
|
|
|
|
|
|
(Pointed out by peter1138)
|
|
|
|
Although it was an accessor, nor his usage nor the values were clear.
|
|
|
|
|
|
|
|
code and proofreading, thanks to peter1138 for another lot of code and ideas.
|
|
|
|
put and get the status of a level crossing
|
|
from a tile
|
|
|
|
|
|
|
|
|
|
|
|
get information about rail tiles
|
|
|
|
shiny new functions and mark some strange constructs with XXX
|
|
road) under bridges
|
|
|
|
|
|
magic numbers by enums and some related changes
|
|
deem it unnecessary
|
|
|
|
|
|
a level crossing by some less magic numbers
|
|
code by using them
|
|
which direction a pieces of rail goes
|
|
tile/depot/waypoint. This is just a tiny step, the rail code needs way more love and caring
|
|
|
