Age | Commit message (Collapse) | Author |
|
cargo is valid.
|
|
|
|
|
|
Adds a console command newgrf_profile to collect some profiling data about NewGRF action 2 callbacks and produce a CSV file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cargo type.
It is only an error if the invalid result is actually used. This will be silently ignored at the moment.
It is still an error if a duplicate cargo type is returned.
|
|
|
|
|
|
|
|
inlineable. Speedup sprite resolving by about 8 percent.
|
|
|
|
include the new triggers.
-Fix: [NewGRF] Reset used random triggers only after all A123 chains have been resolved, so that all RA2 in all chains can test the shard triggers. This also includes multiple RA2 in the same A123 chain.
-Fix: [NewGRF] Industry random triggers are stored per tile, even when randomising the shared random bits of the parent industry.
|
|
|
|
types to 128 per NewGRF and 240 in total.
|
|
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
constructor.
|
|
GetErrorMessageFromLocationCallbackResult instead of the GRFID.
|
|
|
|
pointer since they are never NULL.
|
|
|
|
place (cirdan, LordAro)
|
|
tile is invalid.
|
|
Eagle_rainbow)
|
|
|
|
|
|
|
|
|
|
for adding derived classes.
|
|
complicated and also returned the wrong thing for cargos not present in the translation table.
|
|
|
|
|
|
error.h
|
|
simplify code checking for that
|
|
callback 28.
|
|
variables. (rubidium)
|
|
callbacks, and check the results for validity.
|
|
use instead of property 18.
|
|
variables (using var 7B). Currently most useful for vehicle var 60.
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
industry shape and location callbacks.
|
|
|
|
is intentionally removed, it is only used together with 'scope'.
|
|
continuously overwritten by e.g. industry prospection without closing the old error window; also StopTextRefStackUsage() was not called for errors returned by commands (which caused FS#4599). Now return in the CommandCost result whether the textref stack needs to be used, and store a copy of the stack values in the error window just like for the normal string parameters.
|
|
StartTextRefStackUsage() to make it more obvious that you must call StopTextRefStackUsage() at some point. Also extent the documentation.
|