Age | Commit message (Collapse) | Author |
|
|
|
could e.g. result in incomplete clearing of protected houses.
|
|
|
|
|
|
depots, industries, towns and waypoints
|
|
(if enabled). Primarily useful for systems with touch screen (aapo)
|
|
(optional) parameter.
|
|
target invalid industry
|
|
OWNER_TOWN instead of the founder to take care of protected buildings and to not get stressed by town ratings.
|
|
comments.
|
|
|
|
0x29/0x35. (Yexo)
|
|
|
|
client so it is immediatelly clear which one you are working with.
|
|
introducing a daily random industry change.
This will allow to perform more changes per month on big maps and less on smaller maps, while not overtaxing the IndustryMonthlyLoop process.
Thanks to frosch, for nice code ideas and rewrites
|
|
implicitly tells that it wants to be build on water (land shape flags bit 5).
|
|
of industries into two news of their own
|
|
news event, even those funded by a real player.
|
|
|
|
for stations, houses and industries
|
|
|
|
slopes, just in case someone needs them for fallback.
|
|
tile where search has been successful, or INVALID_TILE if it has not
|
|
of NewGRFs an industry can be built on a steep slope, however when 'querying' the foundation type of an industry we neglected the fact that these steep slope tiles do not have a foundation. As a result of this when one built a structure requiring foundations on a tile SW or SE of a steep slope industry tile it would try to apply the foundation on the steep slope to determine whether to draw the wall of the foundation and trigger an assert.
|
|
settings stored in the savegame so there is no need to have a duplicate copy of it for new games.
|
|
|
|
-Codechange: move all Settings into substructs of _settings in a way that they are logically grouped.
|
|
tile-info-window.
|
|
|
|
|
|
AddNewsMessage as there is (for each news message type) a tuple of 4 parameters that is the same for all calls.
|
|
something more than whitespace as description of files that don't have a description.
|
|
|
|
objects can be build, but check it directly in the pool so we do not have to call destructors in the testing phase. Stations still use the autoptr though.
|
|
every 256 ticks, not every tick... Also bail out of the triggers a little earlier if you know they are not going to happen anyway.
|
|
|
|
uniform naming of the thing instead of using both names for the same thing.
|
|
texteff.cpp (it isn't a text effect after all). Also remove a few more functions from functions.
|
|
place to a single location.
|
|
|
|
compiler's decisions about inlining
|
|
|
|
|
|
|
|
instead of transparent
|
|
station_func.h.
|
|
|
|
strings.
|
|
GetTileTrackStatus().
|
|
there can be less checks in pathfinders for depots/stations/tunnels/bridges
|