| Age | Commit message (Collapse) | Author |
|---|
|
|
|
On TileLoop_Object, HQs are able to produce and move passengers and mail to stations, but querying the HQ tiles for cargo supplied was returning nothing. This makes it so that they return +1 to both passengers and mail.
|
|
|
|
|
|
|
|
|
|
|
|
std::vector::[push|emplace]_back()
|
|
|
|
|
|
tiles may revert to canal. In that case also check the ownership of the canal.
|
|
data is now always accessible
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
GetErrorMessageFromLocationCallbackResult instead of the GRFID.
|
|
transmitter and vice versa
|
|
considered in one more place
|
|
'unremovable' flag
|
|
|
|
were available at any point in the past to support building scenarios with historic items
|
|
function
|
|
function
|
|
information for situations when we only want to know if a tile is flat or not (cirdan, LordAro)
|
|
64000.
|
|
|
|
|
|
owned land, keep on drawing the bridges nevertheless.
|
|
|
|
overbuilding it with an object
|
|
|
|
|
|
|
|
|
|
|
|
validness.
|
|
callbacks, and check the results for validity.
|
|
157 to make them consistent with other slope check callbacks. (michi_cc)
|
|
functions use int z as well
|
|
|
|
from the station/object building code
|
|
for the terraform code
|
|
from the bridge code
|
|
use it
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
callback was run, resulting in possible differences in test and exec run
|
|
steep slopes.
|
|
_cleared_object_areas if clearing actually succeeds, else subsequential tests of the same tile will be skipped and considered successful.
|
|
|
|
another company.
|
|
|
|
|
