| Age | Commit message (Collapse) | Author |
|---|
|
sprite changes.
|
|
|
|
relatives
|
|
road vehicles; only ROAD isn't always enough. Also unify the way of writing it.
|
|
DrawRoadVehImage.
|
|
functions
|
|
Is/Set/HasArticulatedPart member of RoadVehicle.
|
|
|
|
|
|
prevent unnecessary inclusion newgrf.h anyway
|
|
|
|
|
|
|
|
|
|
to not confuse it with image_index from *VehInfo.
|
|
casts when converting Vehicle to specialised vehicle types. Includes safety check
|
|
|
|
code style.
|
|
vehicles in more places. Esp. they were only invalidated for trains.
|
|
|
|
for all vehicle types
|
|
company-based settings, so in a multiplayer game everyone can change them.
|
|
constant and unduplicate a few lines.
|
|
vehicles/stations/industries are deleted.
|
|
struct so (some vehicle related) NewGRF cache 'desyncs' can be tested easier.
|
|
|
|
|
|
|
|
|
|
was deleted
|
|
PoolItem::IsValidID() and PoolItem::Get()
|
|
SoundFX, which was used as a byte and uint16 at different places, when the uint16 sound ID is meant.
|
|
PoolItem::IsValidID(index)
|
|
|
|
creating vehicles, instead of arbitrary sprites not related to the vehicle. (though that also applies to the question mark)
|
|
|
|
some code.
|
|
this ID' from 'some' strings and replace the string name with something more sensible.
|
|
sources too
|
|
information in purchase-list/after building before users have a chance to blame OpenTTD for incorrectly autorenewing/-replacing.
|
|
process of moving the vehicle which means that only the (orientation) data for the vehicles in front of it is valid. Now the data for the vehicles behind the vehicle are valid too.
|
|
VehiclePositionChanged and EndVehicleMove.
|
|
|
|
articulated engine has been built. (except 0x16)
|
|
reserve a slot at a single road stop. 255 + 1 gives trouble, but 64 is even more than the roadstop would be able to handle within the slot timeout time.
|
|
stop, not when they own the road/tram track.
|
|
which cannot accept CT_INVALID.
-Codechange: Add Engine::GetDefaultCargoType() and Engine::CanCarryCargo() and use them.
-Fix [FS#2617]: When articulated parts have no available default cargo, use the cargo type of the first part for livery selection.
-Change: To decide whether a vehicle is refittable do not test its current capacity for being zero, but always use the 'capacity property'.
Note: The property is used unmodifed without calling CB 15/36. By setting it to a non-zero value and returning zero in the callback vehicles can be refitted to/from zero capacity for e.g. livery effects.
Note: It is intentional that you cannot control refittability by CB 36.
|
|
skipped by 'continue'.
|
|
|
|
|
