1 2 3 4 5 6 7 8 9 10

What are addons?

Simutrans addons are additional pak files that are either an addition to an existing pakset (such as pak64 or pak128), or a replacement for a pakset.

Downloading addons

The most important source for simutrans addons is Simutrans Addons, and also look out for newer addons at Simutrans Forum, since it takes a while for them to appear on Simutrans Add-ons page. The japanese wiki also contains a large number of addons.

Installing addons

Addons are either distributed as ready-to-use .pak files that simply needs to be placed in a suitable folder within the Simutrans directory tree, or as source code, which then needs to be compiled before use, see creating pak-files.

It is also possible to place addons in the directory tree that takes the users personal simutrans folder as root. This allows you to keep the addons separate from the paksets and to easily find and remove an addon as well as avoiding them being overwritten by an update of the pakset.The name of the addons folder within the personal simutrans directory tree must be the same as the pakset name.

Addons folder path:

• Windows: Documents/Simutrans/pakset_name
• Linux:user_home/Simutrans/pakset_name

Addons from the personal simutrans directory are loaded when you from the splash screen choose "Load with Addons".

If you want to add an object to an existing pakset, simply put the .pak file in the appropriate folder. This is usually simutrans/pak for pak64 and simutrans/pak128 for pak128. Install a replacement pak set into a new subfolder like simutrans/<replacementsetname>, and point Simutrans to that folder (using parameter "pak_file_path" in simuconf.tab? or the "-objects" starting parameter.

The new addons will be available upon restart of Simutrans. Don't add addons to a pakset folder for a different size than the one.

Restrictions

Addons cannot: Note that this section might be outdated.

• Have any assigned [translation]] text, since the current mechanism does not allow more than one translation file per language.
• Use identifiers (names) identical with those of objects already shipped in official sets (in that case they will replace the original files).

If you upgrade/update to a newer version of Simutrans or the pakset you use, you have to make sure that the latter condition still applies, and that the addons are also compatible to the new environment (although it very rarely happens that a program change requires adjusted paks).

If you share (publish) savegames which use addons, you have to specify or even supply the addons in some way, because the savegames may be unusable without them. (You also have to keep that in mind for yourself, for if you intend to install a newer version of Simutrans - or the pakset - into a new folder.)

Installing citylists

Simutrans can create city names two ways:

xx represents the language code for the chosen language; f ex en for English or de for German.

1) If there is a citylist_xx.txt file for the chosen language city names are read from this file.

2) Otherwise random city names are created from the syllables given in xx.tab

Currently there is only one citylist per language used. I.e. for english, citylist_en.txt is used. A citylist in pak/text/ will overlay a citylist in text/ so that different scenarios can have different citylists. There are some additional citylist files supplied, i.e. citylist_en_au.txt for australian city names and citylist_de_at.txt for austrian city names. You can copy the citylist either into the folder text/ or to your pak-files e.g. pak/text/. To use them, you need to rename the files. I.e. to use the austrian city names, rename citylist_de.txt to citylist_de_de.txt and rename citylist_de_at.txt to citylist_de.txt If you don't want Simutrans to use the city name lists, delete them. Simutrans will then use the old (pre 0.82.15.5exp) scheme of random city names.

---

Top

---