Age | Commit message (Collapse) | Author |
|
support and users for testing.
|
|
|
|
confusing code
|
|
|
|
null-operations
|
|
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
|
|
was on it
|
|
the bridge speed limit
|
|
corner of a tile, and use it to simplify the code in a few places
|
|
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
|
|
|
|
appropriate enums
|
|
pillars. This fixes newgrf's high-bridge pillars drawing. Also remove the now obsolete _bridge_poles_table which was already integrated into the bridge sprite tables
|
|
a now unnecessary test which hid the faulty entry till now and undo r4398 (don't do this!)
|
|
|
|
|
|
|
|
railtype went unnoticed...
|
|
mysteriously it will break in the morning, fix r4373
|
|
- Report the correct z alongside the ramp when a foundation is present
- Always report the z under the bridge for a bridge middle part, except if the z hack is used
This should fix some weird behavior of the tile selector near bridges
|
|
coordinates where it suffices.
|
|
coordinates of the tile to operate on - to a TileIndex
Remove DoCommandByTile(), because now it does the same as DoCommand()
|
|
declaration)
|
|
by TILE_HEIGHT. Reverted one change from the previous commit because it was faulty
|
|
|
|
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.
|
|
of the comma operator
|
|
get information about rail tiles
|
|
|
|
|
|
shiny new functions and mark some strange constructs with XXX
|
|
if there's a transport route at all under the bridge
|
|
make the only place which still extracted that info diretly use the wrapper
|
|
(the line above already says what's going on)
|
|
instead of again and again
|
|
with similar functionality
|
|
offset once instead of all over the place; also use UpdateSignalsOnSegment() instead of SetSignalsOnBothDir(), because this is sufficient
|
|
under bridges works; also remove an unnecessary local variable
|
|
|
|
bridge after removing it. For crossings we can always use .m2 because it is already 0 when not owned by a town.
|
|
|
|
removal loop
|
|
comprehensible and add the needed accessors
|
|
Fix r3887
|
|
bridge ramp
|