| Age | Commit message (Collapse) | Author |
|---|
|
beginning of a line, please
|
|
random towns in scenario editor returns a failing message.
Fix by therken
Doxygen comments by me
|
|
waypoint_func.h
|
|
codes and group them logically
|
|
|
|
|
|
|
|
|
|
UpdateAll[Type]VirtCoords.
|
|
|
|
|
|
of ViewportSign
|
|
clean construct for invalidating nearest town for road tiles
|
|
|
|
to deal with sizeof() wrt. typedef-ed arrays.
|
|
instances to more meaningful names.
|
|
and change its behaviour accordingly
|
|
Town::GetRandom() and Industry::GetRandom()
|
|
_house_specs[]
|
|
|
|
town_type.h to separate files
|
|
|
|
and change its behaviour accordingly
-Codechange: remove dummy GetAcceptedCargo_*() handlers
|
|
|
|
|
|
code style.
|
|
vehicles/stations/industries are deleted.
|
|
|
|
GetActiveCompanyCount(), use PoolItem::GetNumItems() instead
|
|
time, binary size and run time (with asserts disabled) should be improved
|
|
PoolItem::IsValidID() and PoolItem::Get()
|
|
that we allow removing towns now, but better not have desync prone code lingering around)
|
|
PoolItem::IsValidID(index)
|
|
|
|
array (Yexo)
|
|
for testing town rating
|
|
transport 1 unit to the station.
|
|
to build towns near water by not discarding watery random tiles but by searching for near land (db48x)
|
|
this ID' from 'some' strings and replace the string name with something more sensible.
|
|
|
|
are done
-Change: the requirements for location of 'random' town are now a bit less strict
|
|
|
|
number of towns, there were too many cities
|
|
|
|
|
|
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
|
|
contain a suitable location for a town.
|
|
when querying the cost of a command.
|
