| Age | Commit message (Collapse) | Author |
|---|
|
it for more spritegroups
|
|
industry temporarily refues to accept some cargo
|
|
|
|
|
|
|
|
callbacks 28 and 2F. (yexo)
|
|
|
|
industry var 42 while the production level was 0
|
|
|
|
industries from construction callbacks 17, 28 and 2F. That is: The randombits the house/industry will start with, if construction succeeds.
|
|
industries and houses during construction callbacks.
|
|
67/68 could cause a crash
|
|
|
|
industries in var 45; TTDPatch doesn't seem to set the colour data in that case either.
|
|
Industry.
|
|
|
|
CheckIfCallBackAllowsCreation().
|
|
returned the high 8 bits of var A2. Same problem for 9B/9A/98
|
|
tile chain when the industry tile was part of an original industry
|
|
if a header require a header make it include that header
|
|
variables. Also make use of TileArea functions for determining the 'width' and 'height' of an industry.
|
|
before the details string.
Gentlemen, swap your string parameters.
|
|
production callback version 0.
|
|
|
|
@param to @tparam if necessary
|
|
which were sometimes missing and sometimes just typos
|
|
|
|
for more consistency and distinguishability.
|
|
GetIndustryByTile()
|
|
|
|
|
|
instead of using a big union
|
|
PoolItem::IsValidID() and PoolItem::Get()
|
|
PoolItem::IsValidID(index)
|
|
|
|
|
|
this ID' from 'some' strings and replace the string name with something more sensible.
|
|
iterations and show a messagebox blaming the newgrf. (mizipzor)
|
|
sources too
|
|
but at least it can be consistent.
|
|
color and colour.
|
|
|
|
|
|
TTDPatch and
OpenTTD feature with it's origin in TTDPatch to replace/add/change vehicles
(including e.g. maximum speed, graphics and introduction year), stations,
bridges, industries, town houses or any other graphics used by either
TTDPatch or OpenTTD, would tell that building an industry is okay, which
is queried using a so-called callback that allows the NewGRF author to
test all kinds of information about the neighbourhood where the industry
might get build, it would corrupt, i.e. overwrite with invalid data, the
structure that is used to build up an error message. This then might result
in trying to resolve an invalid StringID, an internal numeric representation
of all translateable strings, which would in it's turn trigger a safety
check that is added to ensure invalid StringIDs are never resolved.
|
|
|
|
|
|
client so it is immediatelly clear which one you are working with.
|
|
times faster than pre-r14416 in average case
|
|
the 'nearest land/water' check (~25% performance penalty)
|
|
industries
|
