| Age | Commit message (Collapse) | Author |
|---|
|
before the details string.
Gentlemen, swap your string parameters.
|
|
|
|
signal GUI
-Codechange: move the state updates from OnPaint
|
|
settings in the scenario editor. Also re-enable changing some difficulty settings (e.g. max loan) in the scenario editor.
|
|
|
|
@param to @tparam if necessary
|
|
which were sometimes missing and sometimes just typos
|
|
|
|
for more consistency and distinguishability.
|
|
other functions already.
|
|
them wrt. duplicate GRF IDs.
|
|
|
|
|
|
relatives
|
|
UpdateAll[Type]VirtCoords.
|
|
level to avoid glitches on the difficulty button
|
|
IsTrainWagon(), IsMultiheaded(), EngineHasArticPart() and IsRearDualheaded() members of Train
|
|
|
|
instead of searching them everytime payment is made
|
|
|
|
|
|
commands expect an integer but don't get one.
|
|
|
|
|
|
|
|
for a new company instead of zeroing them.
|
|
|
|
for all vehicle types
|
|
company-based settings, so in a multiplayer game everyone can change them.
|
|
reached like break after returns or break after functions that never return (i.e. NOT_REACHED)
|
|
with calls to CmdChangeCompanySetting
|
|
settings: the default set in the main menu / config file is now really the default for a new company, and changing the value in game will no longer change the default for new companies.
|
|
unnecessarily add it.
|
|
|
|
In the first phase, indexes are stored. In the second phase, indexes are checked for validity and converted to pointers
|
|
CompanySettings struct
|
|
|
|
cause of the problem, r16129 just causes it to be triggered.
|
|
openttd.cfg.
|
|
|
|
they aren't seen as new groups.
|
|
[network]:server_bind_ip doesn't exist anymore. Add the IPs/hostnames to [server_bind_addresses]
|
|
|
|
table/settings.h. Patch breaking time :)
|
|
|
|
config files) were overwritten with default values.
|
|
classes ScriptScanner/ScriptFileInfo.
|
|
sources too
|
|
generated in the generate world window to be customized.
Some warnings:
-the maximum number of towns to be accepted is set to 5000
-the minimum number of towns to be accepted is set to 1
-the number that is specified is NOT guaranteed to be the exact number of towns generated. The normal mechanism of town creation has not been modified. So town placement can still fail.
-setting a custom number of town will change your difficulty settings to custom as well
|
|
(even if 'configure --enable-dedicated' passed)
|
