Linux Binary
Windows Executable
Base Package
Chronological list of changes since the release of 0.82.15exp
24-Nov-03
FIX: fixed an uninitialized variable in station sorting code
that could cause a program crash
FIX: passenger destinations are shown properly in city info
window again.
CHANGE: added bounds checks to station sort mode text arrays
access code
CHANGE: changed Peters new city building rules to avoid
cities only consisting of one single, extremely long
road
Chronological list of changes since the release of 0.82.15.1exp
25-Nov-03
FIX: fixed a bug in city building rule evaluation code
CHANGE: moved simuconf.tab to config subdirectory
CHANGE: moved city building rules into config/cityrules.tab
Chronological list of changes since the release of 0.82.15.2exp
27-Nov-03
FIX: fixed a potential buffer overflow is city building
rules reading code
FIX: fixed a potential crash if a curiosity building was
removed
Chronological list of changes since the release of 0.82.15.3exp
29-Nov-03
CHANGE: better distinguishable colors for finance window
FIX: on slow computers it could happen that the vehicle
starting sound was played several times. This should
be fixed now.
28-Nov-03
FIX: fixed a variable overflow in finance window (Hendrik)
FIX: finance window total money is now updated dynamically
(Hendrik)
CHANGE: replaced most strcpy() calls by a bounds checked, 0
terminating string copy function
Chronological list of changes since the release of 0.82.15.5exp
Changed City List
Chronological list of changes since the release of 0.82.15.5exp
14-Dec-03
FIX: forrest config is now read from 'config' subdirectory, too
CHANGE: split forrest config from simuconf.tab, now it read
from forrestconf.tab
FIX: tried to fix the goods distribution problem for factories
bigger than 2x2 tiles
since 0.82.15.2exp there are some special City building rules
Documentation:
There are two sets of rules. I set of rules for building houses and one set for building roads. The syntax of both rule sets is the same.
Simputrans applies the rules to locations within the city limits to see if a house or road should be built there.
A rule for building a house looks like this:
house_1 = ... Hn. sss
house_1.chance = -2
The first line is the rule itself. It consists of three groups of 3 characters each. Explanation follows below. The second line tells how important this rule is. Lower bound is -7, no upper bound.
The character groups:
The three groups of character are actually three lines of a square. The evaluated spot is right in the middle. The characters tell the code what checks to perform.
There are the following symbols defined:
S = must not be a road
s = must be a road
n = must be 'nature' (grass, no owner)
H = must not be a house
h = must be a house
. = anything fits
A rule is evaluted to true, if all checks succed. I.e. if a spot is checked for building a house, it is sufficient that one of the house building rules evaluteas to true (same for roads).
Have fun creating your own city building rules...
even you are impressed 