| Age | Commit message (Collapse) | Author |
|---|
|
|
|
'will-be-active' between reservation- and activation-stage.
This fixes action7/9 conditions 0x06 to 0x0A to return the same in those two stages.
|
|
strings.
|
|
strings which
includes 0xD000 to 0xD3FF (yes, 0xD0xx makes a lot of sense, really...)
and handle 0xD400 to 0xD7FF strings which map to 0xD000 to 0xD3FF
(obviously).
|
|
|
|
vehicles' running cost, and show running cost of wagons if they have it.
|
|
running_cost, inline with other vehicle types (It is the factor, not the base)
|
|
single function
-Fix: Handle the bridge recolouring mapping as the other features. Although not specified by the specs, it seems to be implicit.
|
|
DrawTileSprites into one PalSpriteID
|
|
one PalSpriteID
|
|
VarAction2 and Action7/9/D to their own function.
-Fix: Add some variables that were missing in one or both cases.
|
|
with some parts for AI use.
|
|
expose in header for use elsewhere.
|
|
instead of two single variables, following the transport type it represents
|
|
with other Specs in used.
|
|
description of a bridge.
|
|
and put bridge spec in table/bridge_land.h, where it should be.
|
|
|
|
at the right time, but all the other global variables were now loaded too early. ;)
|
|
industries, prop 24, nearby station name.
No assignation yet, no real work either.
|
|
AI-use, NewGRF property 0x08 for trains.
|
|
|
|
shores, if shores got replaced by ActionA.
|
|
substraction
|
|
informations about current map size.
|
|
still ignored)
|
|
|
|
cargo it could happen that the strings are defined by one cargo and the 'action2' by another and when one assumes that both come from the same NewGRF... So store the GRF ID with the strings. To be extra sure add the same protection mechanism to industries and towns too.
|
|
caused compilation failure with MSVC.
|
|
|
|
unneeded include from openttd.h.
|
|
now attached to their object directly and there is
no limit to the amount of names.
-Fix: NewGRF engines could not be renamed.
|
|
|
|
TTDP-compatible by allowing specifiing more sprites than needed.
|
|
behaviour
|
|
|
|
some type safety.
|
|
|
|
|
|
when it's not necessary.
|
|
overrides, and adjust scope while there.
|
|
value can be (more adequately, even better) computed from another source.
Thanks peter1138.
|
|
-Codechange: A few bad coding style inadvertendly applied too
|
|
ordering of shore sprites. It was not considered in the missing shore patch
|
|
specific year yet, force the houses with the earliest introduction year to be available.
|
|
by BigBB
|
|
|
|
layouts; forcing a sprite to always be opaque.
|
|
functions.
|
|
so NewGRFs use the proper string ids.
|
