| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
already when placing transmitters
|
|
generating map
|
|
|
|
|
|
more likely to be updated [o-s].
|
|
transmitter nearby
|
|
|
|
|
|
more like TTDPatch does, i.e. fall back to the default check when the callback is not yielding a result for a tile instead of disallowing building the object
|
|
|
|
_cleared_object_areas.
|
|
|
|
changed colour. Now they do, except when the "decide colour" callback is (defined to be) used
|
|
|
|
canal didn't take the cost for clearing the sea into account
|
|
it with canal under it. If we delete the object the terraforming will still fail due to the canal
|
|
|
|
repeated testruns resp. the exec run.
|
|
water.
|
|
window was open for that object
|
|
|
|
|
|
test for either of the bits being set
|
|
removed properly
|
|
called
|
|
of every 250 ticks
|
|
|
|
|
|
|
|
|
