| Age | Commit message (Collapse) | Author |
|---|
|
it doesn't recompile everything that needs to be recompiled...
|
|
in the output of "openttd -h"
|
|
|
|
|
|
|
|
possible to change the password of other companies (on the server)
|
|
saved in case threading is enabled, which is enabled by default
|
|
that can be cleared/terraformed by a company
|
|
|
|
road vehicles and trains.
|
|
|
|
unrelated to the number of passed game days, i.e. don't stop aging chat messages when the server is paused
|
|
scenario editor
|
|
paused. Now you can enable or disable that with a setting
|
|
load), and add support for (safe) loading with a LoadFilter
|
|
desync debug options enabled.
|
|
debugging because some cache was invalidated but never reset
|
|
had an error message open in the game while whatever triggered you to go back to the main menu
|
|
starting an OpenTTD dedicated server like we mention it in the title bar for the GUI version
|
|
|
|
|
|
|
|
leak, causing valgrind warnings
|
|
|
|
some headers
|
|
|
|
caused the introgame to be the server's game causing desyncs when people tried to join
|
|
|
|
|
|
|
|
function and two company globals.
|
|
|
|
|
|
missed :)
|
|
variables and move them to a more logical location
|
|
|
|
VARDEF and put them in a more logical location
|
|
debug is turned on)
|
|
|
|
a savegame fails on the dedicated server, generate a new game.
Generating a new game is the least bad solution:
* loading the intro game: desyncs due to GM_MENU on the server and GM_NORMAL on the clients, NewGRFs not being loaded on the server but being loaded on the client;
* creating an empty map: OpenTTD will go crazy due to missing towns. Also clients can't properly join because of the missing towns;
* loading the last saved game: doesn't always exist and loading it might fail causing an infinite loop;
* stopping being a server: breaks the dedicated server horribly; if you loaded the game via rcon you can't connect with it anymore as you can't join the server;
* generating a new game: should always succeed, although people might think a scenario loaded fine because there are no companies and such.
|
|
|
|
|
|
|
|
before CleanupGeneration() to avoid conflicts with concurrent GUI code.
|
|
sync during GUI operation.
|
|
DEBUG() output. It was triggered on exceptions, especially when aborting world generation.
|
|
of _current_company to ensure proper restoration.
|
|
|
|
don't store just reset values in the savegame but the data from the previous tick
|
|
is overridden and (after a while) there is no company 0 on new year anymore
|
