| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
TILE_HEIGHT for the snow line code
|
|
case, which saves us making the specs even more convoluted.
|
|
suddenly only able to carry coal
|
|
vehicle is one of the refittable cargos in case of refittable engines.
|
|
more strictly.
|
|
Vehicle to simplify code.
|
|
|
|
minimum start year for that house was set to 1930
|
|
|
|
for shore tiles... we should continue to handle it.
|
|
action5 except sea shores
|
|
NewGRF indication.
|
|
not have newlines, e.g. the NewGRF's name
|
|
spriteset IDs.
|
|
Action1 in a single Action2.
|
|
construction stages in spritelayouts with inconsistent number of sprites per spriteset.
|
|
|
|
|
|
each NewGRF, thus waterfeatures could glitch when the properties were set by a previous NewGRF and the NewGRF assumed the properties to be unmodified
|
|
|
|
|
|
|
|
GrfProcessingState, and reset them after each loading stage.
|
|
GrfProcessingState, and reset them after each loading stage.
|
|
temporary data at a specific spot, esp. clear 'data_blocks' now.
|
|
loading into a struct.
|
|
|
|
|
|
|
|
cases like creating a new scenario.
|
|
reasons.
|
|
speed fraction).
|
|
|
|
|
|
|
|
specific point, data might be freed twice.
|
|
|
|
multiple times, the previously allocated sprite layouts were not freed.
|
|
TileLayoutSpriteGroup instead of allocating it separately.
|
|
spritelayouts allocated on the heap, and make use of constructors and destructors.
|
|
failure, also display an error in the GUI.
|
|
|
|
also to station groundsprites from action 1.
|
|
-Remove: the '-i' option for palette selection.
|
|
the values were OR-ed. Use the last set value instead.
|
|
callback is valid
|
|
|
