| Age | Commit message (Collapse) | Author |
|---|
|
|
|
values.
|
|
|
|
Script).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the command proc.
When finished, this will allow each command handler to take individually
different parameters, obliviating the need for bit-packing.
|
|
This is accomplished by changing it to a single member struct with the
appropriate operator overloads to make it all work with not too much
source modifications.
|
|
|
|
function calls.
|
|
|
|
|
|
|
|
|
|
One question that keeps popping up: "when do we release 2.0?".
NewGRF will force that at least 1.16 will be 2.0, but to not wait
for this, let's drop the "1." and be for ever done with that
conversation.
We are following in the footstep of giants here.
|
|
|
|
|
|
|
|
Currently, scripts use various heuristics to detect loaded NewGRFs that are inherently unreliable.
The list of loaded NewGRFs is easily accessible to a human player, and thus giving
scripts the same information is consistent with the current approach to not give scripts
more information than a human player.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(#9350)
|
|
|
|
It was rather confusing which one was for what, especially as some
SaveLoad flags were settings-only. Clean up this mess a bit by
having only Setting flags.
|
|
|
|
|
|
that) in the middle of a C-string
|
|
(#9306)
This is mostly done as there are now constraints on settings.ini you might not
expected. For example, conditional settings always have to come last, as otherwise
they would influence the index.
|
|
|
|
|
|
It is not nice to have your definition say you won't change a value
while in fact the whole reason for your existance is to change it.
|
|
This could have unwanted side-effects, as it could change the
source for ever and ever.
|
