#openttdcoop wiki - User contributions [en]

IRC

2010-07-05T10:11:59Z

Petert: /* Webbased IRC client */ Fixed link

IRC (Internet Relay Chat) is used to improve the communication between all players and friends of #openttdcoop.

Channel: '''#openttdcoop''' + Server: '''irc.oftc.net''' / irc://irc.oftc.net/openttdcoop

If you want to join our community, you will need an '''IRC client'''. We therefore recommend one of these clients:

* http://en.wikipedia.org/wiki/ChatZilla (Many OS'es, Firefox Addon)
* http://konversation.kde.org/ (Linux, KDE)
* http://www.xchat.org/ (Many OS'es)
* http://www.silverex.org/ (Win32 freeware fork of XChat)
* http://www.bersirc.org (Microsoft Windows Only)
* http://colloquy.info/ (Mac OS X)
* http://irssi.org/ (Linux, other UNIX)
* http://www.weechat.org/ (Unix-like)
* [[Wikipedia:Comparison of Internet Relay Chat clients]]

If you installed the client, connect to the OFTC IRC network. For further details and FAQ see http://www.oftc.net/ . 
Alternatively you can also use our [http://irc.openttdcoop.org/ webclient] or [http://www.mibbit.com Mibbit] if you do not want to install anything.

To join our channel, simply type: ''/join #openttdcoop'', or join via irc://irc.oftc.net/openttdcoop . Be sure to have [[IRC_Highlighting]] enabled.

==Webbased IRC client==
'''http://irc.openttdcoop.org/''' ('''Network''': [http://oftc.net/ OFTC] and '''URL''': irc.oftc.net)

==IRC Commands - NickServ==

====Register your nick====
Registers a nickname in our database for your use. Registering your nickname ensures it is reserved for your use and cannot be used by others if you do not wish them to use it. It also allows you to associate various pieces of information with your nickname and also to have access to registered channels.
<pre>
/msg nickserv register <password> <email>
</pre>

====Enforce identification====
''Enforce'' enables or disables nickname enforcement of your account. This means that if someone who is not not on your access list attempts to use your nickname and doesn't identify within a given period their nick will be forcefully changed.
<pre>
/msg nickserv set enforce on
</pre>

====Reclaim your nickname====
If your nickname is being held by services, as is the case if your nickname has been enforced recently, this command will release the hold and change your nickname to the nickname that you specify. This command will also free up your nickname if another user is using it and will change your current nickname to be your registered nickname if successful.
<pre>
/msg nickserv ghost <nickname> <password>
</pre>

====Link your nickname====
Link this nickname to a master nickname. This effectively creates an alias for your nickname to the master nickname.
<pre>
/msg nickserv link master_nickname [password]
</pre>

====General Help====
'''NickServ''' (Nickname services)
<pre>
/msg nickserv help
</pre>
'''ChanServ''' (Channel Services)
<pre>
/msg chanserv help
</pre>

[[Category:Guides]]
[[Category:IRC]]

IRC

2010-07-04T12:22:11Z

Petert:

IRC (Internet Relay Chat) is used to improve the communication between all players and friends of #openttdcoop.

Channel: '''#openttdcoop''' + Server: '''irc.oftc.net''' / irc://irc.oftc.net/openttdcoop

If you want to join our community, you will need an '''IRC client'''. We therefore recommend one of these clients:

* http://en.wikipedia.org/wiki/ChatZilla (Many OS'es, Firefox Addon)
* http://konversation.kde.org/ (Linux, KDE)
* http://www.xchat.org/ (Many OS'es)
* http://www.silverex.org/ (Win32 freeware fork of XChat)
* http://www.bersirc.org (Microsoft Windows Only)
* http://colloquy.info/ (Mac OS X)
* http://irssi.org/ (Linux, other UNIX)
* http://www.weechat.org/ (Unix-like)
* [[Wikipedia:Comparison of Internet Relay Chat clients]]

If you installed the client, connect to the OFTC IRC network. For further details and FAQ see http://www.oftc.net/ . 
Alternatively you can also use our [http://irc.openttdcoop.org/ webclient] or [http://www.mibbit.com Mibbit] if you do not want to install anything.

To join our channel, simply type: ''/join #openttdcoop'', or join via irc://irc.oftc.net/openttdcoop . Be sure to have [[IRC_Highlighting]] enabled.

==Webbased IRC client==
'''http://www.openttdcoop.org/irc/''' ('''Network''': [http://oftc.net/ OFTC] and '''URL''': irc.oftc.net)

==IRC Commands - NickServ==

====Register your nick====
Registers a nickname in our database for your use. Registering your nickname ensures it is reserved for your use and cannot be used by others if you do not wish them to use it. It also allows you to associate various pieces of information with your nickname and also to have access to registered channels.
<pre>
/msg nickserv register <password> <email>
</pre>

====Enforce identification====
''Enforce'' enables or disables nickname enforcement of your account. This means that if someone who is not not on your access list attempts to use your nickname and doesn't identify within a given period their nick will be forcefully changed.
<pre>
/msg nickserv set enforce on
</pre>

====Reclaim your nickname====
If your nickname is being held by services, as is the case if your nickname has been enforced recently, this command will release the hold and change your nickname to the nickname that you specify. This command will also free up your nickname if another user is using it and will change your current nickname to be your registered nickname if successful.
<pre>
/msg nickserv ghost <nickname> <password>
</pre>

====Link your nickname====
Link this nickname to a master nickname. This effectively creates an alias for your nickname to the master nickname.
<pre>
/msg nickserv link master_nickname [password]
</pre>

====General Help====
'''NickServ''' (Nickname services)
<pre>
/msg nickserv help
</pre>
'''ChanServ''' (Channel Services)
<pre>
/msg chanserv help
</pre>

[[Category:Guides]]
[[Category:IRC]]

IRC

2010-07-04T12:18:37Z

Petert: /* Helpful commands/settings to make your Nick belonging to you */

IRC (Internet Relay Chat) is used to improve the communication between all players and friends of #openttdcoop.

Channel: '''#openttdcoop''' + Server: '''irc.oftc.net''' / irc://irc.oftc.net/openttdcoop

If you want to join our community, you will need an '''IRC client'''. We therefore recommend one of these clients:

* http://en.wikipedia.org/wiki/ChatZilla (Many OS'es, Firefox Addon)
* http://konversation.kde.org/ (Linux, KDE)
* http://www.xchat.org/ (Many OS'es)
* http://www.silverex.org/ (Win32 freeware fork of XChat)
* http://www.bersirc.org (Microsoft Windows Only)
* http://colloquy.info/ (Mac OS X)
* http://irssi.org/ (Linux, other UNIX)
* http://www.weechat.org/ (Unix-like)
* [[Wikipedia:Comparison of Internet Relay Chat clients]]

If you installed the client, connect to the OFTC IRC network. For further details and FAQ see http://www.oftc.net/ . 
Alternatively you can also use our [http://irc.openttdcoop.org/ webclient] or [http://www.mibbit.com Mibbit] if you do not want to install anything.

To join our channel, simply type: ''/join #openttdcoop'', or join via irc://irc.oftc.net/openttdcoop . Be sure to have [[IRC_Highlighting]] enabled.

==Webbased IRC client==
'''http://www.openttdcoop.org/irc/''' (for server oftc.net)

==IRC Commands - NickServ==

====Register your nick====
Registers a nickname in our database for your use. Registering your nickname ensures it is reserved for your use and cannot be used by others if you do not wish them to use it. It also allows you to associate various pieces of information with your nickname and also to have access to registered channels.
<pre>
/msg nickserv register <password> <email>
</pre>

====Enforce identification====
''Enforce'' enables or disables nickname enforcement of your account. This means that if someone who is not not on your access list attempts to use your nickname and doesn't identify within a given period their nick will be forcefully changed.
<pre>
/msg nickserv set enforce on
</pre>

====Reclaim your nickname====
If your nickname is being held by services, as is the case if your nickname has been enforced recently, this command will release the hold and change your nickname to the nickname that you specify. This command will also free up your nickname if another user is using it and will change your current nickname to be your registered nickname if successful.
<pre>
/msg nickserv ghost <nickname> <password>
</pre>

====Link your nickname====
Link this nickname to a master nickname. This effectively creates an alias for your nickname to the master nickname.
<pre>
/msg nickserv link master_nickname [password]
</pre>

====General Help====
'''NickServ''' (Nickname services)
<pre>
/msg nickserv help
</pre>
'''ChanServ''' (Channel Services)
<pre>
/msg chanserv help
</pre>

[[Category:Guides]]
[[Category:IRC]]

Ruleset

2010-05-31T01:14:33Z

Petert: /* Rules of our games */ Extra bolded

==Note==
Rules are used to ease the cooperative gameplay. Do not think of rules as laws, being punished if you don't follow them, but rules as a cornerstone to play together.

Please note: individual games may have different rulesets. These rules are a default set, and in different games different rules may be needed - look at our [[Gametypes|Gametype-pages]] for further information.

=<center>Rules of our games</center>=

Playing in a team is very challenging. Imagine a team of skilled players who stick to their own individual playing style. If we want to set up a comprehensive and efficient transportation network we need to stick to certain rules.

These rules help us to understand what our teammates are doing. Also, it keeps us away from additional work caused by a lack of proper building style. If you want to join us, you are very welcome; but we request you to pay attention to our rules.

===Communication===
* '''You should be on [[IRC]] in case we need to have a discussion for which in game chat is not sufficient.'''
* We have no choice but to kick and/or ban players who are disruptive to the cooperative style of play, to make sure everyone can enjoy the game.
* Try not to disrupt the whole network. If that's necessary, talk to everyone else; so they know what's going on.
* Two people building in the same place is generally about as many as can be without a large amount of confusion. So communicate what and where you are doing something.
* For the same reason in order to make communication easier: choose the same (or at least a recognisably similar) ingame name as your IRC nick.
* If you have a special intention about something, use the ingame signs. Use them to comment out your ideas, like programmers use comments in their code. In fact, playing OTTD is like programming a system.
* ''No Sign overkill is needed!'' If you see obsolete signs, delete them (if you are not sure, keep them).
* Language is english (due to popular demand ;-) )
* We '''always''' name our hubs and add the name of the builder on the sign to ease bugtracking and communication. Look at our [[Naming_conventions|naming conventions]].

===Game Start===
Most games start with coal, because it's the resource with the best distance/profit margins. The route should go a reasonable distance (the further the better) in a (preferable) straight line. We will discuss where and how to start a game via IRC and work together to find a route that is both profitable and easy to expand. If none can be found a new map will be started. The start should be done by no more than 3 people at a time, to avoid confusion while establishing an initial profitable route.
The company color is always orange. Don't question this. It leads to nothing at all ;-)

There is a very-short but very-meaningful [[Game_Start|Game Start Guide]]. Have a quick look at that, it says more than a thousand words.

===Construction===
*Stick to our construction guides for a proper building style as long as a plan says something different. Therefore, ask some others ingame.
*Avoid having a full loan like the plague. One loan unit is needed in case the total amount of money goes into the red. If this happens too much, the company can go bankrupt. So, it's good to have one loan unit to borrow on so that this doesn't happen.
*No 90 degree turns! Trains can't take them due to our patch-settings.
*No 2*45 degree curves, due to too high speed penalties with the new train acceleration. It should and can be avoided in 99.9% of all situations. Only at some less-frequented, bad-located stations, 2*45s are acceptable. This holds true also for "chaos style".
*Stations are all equally long - depending on game type and strategy. Usually the smallest stations have 2 platforms but on larger games, like 1024x1024, you should stick to even larger stations - because of the long train running times there some queuings can occur.
*Use the "[http://wiki.openttd.org/index.php/Railway_Stations#Ro-Ro Ro-Ro]" style. Terminus stations are acceptable for eyecandy as well as less-frequented stations or in difficult terrain.
*On 2+/2+ lines ([[Guides:Glossary:Mainline|''Mainlines'']]) be sure to leave some spaces in between the two lanes (the more the better, depending on space restrictions).
*We (well most of us) drive on the right side of the road, the trains should too ;-).
*Never build industries until the entire map is connected. This is because the max industry limit could be reached accidentally, which would prevent the building of a necessary industry such as a factory or oil refinery.
*Unless stated otherwise we keep terraforming as low as possible. Moving a few tiles for a station or a curve is OK, but carving out a valley to lay your Sideline is a no-no. Also see [[Terraforming|Terraforming]]

===Network Design===
*Often, we build large mainlines (also known as 'Axis' - at least LL___RR or even more depending on the size of the map) and use them as backbones for all of the traffic. Everything is connected to those mainlines by the [[Line_hierarchy|standard line hierarchy]]. On the other hand, this can vary basing on a specific plan. Be sure to search for a sign called like "!Network plan" to gain further information. They may mention one of the proven [[Gametypes|concepts]] in order to avoid writing down everything anew.
*We build sidelines (LR) that access the mainlines via [[Guides:Glossary:Sideline_Hub|Sideline Hubs]].
*Never ever connect a station directly to the mainline. This makes a fast mainline slow. Always connect a station via a sideline.
*Try to minimize the number of sidelines. A sidelinehub is always a possible source of a jam or speed decrease. Just connect stations in a certain area via the same sideline.

===Trains===
*At the very beginning of a map we try to agree on a train length. A certain trainlength needs a certain curve radius, therefore we try to avoid different lengths.
*Shared orders are a must if more than one vehicle shares the same route.

===Public Server===
*The [[Public Server]] is a special case. Rules must be observed even more stringently than elsewhere.
*The password for the [[Public Server]] is available only from [[IRC]]. You can query the password easily via an [[IRC Commands|IRC command]] at any time.
*NEVER join the server twice. Ask others to join as well. It's a '''coop server''' - and you can hardly playing by yourself call co-operation.
*If you plan to be AFK for some reasons, please leave or join spectactors.

ProZone:Archive - Games 11 - 20

2010-05-10T23:20:46Z

Petert: Corrected order

<noinclude>{{ProZoneArchiveMenu}}</noinclude>

{{Archive_ProZone|Pro Zone Game 12|19.02.2010 - 10.05.2010|{{User|Chris Booth}}, {{User|Razaekel}}, {{User|Mark}}, {{User|^Spike^}}, {{User|OwenS}} | [[Gametype:ICE_SBahn|PAX]] |TL3|256 x 512 Temperate |r19734|#openttdcoop-GRF Pack7.3|This Pro Zone game is was a attempt to develop a Japanese style passenger network across several islands. We quite soon hit some problems with the amount of CPU power that the Japanese city set was using. this meant that we had to change the city set to total towns. we also changed the train set at this time to the DBXL set. we finnaly managed to grow the cities on each island so the map was almost completely covered by cities.With many interesting metro networks emerging. |12|Image:ProZone12.png|A View of one of the busy city stations)}}

{{Archive_ProZone|Pro Zone Game 11|04.11.2009 - 19.02.2010|{{User|Chris Booth}}, {{User|Razaekel}}, {{User|Mark}}, {{User|^Spike^}}, {{User|Damalix}} | [[Gametype:ICE_SBahn|PAX]] |TL3|256 x 512 Temperate |r19145|#openttdcoop-GRF Pack7.3|This Pro Zone game is was a attempt to develop a pax network across several islands and to grow the cities on each island so the map would be covered in cities.|11|Image:ProZone11.png|Add Picture Description}}

Quickstart/Stable

2010-05-04T21:10:25Z

Petert: !name command

Welcome to the Quckstart for the Stable competition server.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
**Respect general [http://wiki.openttd.org/Multiplayer_Rules Multiplayer rules]
*Keep the terraform to a minimum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text
*Use decent nick, no vulgar/inappropriate nick names
**You can change your nick via the console (press the key to the left of '1' to open it). Type: <code>name <new-name></code>
**You can also use the !name <newname> command
*Ask for an admin to mediate, if you have issues with another player

==Version==
We use a stable or testing version, download it from [http://openttd.org/ openttd.org]

==Recommended==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[IRC]] on [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients. ([http://irc.openttdcoop.org:6677/?channels=openttdcoop,openttdcoop.stable Webchat])

==Password==
The current password for the server is:
<pre width="15%">release</pre>

Osqc

2010-04-08T20:44:56Z

Petert: Undo revision 11461 by Adrianjackson21 (Talk) Spammer

Official Page: [http://www.openttdcoop.org/osqc http://www.openttdcoop.org/osqc]
== The Idea ==
OSQC is the #openttdcoop Scenario Quest/Competition. The main idea is to solve the quests of a given scenario and to play it. Finding a creative and good solution is another key point, because after one month we are going to nominate a winner of the monthly #osqc. The Winner will be announced and the savegame archived in a Hall of Fame. The competitive factor encourages the players to show their best skills and think about the game. #openttdcoop is not only ‘building and playing together’, it is also high quality gaming at the bleeding edge of features and possibilities in OpenTTD.

== Criteria for osqc ==
Rating range is from 10 (best) till 1 (worst)
* building skill (junctions, constructions, LB, stations, depots, network flow etc.)
* organisation (network layout, usage of different vehicle types, transporting)
* economy (transported cargo, income, number of trains/rvs/planes/ships, TL)
* tasks (how are the tasks of the quests solved)
* look&feel (low terraforming, eyecandy, beautiful constructions)
* personal opinion of the judge
* bad builder (usage of station walk, massive terraforming, low station ratings, train jams)

=== Multipliers ===
* building skill = rating * 1,5
* organisation = rating * 1,0
* economy = rating * 1,0
* tasks = rating * 1,75
* look&feel = rating * 1,25
* personal opinion = rating * 0,5
* bad builder = (-10 + rating) * 0,75

=== Final Calculation ===
[total sum of ratings by all judges] / [number of judges] = FINAL RATING

== Schedule ==
{| class="osqc_table"
! width="5%" | #
! width="40%" | Name
! width="40%" | Date
! width="20%" | Sign Up
{{osqc|1|"The Bottleneck"|01-01-2008 - 31-01-2008|[http://openttdcoop.ppcis.org/osqc Closed]}}
|}

Expect osqc #02 to come soon.

Autopilot

2010-04-06T20:10:20Z

Petert: Link to Avignon's wiki

autopilot is a [http://tcl.tk/ Tcl] script which uses Tcl's [http://expect.nist.gov/ Expect] package to interface with [http://www.openttd.org/ OpenTTD's] dedicated server console to provide network games with additional features not normally available with the game alone. This is the operator's manual for version 2.0 of autopilot.

==Branches==
===AP+===
[[Autopilot/ap+|ap+]] is a branch of Autopilot - trying to not lose too many features and to provide many more. development is at version ap+ 3.0 beta (started counting after autopilot's 2.x)

===Avignon===
[[Autopilot/Avignon|Avignon]] is a new ground-up approach of the known autopilot or ap+
it is written in TCL8.5 using some (slightly modified) modules from tcllib

Homepage: http://www.codecubes.org/wiki/Avignon

==License==
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

Additionally, this operator's manual is Copyright © 2006 Brian Ronald.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is available [http://www.gnu.org/licenses/fdl.txt here].

== Overview ==
'''autopilot''' is a modular script. It comes as a set of Tcl source files. Some of these require that additional Tcl packages be installed in order to run.

=== Base module ===
The base module consists of ''autopilot.tcl'', ''autopilot-lib.tcl'' and a language file. Alone, it provides the following features:
* Periodic automatic server password changes
* Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)
* Implementation of net_frame_freq setting in openttd.cfg
* Automatic pausing of the server when the number of connected clients is below a user-defined threshold
* Greeting of players, by name, as they join the server (up to three chat lines)
* Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server
* Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified
* adds '''version''' and '''license''' commands to console
* adds an admin pager facility to the game

'''autopilot''' takes control of the server's dedicated console. Optionally, it can allow pass-through commands so that the server's operator can use the console as normal, although this comes at the price of slightly reduced responsiveness.

=== IRC module ===
The IRC module consists of ''autopilot-irc.tcl'', and requires that tcllib is installed. When enabled, it provides the following additional features:
* Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.
* Provides channel and privmsg commands to query the players and companies on the server
* Provides channel and privmsg commands to show server version and newgrf settings
* Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server
* Provides channel and privmsg commands allowing IRC users to learn the current password
* Supports CTCP VERSION and can identify to IRC services

=== MySQL module ===
The [http://www.mysql.com/ MySQL] module consists of ''autopilot-mysql.tcl'', and requires that [http://www.xdobry.de/mysqltcl/ mysqltcl] is installed. When enabled, it provides the following additional features:
* Storage of the current server password in the database, to allow database aware applications to reveal it
* Logging of in-game chat, client joins, quits and name changes to a database, including logical separation of games and servers to allow for many servers to log to the same database
The module supports database table prefixing, to allow easy co-existence with other database applications.

=== Language ===
autopilot's messages can be easily translated to other languages by including additional language files. Version 2.0 comes with one language file, ''lang_english.tcl'', which can be copied and modified to facilitate translation. The server requires that openttd be in English (at present).

== Configuration ==
'''autopilot''' is configured through ''openttd.cfg''. If a different configuration file is to be used, it must be specified to '''autopilot''' through the OTTD_CONFIG environment variable. Included with '''autopilot''' is the file ''openttd_additional.cfg'', which contains the additional sections required to operate the script. '''autopilot''' will fail to run without this configuration.

=== IRC ===
If you wish '''autopilot''' to have its IRC nickname identified with services on your chosen network, it is necessary for the nickname to be registered in advance.

=== MySQL ===
In order to use the MySQL module, the script must have access to a properly configured MySQL server in which the tables can be found. Such configuration is beyond the scope of this document, except to say that the file ''autopilot.sql'' contains the necessary CREATE TABLE commands for a MySQL 5.0 server.

=== openttd.cfg ===
Here follows a line by line description of all the new openttd.cfg options used by '''autopilot'''. They are all specified in the form of '''option = value'''. Boolean values can be ''yes'', ''true'' or ''on'' to set a feature, and anything else to un-set it.
==== network section ====
In the <nowiki>[network]</nowiki> section, the following commands are added:
;max_companies
:Set to an integer (maximum of 8 is the default). Specify the maximum number of companies allowed in the game.
;max_players
:Set to an integer (10 is the default, maximum is 11). Specify the maximum number of players allowed to connect to the game.
;max_spectators
:Set to an integer (maximum of 10 is the default). Specify the maximum number of spectators allowed to connect to the game.
;net_frame_freq
:Set to an integer. Usual default is 1, autopilot changes the default to 2. See openttd documentation for effect.

==== autopilot section ====
In the <nowiki>[autopilot]</nowiki> section, the following commands are added:
;command
:String value. Specifies the filename of the openttd executable ('''./openttd''' for Linux, '''openttd.exe''' for Windows, etc)
;language
:String value. Selects the language file ''lang_language.tcl'' where ''language'' is the content of this setting.
;responsiveness
:Integer value. Used when the console is enabled (see below). Amount of time, in seconds, between '''autopilot''' switching its attention between the console (for command entry) and the server. Lower numbers make the server more responsive to commands and events, higher numbers decrease CPU use slightly.
;email
:String value. Specifies the email address of the admin. This can be used in variable substitution and is the email address used by the admin pager.
;url
:String value. Specifies a URL which can be used in variable subsitution.
;use_irc
:Boolean value. Specifies whether to load the IRC module.
;use_mysql
:Boolean value. Specifies whether to load the MySQL module.
;use_console
:Boolean value. Specifies whether to enable pass-through commands to the user of the console. If turned off, the server ismuch more responsive, but control can only be taken through the server's rcon facility.
;randomize_password
:Boolean value. Enables the periodic password change feature.
;password_list
:String value. Filename of a text file containing a list of possible passwords to choose from. The format should be one password per line.
;password_frequency
:Boolean value. Number of milliseconds between password changes. 300000 is 5 minutes.
;pause_level
:Integer value. '''autopilot''' will pause the game if this many clients, or less, are connected to the server.
;irc_server
:String value, used only by the IRC module. The domain name or IP address of the IRC server.
;irc_port
:Integer value, used only by the IRC module. The port on which to connect to the IRC server.
;irc_user
:String value, used only by the IRC module. The IRC username to connect with.
;irc_channel
:String value, used only by the IRC module. The IRC channel to join after connecting. Must use one of # for global channels, and @ for local channels.
;irc_bridge
:Boolean value, used only by the IRC module. Specifies whether '''autopilot''' will show the game chat in the IRC channel, and vice versa.
;irc_explicit_say
:Boolean value, used only by the IRC module. If set, IRC users must use !say to communicate with game players.
;irc_rcon
:Boolean value, used only by the IRC module. Enables use of the rcon command from IRC.
;irc_nickserv
:String value, used only by the IRC module. A string to be quoted to the server in order to authenticate to services.
;motd1
:String value. A string to be sent to game chat when a player joins the server. Uses variable substitution.
;motd2
:as motd1
;motd3
:as motd1
;recount_frequency
:Integer value. Number of milliseconds between client recounts (300000 is 5 minutes). Used to maintain an accurate count for the '''pause_level''' setting in the event that clients join or quit without messages (rare, but does happen).
;mysql_server
:String value, used only by the MySQL module. The domain name or IP address of the MySQL server.
;mysql_database
:String value, used only by the MySQL module. The name of the databse which contains the database tables.
;mysql_user
:String value, used only by the MySQL module. The user with which to log in to the database.
;mysql_pass
:String value, used only by the MySQL module. The password associated with the user.
;mysql_prefix
:String value, used only by the MySQL module. The table prefix used to distinguish autopilot's tables in the database.
;mysql_gameserver
:Integer value, used only by the MySQL module. The integer value of this server, which must be a key in the '''server''' table in the database.
;smtp_server
:String value. SMTP relay server used for the admin pager command. leave empty to disable.
===responses section===
The <nowiki>[responses]</nowiki> section is used for '''keyword = response''' style command definitions. These responses are used solely by the IRC module to provide (and override) commands in the channel and by private message. Variable substitutions are supported in the responses.

=== Variable substitutions ===
Variable substitution is a means of making responses more dynamic. They are supported in the motd1, motd2 and motd3 settings, as well as in the <nowiki>[responses]</nowiki> section. The variables are specified as all-capital keywords. Wherever one o fthese keywords is found in these settings, the keyword is replaced with a substituted string. The substitutions are as follows.
;NAME
:Only used in motd1, motd2 and motd3. This is replaced with the name of the client that has joined the server.
;COMPANIES
:Replaced with an integer, being the number of companies in the game the last time that '''autopilot''' counted them.
;EMAIL
:Replaced with the email address specified in the '''email'''setting in the <nowiki>[autopilot]</nowiki> section.
;LICENSE
:Replaced with the license string, as defined in the language file.
;PASSWORD
:Replaced with the current server password.
;PLAYERS
:Replaced with an integer, being the number of connected clients.
;URL
:Replaced with the URL specified in the '''url'''setting in the <nowiki>[autopilot]</nowiki> section.
;VERSION
:Replaced with the current autopilot version string
;OTTD
:Replaced with the current OpenTTD revision or release number.

== Use ==
Once configured, starting autopilot is simply a matter of running the file ''autopilot.tcl'' from a terminal. Optionally, the command line parameter '''load''' will load the game in ''save/game.sav''. An optional second parameter is the name of a specific saved game to load:
./autopilot.tcl
This starts a new game according to what's defined in openttd.cfg
./autopilot.tcl load
This loads and continues ''save/game.sav''
./autopilot.tcl load save/special.sav
This loads and continues ''save/special.sav''

===Chat commands===
From within the game chat, three commands are acted upon by autopilot.
!page admin
This command will attempt to send an email to the admin email address.
!version
This command will show the autopilot version to players.
show autopilot version
This command will show the autopilot version to players (and has been supported since the very first version).

===MySQL module===
Use of the MySQL server requires a little more preparation. The following steps must be taken:
#The server must be named in the server table, and its key specified in openttd.cfg
#The game must have a name in the game table, and the server's key must be inserted in the server field as a foreign key
#A record must be inserted into the setup table specifying the setting of current_game, the server's key in th server field and the key of the game in the game table as a foreign key in the value field.
There is currently no tool to do this included with '''autopilot'''.
Once this is done, '''autopilot''' will automatically log the game's chat to the chatlog table (if enabled) and will write the server password to the setup table whenever it has changed. The password will be the '''value''' field in a record where '''setting''' is ''password'' and '''server''' is the server's key, as specified in openttd.cfg.

===IRC module===
The autopilot will use it's own playername as its IRC nickname. It will attempt to join its channel. If kicked, it will not rejoin unless invited. If it is invited (to anywhere, by anybody) it will take that as its cue to attempt to join its own channel.

All commands are sent by private message or in the channel. If sent in the channel, they are preceded with an exclamation mark (!).

If IRC bridging is enabled, players can converse with the IRC channel simply by using the in-game chat.
If irc_explicit_say is disabled, IRC users can converse with players simply by talking in the IRC channel. If it is enabled, they must use the !say command in the channel to be seen in the game:
!say Hi there.
This command must also be used, even if irc_explicit_say is disabled, if an IRC user wishes what they said to be logged with the in-game chat by the MySQL module.

If irc_enable_rcon is on, then any IRC user with the rcon password can execute rcon commands on the OpenTTD server by sending a private message to the autopilot:
/msg autopilot rcon password net_frame_freq 1
This command would set the OpenTTD variable net_frame_freq to 1 if autopilot's rcon password was ''password''. '''rcon''' cannot be used in the channel.

Other commands which can be used by default, either by private message or in channel:
;version
:shows the autopilot version
;newgrf
:lists the newgrf lines you’d need in your openttd.cfg
;companies
:lists the companies that are in the game
;players
:lists the players and spectators that are in the game
;url
:gives the #openttdcoop web site address
;wiki
:gives the URL of the wiki
;blog
:gives the URL of this blog
;email
:gives the email address of an admin (er, mine, as it happens…)
;revision
:shows the revision number of the openttd server
;playercount
:shows you the number of players inthe game
;companycount
:shows you the number of companies in the game

Most of these are defined in the <nowiki>[responses]</nowiki> section of ''openttd.cfg'' and can be altered or removed by autopilot's operator. New commands can be added the same way.

The newgrf command, if disabled, will still work by private message. This is by design, and allows players to request the newgrf list from the server whilst still allowing the option of not dumping huge amounts of text into the channel.

== Windows ==
Whilst '''autopilot''' works perfectly with [http://www.activestate.com/Products/ActiveTcl/ ActiveTcl], it is unfortunate that its Expect package is unable to take control over a Windows based openttd dedicated server without modification of the latter. A modification tool is available [http://www.tt-forums.net/viewtopic.php?p=490231#p490231 in this post on tt-forums.net] which will convert the Windows openttd.exe to a console application capable of being controlled.

==Support==
Because '''autopilot''' is free software, it is provided without any warranty. That said, the author (Brian Ronald, aka Brianetta) is normally happy to provide help with '''autopilot''' to those who ask nicely.

[[Category:Guides]] [[Category:IRC]]

Quickstart/Stable

2010-04-02T13:04:05Z

Petert: /* Downloading the version */

==Stable Server==
Welcome to the Quckstart for the Stable competition server.

==What you will need==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[:Category:IRC|IRC]] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients.

==IRC Channel==
We have an IRC channel, [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable], but it is mainly for admin things. You can join, but it's not necessary.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
*Keep the terraform to a minimum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text
*Use decent nick, no vulgar/inappropriate nick names
**You can change your nick via the console (press the key to the left of '1' to open it). Type: <code>name <new-name></code>

==Version==
We use a stable version, download it from [http://openttd.org/ openttd.org]

==Password==
The current password for the server is:
<pre width="15%">release</pre>

Quickstart/Stable

2010-04-02T13:03:21Z

Petert:

==Stable Server==
Welcome to the Quckstart for the Stable competition server.

==What you will need==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[:Category:IRC|IRC]] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients.

==IRC Channel==
We have an IRC channel, [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable], but it is mainly for admin things. You can join, but it's not necessary.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
*Keep the terraform to a minimum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text
*Use decent nick, no vulgar/inappropriate nick names
**You can change your nick via the console (press the key to the left of '1' to open it). Type: <code>name <new-name></code>

==Downloading the version==
You can either go to [http://openttd.org/ openttd.org] and download the latest stable, or go to the IRC channel and type:
<pre width="50%">!dl lin|lin64|osx|win32|win64|win9x</pre>

==Password==
The current password for the server is:
<pre width="15%">release</pre>

Quickstart/Stable

2010-04-02T13:01:31Z

Petert: Remove Comunication

==Stable Server==
Welcome to the Quckstart for the Stable competition server.

==What you will need==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[:Category:IRC|IRC]] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients.

==IRC Channel==
Our IRC channel is [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable]. You will need an [[IRC|IRC client]] to join. The topic will be updated regularly with important information about the server.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
*Keep the terraform to a minimum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text
*Use decent nick, no vulgar/inappropriate nick names
**You can change your nick via the console (press the key to the left of '1' to open it). Type: <code>name <new-name></code>

==Downloading the version==
You can either go to [http://openttd.org/ openttd.org] and download the latest stable, or go to the IRC channel and type:
<pre width="50%">!dl lin|lin64|osx|win32|win64|win9x</pre>

==Password==
The current password for the server is:
<pre width="15%">release</pre>

Quickstart/Stable

2010-04-02T12:59:48Z

Petert: /* Rules */ Nicks and some spelling mistakes

==Stable Server==
Welcome to the Quckstart for the Stable competition server.

==What you will need==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[:Category:IRC|IRC]] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients.
*[[Communication]]

==IRC Channel==
Our IRC channel is [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable]. You will need an [[IRC|IRC client]] to join. The topic will be updated regularly with important information about the server.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
*Keep the terraform to a minimum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text
*Use decent nick, no vulgar/inappropriate nick names
**You can change your nick via the console (press the key to the left of '1' to open it). Type: <code>name <new-name></code>

==Downloading the version==
You can either go to [http://openttd.org/ openttd.org] and download the latest stable, or go to the IRC channel and type:
<pre width="50%">!dl lin|lin64|osx|win32|win64|win9x</pre>

==Password==
The current password for the server is:
<pre width="15%">release</pre>

Quickstart/Stable

2010-04-02T12:52:04Z

Petert: /* Stable Server */ Remove '

==Stable Server==
Welcome to the Quckstart for the Stable competition server.

==What you will need==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[:Category:IRC|IRC]] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients.
*[[Communication]]

==IRC Channel==
Our IRC channel is [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable]. You will need an [[IRC|IRC client]] to join. The topic will be updated regularly with important information about the server.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
*Keep the terraform to a minmum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text

==Downloading the version==
You can either go to [http://openttd.org/ openttd.org] and download the latest stable, or go to the IRC channel and type:
<pre width="50%">!dl lin|lin64|osx|win32|win64|win9x</pre>

==Password==
The current password for the server is:
<pre width="15%">release</pre>

Quickstart/Stable

2010-04-02T12:41:39Z

Petert: Basic page

==Stable Server==
Welcome to the Quckstart for the Stable competition server.'

==What you will need==
*[http://wiki.openttd.org/OpenTTD OpenTTD Manual]
*[[:Category:IRC|IRC]] 
*:In addition to just connecting to the IRC channel, it would be wise to pay attention to the 'topic', as it is often updated with FAQ info about the current game on the Stable Server. The topic is usually shown in the main chat window upon channel joining, and at the top of the chat window in most GUI clients.
*[[Communication]]

==IRC Channel==
Our IRC channel is [irc://irc.oftc.net/openttdcoop.stable/ #openttdcoop.stable]. You will need an [[IRC|IRC client]] to join. The topic will be updated regularly with important information about the server.

==Rules==
*Keep it fair
**Do not block other players
**Do not intentionally sabotage
*Keep the terraform to a minmum
**See [[Terraforming#Low-Terraforming|the Low TF page]] for examples
*Please, oh please, use the chat system! You can start a chat by pressing "Enter" and entering text

==Downloading the version==
You can either go to [http://openttd.org/ openttd.org] and download the latest stable, or go to the IRC channel and type:
<pre width="50%">!dl lin|lin64|osx|win32|win64|win9x</pre>

==Password==
The current password for the server is:
<pre width="15%">release</pre>

PublicServer:Archive - Games 171 - 180

2010-03-29T10:46:52Z

Petert: PSG 179 in comments

<noinclude>{{PublicServerArchiveMenu}}</noinclude>



{{Archive_PublicServer|Public Server Game 178|27.02.10-17.03.10| {{User|V453000}}, {{User|XeryusTC}}, {{User|Thraxian}}, {{User|OwenS}}, {{User|jondisti}}, {{User|Thorinbur}}, {{User|Zerpa}}, {{User|Intexon}}, {{User|Sander_Buruma}}, {{User|Pirate87}}, {{User|VictorOfSweden}}, {{User|SmatZ}}, {{User|Zuu}}, {{User|Petert}} | [[Gametype:Cargo Concept|Cargo]] | TL3 | 256x1024 | r19410 [[GRF|#openttdcoop-GRF-Pack 7.3]] | "FIRS game" says it almost all. This was quite a hard map as it was rough, watery and atop of it all very mountainous with high multiplier/slope steepness settings. The network design was an outer ring of LL_RR or LLL_RRR with inner LL_RR spokes. The outer ring was intensively used but due to massive amount of secondary industries, trains got splitted there and most of the MSHs remained an overkill. As there were many MSHs to be built even though we grouped 2 or 4 industries per MSH, the game took a very long time in game years and ended just after year 2500 with almost 1000 trains and 175 road vehicles. |178|File:PSG178.png| Oil refinery area, the most stressed secondary. }}

{{Archive_PublicServer|Public Server Game 177|18.02.10-27.02.10| {{User|Combuster}}, {{User|PeterT}}, {{User|Mitooo}}, {{User|Sietse}}, {{User|mrcool}}, {{User|Thraxian}}, {{User|OwenS}}, {{User|V453000}}, {{User|roboboy}}, {{User|jondisti}}, {{User|ed__}}, {{User|Phazorx}}, {{User|Zerpa}}, {{User|Intexon}}, {{User|Sander_Buruma}}, {{User|Grim}}, {{User|Pirate87}}, {{User|Jorl17}}, {{User|Kenix}}, {{User|VictorOfSweden}}, {{User|Qanael}}, {{User|XeryusTC}}, {{User|SmatZ}}, | [[Gametype:TGV_Concept]] | TL15 | 512x512 | r19163 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A TGV concept game in a tropical setting. The mainline was 1x1 almost all the way round due to the long trains - there were no SLs, so only BBHs and MSHs were built, focusing on speed and avoiding interruptions as per the concept. The plan also called for independent food and water networks to supply desert towns, which ended up being far more complex than the main network itself. There was a variety of styles for the supply networks, from V's crazy TL1 "anthill" (pictured) to less hectic TL5 networks. The total population ended up around 720,000, with over 1100 trains in total and 2 cities over 100 thousand inhabitants. |177|File:PSG177.png|V's anthill of insanity. Look at those cute little trains toiling away! }}

{{Archive_PublicServer|Public Server Game 176|09.02.10-18.02.10| {{User|ODM}}, {{User|Combuster}}, {{User|Mitooo}}, {{User|Fuco}}, {{User|^Spike^}}, {{User|Phazorx}}, {{User|Chris Booth}}, {{User|csuke}}, {{User|grim}}, {{User|Pirate87}}, {{User|Thraxian}}, {{User|V453000}}, {{User|sepp}}, {{User|Zerpa}} | [[Gametype:Cargo Concept|Boost]] | TL7 | 512x512 | r19145 [[GRF|#openttdcoop-GRF-Pack 7.3]] | Total boost game. As planned by Combuster, this game reached 100k goods production per month, being as good as the current record from PSG 121. The whole network had 4 parts called branches which were not connected with each other. Fail-safe SML was used to maintain the 4-6 line traffic. The drop was smartly splitted into multiple sawmill drop stations in on complex and trains were ordered by entrance and exit waypoints of the whole drop area, nicely balancing the productions of sawmills. 18 - Eighteen! lines of trains were flowing into the drop. Resulting in almost 1200 trains. |176|File:PSG176.png|The drop complex almost fitted into the one-out zoom screenshot! :D }}

{{Archive_PublicServer|Public Server Game 175|02.02.10-09.02.10| {{User|V453000}}, {{User|Combuster}}, {{User|ODM}}, {{User|XeryusTC}}, {{User|Thraxian}}, {{User|Jondisti}}, {{User|Sietse}}, {{User|Techinica}}, {{User|Qanael}}, {{User|Intexon}}, {{User|MD}} | [[Gametype:Cargo Concept|Cargo]] | TL2-5 | 512x512 | r18985 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game had a very simple plan. One ML, completely no BBHs and only LLLL_RRRR at the largest point of the ML. Nothing interesting there. More interesting was that this game actually had not only two separate networks, but also two separate plans. The general one from V453000 and the more detailed one from Combuster, which served as a clever specification of our solution to the food transfering :). The first was just a network that supplied the Food Processing Plant. Then there was another nework - the food delivery. The goal was to deliver food to all towns that require food for town growth. We went for TL3 feeders of transfer stations and from the transfers food was delivered by TL2 trains to the towns. The delivery was more interesting task than it might seem. There were various types of delivery networks, but logic based splitters seemed to work best. The game ended with 1200 trains and Food processing plant at 27540 tonnes of food per month. |175|File:PSG175.png|Maxed production of FPP and interesting stations. }}

{{Archive_PublicServer|Public Server Game 174|28.01.10-02.02.10| {{User|V453000}}, {{User|Sietse}}, {{User|Chris Booth}}, {{User|csuke}}, {{User|db48x}}, {{User|jondisti}}, {{User|Thorinbur}}, {{User|MDGrein}}, {{User|Combuster}}, {{User|haseo}}, {{User|Zerpa}}, {{User|Kenix}}, {{User|Qanael}}, | [[Gametype:PAX Concept|PAX]] | TL6 | 256 x 1024 Temperate | r18927 [[GRF|#openttdcoop-GRF-Pack 7.3]] | In the planning phase were made many plans but voting ended up with everyone-voted-for-one. Osai made a plan called "City Game". This was expected to be a network of connected cities with train ICE, buses and also planes. Only some cities had proper Sbahn, which resulted in some uselessly big cities that supported the ICE only with several thousands of pax per month. On the other hand the biggest city of this game was Gretborough, growed by Chris Booth and reaching about 108k inhabitants. This city also provided quite a lot pax to the ICE, by having a nice Sbahn. The game ended with 738 trains, 963 road vehicles, 80 aircraft and the world population reached above 1,5 million. |174|File:PSG174.png|The so-called Lake area. Grown mainly by Chris Booth, this was the most effective in providing pax to the ICE. }}

{{Archive_PublicServer|Public Server Game 173|19.01.10-28.01.10| {{User|Mark}}, {{User|Sietse}}, {{User|KenjiE20}}, {{User|Chris Booth}}, {{User|Ammler}}, {{User|XeryusTC}}, {{User|Raz}}, {{User|Sepp}}, {{User|csuke}}, {{User|db48x}}, {{User|MeisterMarkus}}, {{User|jondisti}} | [[Gametype:Cargo Concept|Cargo]] | TL3 | 1024 x 1024 Temperate | r18867 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was a replay of [http://www.openttdcoop.org/wiki/MemberZone:Archive#gameid_04 MZ04] (so called Pile Transport). We reused the plan and went for Pile Transport 2.0. The plan consisted of a grid of LL_10_RR network with many 4-way hubs. Trains were already inserted in the network while lots of BBH and MSH were being created still. The huge pickup / drop stations required many improvements to keep the massive flow of trains going. The game ended with almost 1500 trains. |173|File:PSG173.png|The huge sawmill created by V453000 creating 13k goods a month and serving over 500 trains. }}

{{Archive_PublicServer|Public Server Game 172|02.01.10-19.01.10| {{User|Mark}}, {{User|V453000}}, {{User|Chris Booth}}, {{User|Osai}}, {{User|csuke}}, {{User|Samh}}, {{User|Combuster}}, {{User|ZarenorDarkstalker}}, {{User|Techinica}}, {{User|Kolo}}, {{User|Roysvork}}, {{User|sparr}}, {{User|Zuu}}, {{User|Hyppy}}, {{User|Sietse}}, {{User|Petert}}, {{User|Iomba}}, {{User|kratt}}, {{User|jondisti}} | [[Gametype:Cargo Concept|4 Cargo SRNW]] | TL5 | 512 x 512 Sub-Tropical | r18758 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was supposed to be insane as planned. Plan by Mark, four cargo type SRNW, sidelines crossing over each other, planned high cargo capacity. The game finished quite well even though the cargos ended up quite imbalanced as people added only copper ore in the beginning of the game as the copper mines were the only industries still alive after the long voting phase. Most of the problem were the huge stations which proved that SRNW should be built with more and smaller of them. |172|File:PSG172.png| Most capacity loading station - 32 bays, TL 147 total dummy trains. It served about 8 farms.}}

{{Archive_PublicServer|Public Server Game 171|30.12.09-02.01.10| {{User|Pm}}, {{User|Mark}}, {{User|Combuster}}, {{User|KenjiE20}}, {{User|V453000}}, {{User|Sparr}}, {{User|Sam}}, {{User|ZarenorDarkstalker}}, {{User|csuke}}, {{User|Petert}}, {{User|MeisterMarkus}} | RV [[Gametype:Cargo_Concept|Cargo]] & [[Gametype:ICE SBahn|PAX]] | TL0 (RV) | 256 x 256 Sub-Arctic | r18669 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A new-year minigame. RV only, supplying two cities with food, goods and PAX from each other. In the early stages we had trouble with the very low snowline preventing from prospecting farms. After this problem solved, the game was very quick (just few days) as it was a small map and a RV game. Probably the most remarkable thing is the RV balancer which has been used a lot during the game. The game ended with 1709 road vehicles. |171|File:PSG171.png|One of the multiple-version SLH and a balancer (Chahill balancer) }}

IRC

2010-03-28T15:51:54Z

Petert: Pidgin

Talk:Two-way Prio

2010-03-17T10:27:21Z

Petert:

==Gif==
What did you use to make the animated gif? --[[User:Petert|Petert]] 00:53, 17 March 2010 (UTC)

:Gimp 2.6 of course :-) Check out this [http://www.gimp.org/tutorials/Simple_Animations/ This guide] [[User:Zerpa|Zerpa]] 08:55, 17 March 2010 (UTC)
:* Thanks Zerpa

Talk:Two-way Prio

2010-03-17T00:53:47Z

Petert: cleanup

==Gif==
What did you use to make the animated gif? --[[User:Petert|Petert]] 00:53, 17 March 2010 (UTC)

Talk:Two-way Prio

2010-03-17T00:53:33Z

Petert: Created page with 'What did you use to make the animated gif? --~~~~'

What did you use to make the animated gif? --[[User:Petert|Petert]] 00:53, 17 March 2010 (UTC)

PublicServer:Archive - Games 171 - 180

2010-03-17T00:44:44Z

Petert: Added self

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 178|27.02.10-17.03.10| {{User|V453000}}, {{User|XeryusTC}}, {{User|Thraxian}}, {{User|OwenS}}, {{User|jondisti}}, {{User|Thorinbur}}, {{User|Zerpa}}, {{User|Intexon}}, {{User|Sander_Buruma}}, {{User|Pirate87}}, {{User|VictorOfSweden}}, {{User|SmatZ}}, {{User|Zuu}}, {{User|Petert}} | [[Gametype:Cargo Concept|Cargo]] | TL3 | 256x1024 | r19410 [[GRF|#openttdcoop-GRF-Pack 7.3]] | "FIRS game" says it almost all. This was quite a hard map as it was rough, watery and atop of it all very mountainous with high multiplier/slope steepness settings. The network design was an outer ring of LL_RR or LLL_RRR with inner LL_RR spokes. The outer ring was intensively used but due to massive amount of secondary industries, trains got splitted there and most of the MSHs remained an overkill. As there were many MSHs to be built even though we grouped 2 or 4 industries per MSH, the game took a very long time in game years and ended just after year 2500 with almost 1000 trains and 175 road vehicles. |178|File:PSG178.png| Oil refinery area, the most stressed secondary. }}

{{Archive_PublicServer|Public Server Game 177|18.02.10-27.02.10| {{User|Combuster}}, {{User|PeterT}}, {{User|Mitooo}}, {{User|Sietse}}, {{User|mrcool}}, {{User|Thraxian}}, {{User|OwenS}}, {{User|V453000}}, {{User|roboboy}}, {{User|jondisti}}, {{User|ed__}}, {{User|Phazorx}}, {{User|Zerpa}}, {{User|Intexon}}, {{User|Sander_Buruma}}, {{User|Grim}}, {{User|Pirate87}}, {{User|Jorl17}}, {{User|Kenix}}, {{User|VictorOfSweden}}, {{User|Qanael}}, {{User|XeryusTC}}, {{User|SmatZ}}, | [[Gametype:TGV_Concept]] | TL15 | 512x512 | r19163 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A TGV concept game in a tropical setting. The mainline was 1x1 almost all the way round due to the long trains - there were no SLs, so only BBHs and MSHs were built, focusing on speed and avoiding interruptions as per the concept. The plan also called for independent food and water networks to supply desert towns, which ended up being far more complex than the main network itself. There was a variety of styles for the supply networks, from V's crazy TL1 "anthill" (pictured) to less hectic TL5 networks. The total population ended up around 720,000, with over 1100 trains in total and 2 cities over 100 thousand inhabitants. |177|File:PSG177.png|V's anthill of insanity. Look at those cute little trains toiling away! }}

{{Archive_PublicServer|Public Server Game 176|09.02.10-18.02.10| {{User|ODM}}, {{User|Combuster}}, {{User|Mitooo}}, {{User|Fuco}}, {{User|^Spike^}}, {{User|Phazorx}}, {{User|Chris Booth}}, {{User|csuke}}, {{User|grim}}, {{User|Pirate87}}, {{User|Thraxian}}, {{User|V453000}}, {{User|sepp}}, {{User|Zerpa}} | [[Gametype:Cargo Concept|Boost]] | TL7 | 512x512 | r19145 [[GRF|#openttdcoop-GRF-Pack 7.3]] | Total boost game. As planned by Combuster, this game reached 100k goods production per month, being as good as the current record from PSG 121. The whole network had 4 parts called branches which were not connected with each other. Fail-safe SML was used to maintain the 4-6 line traffic. The drop was smartly splitted into multiple sawmill drop stations in on complex and trains were ordered by entrance and exit waypoints of the whole drop area, nicely balancing the productions of sawmills. 18 - Eighteen! lines of trains were flowing into the drop. Resulting in almost 1200 trains. |176|File:PSG176.png|The drop complex almost fitted into the one-out zoom screenshot! :D }}

{{Archive_PublicServer|Public Server Game 175|02.02.10-09.02.10| {{User|V453000}}, {{User|Combuster}}, {{User|ODM}}, {{User|XeryusTC}}, {{User|Thraxian}}, {{User|Jondisti}}, {{User|Sietse}}, {{User|Techinica}}, {{User|Qanael}}, {{User|Intexon}}, {{User|MD}} | [[Gametype:Cargo Concept|Cargo]] | TL2-5 | 512x512 | r18985 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game had a very simple plan. One ML, completely no BBHs and only LLLL_RRRR at the largest point of the ML. Nothing interesting there. More interesting was that this game actually had not only two separate networks, but also two separate plans. The general one from V453000 and the more detailed one from Combuster, which served as a clever specification of our solution to the food transfering :). The first was just a network that supplied the Food Processing Plant. Then there was another nework - the food delivery. The goal was to deliver food to all towns that require food for town growth. We went for TL3 feeders of transfer stations and from the transfers food was delivered by TL2 trains to the towns. The delivery was more interesting task than it might seem. There were various types of delivery networks, but logic based splitters seemed to work best. The game ended with 1200 trains and Food processing plant at 27540 tonnes of food per month. |175|File:PSG175.png|Maxed production of FPP and interesting stations. }}

{{Archive_PublicServer|Public Server Game 174|28.01.10-02.02.10| {{User|V453000}}, {{User|Sietse}}, {{User|Chris Booth}}, {{User|csuke}}, {{User|db48x}}, {{User|jondisti}}, {{User|Thorinbur}}, {{User|MDGrein}}, {{User|Combuster}}, {{User|haseo}}, {{User|Zerpa}}, {{User|Kenix}}, {{User|Qanael}}, | [[Gametype:PAX Concept|PAX]] | TL6 | 256 x 1024 Temperate | r18927 [[GRF|#openttdcoop-GRF-Pack 7.3]] | In the planning phase were made many plans but voting ended up with everyone-voted-for-one. Osai made a plan called "City Game". This was expected to be a network of connected cities with train ICE, buses and also planes. Only some cities had proper Sbahn, which resulted in some uselessly big cities that supported the ICE only with several thousands of pax per month. On the other hand the biggest city of this game was Gretborough, growed by Chris Booth and reaching about 108k inhabitants. This city also provided quite a lot pax to the ICE, by having a nice Sbahn. The game ended with 738 trains, 963 road vehicles, 80 aircraft and the world population reached above 1,5 million. |174|File:PSG174.png|The so-called Lake area. Grown mainly by Chris Booth, this was the most effective in providing pax to the ICE. }}

{{Archive_PublicServer|Public Server Game 173|19.01.10-28.01.10| {{User|Mark}}, {{User|Sietse}}, {{User|KenjiE20}}, {{User|Chris Booth}}, {{User|Ammler}}, {{User|XeryusTC}}, {{User|Raz}}, {{User|Sepp}}, {{User|csuke}}, {{User|db48x}}, {{User|MeisterMarkus}}, {{User|jondisti}} | [[Gametype:Cargo Concept|Cargo]] | TL3 | 1024 x 1024 Temperate | r18867 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was a replay of [http://www.openttdcoop.org/wiki/MemberZone:Archive#gameid_04 MZ04] (so called Pile Transport). We reused the plan and went for Pile Transport 2.0. The plan consisted of a grid of LL_10_RR network with many 4-way hubs. Trains were already inserted in the network while lots of BBH and MSH were being created still. The huge pickup / drop stations required many improvements to keep the massive flow of trains going. The game ended with almost 1500 trains. |173|File:PSG173.png|The huge sawmill created by V453000 creating 13k goods a month and serving over 500 trains. }}

{{Archive_PublicServer|Public Server Game 172|02.01.10-19.01.10| {{User|Mark}}, {{User|V453000}}, {{User|Chris Booth}}, {{User|Osai}}, {{User|csuke}}, {{User|Samh}}, {{User|Combuster}}, {{User|ZarenorDarkstalker}}, {{User|Techinica}}, {{User|Kolo}}, {{User|Roysvork}}, {{User|sparr}}, {{User|Zuu}}, {{User|Hyppy}}, {{User|Sietse}}, {{User|Petert}}, {{User|Iomba}}, {{User|kratt}}, {{User|jondisti}} | [[Gametype:Cargo Concept|4 Cargo SRNW]] | TL5 | 512 x 512 Sub-Tropical | r18758 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was supposed to be insane as planned. Plan by Mark, four cargo type SRNW, sidelines crossing over each other, planned high cargo capacity. The game finished quite well even though the cargos ended up quite imbalanced as people added only copper ore in the beginning of the game as the copper mines were the only industries still alive after the long voting phase. Most of the problem were the huge stations which proved that SRNW should be built with more and smaller of them. |172|File:PSG172.png| Most capacity loading station - 32 bays, TL 147 total dummy trains. It served about 8 farms.}}

{{Archive_PublicServer|Public Server Game 171|30.12.09-02.01.10| {{User|Pm}}, {{User|Mark}}, {{User|Combuster}}, {{User|KenjiE20}}, {{User|V453000}}, {{User|Sparr}}, {{User|Sam}}, {{User|ZarenorDarkstalker}}, {{User|csuke}}, {{User|Petert}}, {{User|MeisterMarkus}} | RV [[Gametype:Cargo_Concept|Cargo]] & [[Gametype:ICE SBahn|PAX]] | TL0 (RV) | 256 x 256 Sub-Arctic | r18669 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A new-year minigame. RV only, supplying two cities with food, goods and PAX from each other. In the early stages we had trouble with the very low snowline preventing from prospecting farms. After this problem solved, the game was very quick (just few days) as it was a small map and a RV game. Probably the most remarkable thing is the RV balancer which has been used a lot during the game. The game ended with 1709 road vehicles. |171|File:PSG171.png|One of the multiple-version SLH and a balancer (Chahill balancer) }}

Autopilot/Avignon

2010-03-07T18:33:07Z

Petert: /* [IRC] */ Typo

{{beta}}
==Avignon==
Avignon is an ground-up re-write of [[ap+]] with an emphasis on being modular.

It is available from [http://www.codecubes.org CodeCubes]. 

== Configuration ==

Checkout via
svn co http://svn.codecubes.org/avignon/trunk
svn co http://svn.codecubes.org/avignon/tags/avignon-0.1a1

Once you have a checkout, configuration of Avignon is handled by making a copy of ''config/default.ini'' to ''config/user.ini''

=== [IRC] ===
important settings are
* auto.connect = no 
set this to yes, to avoid having to make it connect everytime (you may want to leave this on 'no' till you have everything set)
* network.host = HOSTNAME
* network.pass =
* network.port = 6667
* nick = NICKNAME
* nick.alternatives = NICKNAME2 NICKNAME3
* channels = #CHANNEL #CHANNEL2
* channels.key.#CHANNEL = PASSWORD
* nickserv = NICKSERV IDENTIFY {password} 
These should be straightforward enough
* command.char = ! 
trigger character for the bot on IRC

=== [plugins] ===
* load = Alias DemoPlugin 
Sets the plugins loaded on startup
* prefer.irc.COMMAND = PLUGIN 
if there are multiple versions of a command this sets the default plugin used. 
i.e. 'version' is in both Avignon and OpenTTD

== Starting a Server OpenTTD ==

The OpenTTD app is subject to rapid change, see [http://www.codecubes.org/browser/avignon/trunk/extensions/apps/OpenTTD/readme.txt readme.txt] for lastest info

The following was correct at time of writing (07 March 2010).

To load issue
<code>load OpenTTD</code>
if not alread loaded by default. (see [[#.5Bplugins.5D|[plugins]]])

The OpenTTD app, looks for an openttd install in ./openttd relative to avignon.tcl
<code>openttd start</code>
will start the OpenTTD server.
<code>openttd load [savegame_here.sav]</code>
will load a game. There is no need to give the ''save/savegame.sav'' path, as the app assumes saves are in save. 
!Though currently, loading anything other than game.sav sends a bad command and may fail to load

OpenTTD's app has a few settings, the default will normally suffice, but can be overridden by adding a new section to the user.ini

=== [OpenTTD] ===
Th defaults should be fine, but you may like to tweak;
* irc.bridge = <#irc_channel> 
This is probably the one you want to attck first, the #channel should already be joined by setting it in the [[#.5BIRC.5D|[irc]]] section.
* password.randomize = <yes>|<no> 
Do you want to enable password randomzing (default: no)
* password.file = <path/to/file>
The file storing passwords; one word per line (default: ./extensions/apps/OpenTTD/words6)
* password.frequency = <int> 
Frequency of password change in seconds (default: 300)

Autopilot/Avignon

2010-03-07T17:08:59Z

Petert: /* Starting a Server OpenTTD */ Wrong spacing caused some <pre> things to fail

==Avignon==
Avignon is an advanced re-write of [[ap+]] which is easily extendable with plugins.

==Basic Usage==
First of all, checkout the source from the trunk repo.
<pre>svn co http://svn.codecubes.org/avignon/trunk/ avignon</pre>

This will checkout the source to ''./avignon/''

Once you have that set up, configure Avignon with ''default.ini'' located in ''./config''.

To connect your bot to IRC, make sure you have set all the settings in [irc], and type "connect".

==Starting a Server OpenTTD==
To start a server, make sure you have all necesarry OpenTTD binaries in ''./avignon/openttd/''
Then, load the OpenTTD module
<code>load OpenTTD</code>
Alternatively, you can auto-load the plugin on startup, just set it in the config:
<pre>[plugins]
...
load = Alias DemoPlugin
load = OpenTTD</pre>
Then, either in IRC or the Terminal window, type:
<pre>start</pre>

and it will start the OpenTTD server. You can configure it with !rcon or in openttd.cfg.

Autopilot/Avignon

2010-03-07T17:07:48Z

Petert: /* Starting a Server OpenTTD */ Start

==Avignon==
Avignon is an advanced re-write of [[ap+]] which is easily extendable with plugins.

==Basic Usage==
First of all, checkout the source from the trunk repo.
<pre>svn co http://svn.codecubes.org/avignon/trunk/ avignon</pre>

This will checkout the source to ''./avignon/''

Once you have that set up, configure Avignon with ''default.ini'' located in ''./config''.

To connect your bot to IRC, make sure you have set all the settings in [irc], and type "connect".

==Starting a Server OpenTTD==
To start a server, make sure you have all necesarry OpenTTD binaries in ''./avignon/openttd/''
Then, load the OpenTTD module
<code>load OpenTTD</code>
Alternatively, you can auto-load the plugin on startup, just set it in the config:
<pre>[plugins]
...
load = Alias DemoPlugin
load = OpenTTD</pre>
Then, either in IRC or the Terminal window, type:
<pre>start</pre>
and it will start the OpenTTD server. You can configure it with !rcon or in openttd.cfg.

Autopilot/Avignon

2010-03-07T16:58:51Z

Petert: Basic Layout of Avignon's help page

X-Sync

2010-03-01T03:30:16Z

Petert: Redirect to Line_sync#X-Sync

#REDIRECT [[Line_sync#X-Sync]]

File talk:TBDS.gif

2010-03-01T03:25:19Z

Petert: Gif animator

==Gif Animator==
Hello Phazorx,
I was wondering, what gif animator did you use to make this? Was it free?
--[[User:Petert|Petert]] 03:25, 1 March 2010 (UTC)

PublicServer:Archive - Games 171 - 180

2010-02-27T20:53:11Z

Petert: PSG 177 Archived

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 177|18.02.10-27.02.10| {{User|Combuster}}, {{User|PeterT}}, {{User|Mitooo}}, {{User|Sietse}}, {{User|mrcool}}, {{User|Thraxian}}, {{User|OwenS}}, {{User|V453000}}, {{User|roboboy}}, {{User|jondisti}}, {{User|ed__}}, {{User|Phazorx}}, {{User|Zerpa}}, {{User|Intexon}}, {{User|Sander_Buruma}}, {{User|Grim}}, {{User|Pirate87}}, {{User|Jorl17}}, {{User|Kenix}}, {{User|VictorOfSweden}}, {{User|Qanael}}, {{User|XeryusTC}}, {{User|SmatZ}}, | [[Gametype:TGV_Concept]] | TL15 | 512x512 | r19163 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A TGV concept game in a tropical setting. The mainline was 1x1 almost all the way round due to the long trains - there were no SLs, so only BBHs and MSHs were built, focusing on speed and avoiding interruptions as per the concept. The plan also called for independent food and water networks to supply desert towns, which ended up being far more complex than the main network itself. There was a variety of styles for the supply networks, from V's crazy TL1 "anthill" (pictured) to less hectic TL5 networks. The total population ended up around 720,000, with over 1100 trains in total and 2 cities over 100 thousand inhabitants. |177|File:PSG177.png|V's anthill of insanity. Look at those cute little trains toiling away! }}

{{Archive_PublicServer|Public Server Game 176|09.02.10-18.02.10| {{User|ODM}}, {{User|Combuster}}, {{User|Mitooo}}, {{User|Fuco}}, {{User|^Spike^}}, {{User|Phazorx}}, {{User|Chris Booth}}, {{User|csuke}}, {{User|grim}}, {{User|Pirate87}}, {{User|Thraxian}}, {{User|V453000}}, {{User|sepp}}, {{User|Zerpa}} | [[Gametype:Cargo Concept|Boost]] | TL7 | 512x512 | r19145 [[GRF|#openttdcoop-GRF-Pack 7.3]] | Total boost game. As planned by Combuster, this game reached 100k goods production per month, being as good as the current record from PSG 121. The whole network had 4 parts called branches which were not connected with each other. Fail-safe SML was used to maintain the 4-6 line traffic. The drop was smartly splitted into multiple sawmill drop stations in on complex and trains were ordered by entrance and exit waypoints of the whole drop area, nicely balancing the productions of sawmills. 18 - Eighteen! lines of trains were flowing into the drop. Resulting in almost 1200 trains. |176|File:PSG176.png|The drop complex almost fitted into the one-out zoom screenshot! :D }}

{{Archive_PublicServer|Public Server Game 175|02.02.10-09.02.10| {{User|V453000}}, {{User|Combuster}}, {{User|ODM}}, {{User|XeryusTC}}, {{User|Thraxian}}, {{User|Jondisti}}, {{User|Sietse}}, {{User|Techinica}}, {{User|Qanael}}, {{User|Intexon}}, {{User|MD}} | [[Gametype:Cargo Concept|Cargo]] | TL2-5 | 512x512 | r18985 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game had a very simple plan. One ML, completely no BBHs and only LLLL_RRRR at the largest point of the ML. Nothing interesting there. More interesting was that this game actually had not only two separate networks, but also two separate plans. The general one from V453000 and the more detailed one from Combuster, which served as a clever specification of our solution to the food transfering :). The first was just a network that supplied the Food Processing Plant. Then there was another nework - the food delivery. The goal was to deliver food to all towns that require food for town growth. We went for TL3 feeders of transfer stations and from the transfers food was delivered by TL2 trains to the towns. The delivery was more interesting task than it might seem. There were various types of delivery networks, but logic based splitters seemed to work best. The game ended with 1200 trains and Food processing plant at 27540 tonnes of food per month. |175|File:PSG175.png|Maxed production of FPP and interesting stations. }}

{{Archive_PublicServer|Public Server Game 174|28.01.10-02.02.10| {{User|V453000}}, {{User|Sietse}}, {{User|Chris Booth}}, {{User|csuke}}, {{User|db48x}}, {{User|jondisti}}, {{User|Thorinbur}}, {{User|MDGrein}}, {{User|Combuster}}, {{User|haseo}}, {{User|Zerpa}}, {{User|Kenix}}, {{User|Qanael}}, | [[Gametype:PAX Concept|PAX]] | TL6 | 256 x 1024 Temperate | r18927 [[GRF|#openttdcoop-GRF-Pack 7.3]] | In the planning phase were made many plans but voting ended up with everyone-voted-for-one. Osai made a plan called "City Game". This was expected to be a network of connected cities with train ICE, buses and also planes. Only some cities had proper Sbahn, which resulted in some uselessly big cities that supported the ICE only with several thousands of pax per month. On the other hand the biggest city of this game was Gretborough, growed by Chris Booth and reaching about 108k inhabitants. This city also provided quite a lot pax to the ICE, by having a nice Sbahn. The game ended with 738 trains, 963 road vehicles, 80 aircraft and the world population reached above 1,5 million. |174|File:PSG174.png|The so-called Lake area. Grown mainly by Chris Booth, this was the most effective in providing pax to the ICE. }}

{{Archive_PublicServer|Public Server Game 173|19.01.10-28.01.10| {{User|Mark}}, {{User|Sietse}}, {{User|KenjiE20}}, {{User|Chris Booth}}, {{User|Ammler}}, {{User|XeryusTC}}, {{User|Raz}}, {{User|Sepp}}, {{User|csuke}}, {{User|db48x}}, {{User|MeisterMarkus}}, {{User|jondisti}} | [[Gametype:Cargo Concept|Cargo]] | TL3 | 1024 x 1024 Temperate | r18867 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was a replay of [http://www.openttdcoop.org/wiki/MemberZone:Archive#gameid_04 MZ04] (so called Pile Transport). We reused the plan and went for Pile Transport 2.0. The plan consisted of a grid of LL_10_RR network with many 4-way hubs. Trains were already inserted in the network while lots of BBH and MSH were being created still. The huge pickup / drop stations required many improvements to keep the massive flow of trains going. The game ended with almost 1500 trains. |173|File:PSG173.png|The huge sawmill created by V453000 creating 13k goods a month and serving over 500 trains. }}

{{Archive_PublicServer|Public Server Game 172|02.01.10-19.01.10| {{User|Mark}}, {{User|V453000}}, {{User|Chris Booth}}, {{User|Osai}}, {{User|csuke}}, {{User|Samh}}, {{User|Combuster}}, {{User|ZarenorDarkstalker}}, {{User|Techinica}}, {{User|Kolo}}, {{User|Roysvork}}, {{User|sparr}}, {{User|Zuu}}, {{User|Hyppy}}, {{User|Sietse}}, {{User|Petert}}, {{User|Iomba}}, {{User|kratt}}, {{User|jondisti}} | [[Gametype:Cargo Concept|4 Cargo SRNW]] | TL5 | 512 x 512 Sub-Tropical | r18758 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was supposed to be insane as planned. Plan by Mark, four cargo type SRNW, sidelines crossing over each other, planned high cargo capacity. The game finished quite well even though the cargos ended up quite imbalanced as people added only copper ore in the beginning of the game as the copper mines were the only industries still alive after the long voting phase. Most of the problem were the huge stations which proved that SRNW should be built with more and smaller of them. |172|File:PSG172.png| Most capacity loading station - 32 bays, TL 147 total dummy trains. It served about 8 farms.}}

{{Archive_PublicServer|Public Server Game 171|30.12.09-02.01.10| {{User|Pm}}, {{User|Mark}}, {{User|Combuster}}, {{User|KenjiE20}}, {{User|V453000}}, {{User|Sparr}}, {{User|Sam}}, {{User|ZarenorDarkstalker}}, {{User|csuke}}, {{User|Petert}}, {{User|MeisterMarkus}} | RV [[Gametype:Cargo_Concept|Cargo]] & [[Gametype:ICE SBahn|PAX]] | TL0 (RV) | 256 x 256 Sub-Arctic | r18669 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A new-year minigame. RV only, supplying two cities with food, goods and PAX from each other. In the early stages we had trouble with the very low snowline preventing from prospecting farms. After this problem solved, the game was very quick (just few days) as it was a small map and a RV game. Probably the most remarkable thing is the RV balancer which has been used a lot during the game. The game ended with 1709 road vehicles. |171|File:PSG171.png|One of the multiple-version SLH and a balancer (Chahill balancer) }}

IRC Commands

2010-02-23T01:39:20Z

Petert: !auto command

{{update}}
In our channel #openttdcoop there are 2 bots active. One bot is called '''"publicserver"''' and whenever it is on IRC you know that there is a [[Public Server]] Game running. The second bot is called '''"Webster"''' which is giving us some additional features to the IRC channel itself.

'''publicserver''' understands several commands and gives you the the ability to communicate with people on The Public Server via our IRC channel. Just type this command in your chatline. You can also send commands to publicserver by private message (/msg) if you do not wish to disturb the flow of the channel.

<center>
{| border="1" style="border: 1px solid black;" cellpadding="5" cellspacing="0" align="center" width="75%"
|- style="border: 1px solid black;"
! style="background:#800000 ;" width="25%" | Command
! style="background:#800000 ;" width="75%"| Description
{{IRC_Channel_Commands|!archive|Shows the link to our saved games archive}}
{{IRC_Channel_Commands|!auto|Sets auto-pause}}
{{IRC_Channel_Commands|!blog|Shows the link to our blog}}
{{IRC_Channel_Commands|!companies|Lists the companies on the [[Public Server]] (should just be one)}}
{{IRC_Channel_Commands|!companycount|Tells you the number of companies in the game, mostly only one in our games though}}
{{IRC_Channel_Commands|!curve|Gives you a link that contains the speed/ curve length ratio}}
{{IRC_Channel_Commands|!date|Shows current game date}}
{{IRC_Channel_Commands|!download|Shows you the download links of the current OpenTTD version we use}}
{{IRC_Channel_Commands|!grf|Returns the URL of the [[GRF|GRF-Info-Page]]}}
{{IRC_Channel_Commands|!help|URL to access this help-page}}
{{IRC_Channel_Commands|!info|Shows game details.}}
{{IRC_Channel_Commands|!ip|Shows IP-Address and Port of the server}}
{{IRC_Channel_Commands|!junctionary|Show the link to our Junctionary}}
{{IRC_Channel_Commands|!password|Shows the actual password of the [[Public Server]] in our channel}}
{{IRC_Channel_Commands|!playercount|Tells you how many people are playing on the [[Public Server]]}}
{{IRC_Channel_Commands|!players|Lists the people who are playing on the [[Public Server]], if any}}
{{IRC_Channel_Commands|!revision|The version of OpenTTD}}
{{IRC_Channel_Commands|!rss|Show the link to our RSS-feed}}
{{IRC_Channel_Commands|!save|Saves the game on [[Public Server]] }}
{{IRC_Channel_Commands|!svn|Shows the command to update the client via SVN}}
{{IRC_Channel_Commands|!url|Shows the link to the [[Public Server]] helppage}}
{{IRC_Channel_Commands|!version|The version of Autopilot}}
{{IRC_Channel_Commands|!wiki|Shows the link to our wiki}}
{{IRC_Channel_Commands|!rules|Shows the link to the playing rules of this server}}
{{IRC_Channel_Commands|!rcon <command>|Execute a command on the console (requires channel op)}}
{{IRC_Channel_Commands|!trains <number>|set max_trains to <number> (requires channel op)}}
{{IRC_Channel_Commands|!pause|pause the game (requires channel op)}}
|}
</center>

'''Webster''' logs our channel and gives you some other nice stuff: (prefix for commands: @) 
For a full list of Webster's features and commands see the [[User:KenjiE20/Webster|full help]] page.
<center>
{| border="1" style="border: 1px solid black;" cellpadding="5" cellspacing="0" align="center" width="75%"
|- style="border: 1px solid black;"
! style="background:#800000 ;" width="25%" | Command
! style="background:#800000 ;" width="75%"| Description
{{IRC_Channel_Commands|@logs|Shows channel logs}}
{{IRC_Channel_Commands|@seen username|Shows, when a user was online last time and sends him a msg when returning}}
{{IRC_Channel_Commands|@wiki <topic>|Searches the wiki for <topic> and returns the title search address. If <topic> is an article, the link will redirect you to it.}}
|}
</center>

[[Category:Guides]]
[[Category:IRC]]

AutoPilot/ap+

2010-02-06T23:07:57Z

Petert: Redirected page to Autopilot/ap+

#REDIRECT [[Autopilot/ap+]]

AutoPilot

2010-02-06T23:00:09Z

Petert: Redirected page to Autopilot

#REDIRECT [[Autopilot]]

Autopilot/ap+

2010-02-06T19:12:24Z

Petert: /* license */ Capitalization

{|
|
= ap+ =
|rowspan=3|__TOC__
|-
|
== About ==
ap+ is a branch of [[Autopilot]] - Trying to not lose too many features while providing many more. Development is at version ap+ 3.0-beta (Started counting after AutoPilot's 2.x)
|-
|

== License ==
for license information please see [[Autopilot#License]]
|}

== features ==
=== standard ===
features from autopilot:
* Periodic automatic server password changes
* <s>Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)</s>
* Implementation of net_frame_freq setting in openttd.cfg
* Automatic pausing of the server when the number of connected clients is below a user-defined threshold
* Greeting of players, by name, as they join the server (up to three chat lines)
* Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server
* Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified
* adds '''version''' and '''license''' commands to console
* adds an admin pager facility to the game

features introduced in ap+:
* callback environment (used for all !commands and callbacks)
* custom in-game !commands (see [[#custom commands|custom !commands]] for more details)
* callback on client joining the game (MOTD now takes place in here and can be sent to the new client privately)
* callback on changed server password

=== irc ===
requires: tcllib
features from autopilot:
* Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.
* Provides channel and privmsg commands to query the players and companies on the server
* Provides channel and privmsg commands to show server version and newgrf settings
* Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server
* Provides channel and privmsg commands allowing IRC users to learn the current password
* Supports CTCP VERSION and can identify to IRC services

features added in ap+:
* !rcon command can now be used by channel op's (from channel or privmsg) without rcon password (e.g. !rcon pause)
* custom !commands (see [[#custom commands|custom !commands]] for more details)
* callback on kick (autopilot/scripts/callback/on_irc_kick.tcl) auto-rejoin after kick now takes place here
* callback on irc connection established (autopilot/scripts/callback/on_irc_connect.tcl) (after MOTD)
* !leave command (leave the channel, make bot rejoin with /invite)

features planed for ap+:
* capture console output and return to the command issueing irc client
* private chat between irc client and game client

=== mysql ===
unchanged, see [[Autopilot#MySQL module]]

=== signals ===
requires [http://tclx.sf.net tclx]
ap+ provides kill signal catching and sourcing files from autopilot/signals/ appropriately
please note that not all os's support all the signals that ap+ has support for. ap+ will filter the unsupported signals out of the list and output a warning. bin/ap-signal.sh links the kill signals to actions their respective signal tcl script performes (making it easier to determin what signal to send)
(e.g. bin/ap-signal.sh IRC_QUIT will disconnect form the irc server)

== custom commands ==
custom commands are sourced on every call, meanting they can be edited without needing ap+ to be restarted / rehashed. they are executed in the callback namespace (see [[#callbacks|callbacks]] for more details)

ap+
`-- autopilot
`-- scripts
|-- callback (callback files, creating your own has no affect)
|-- game (!commands, only accessible from the game)
|-- global (!commands, accessible from game and irc)
`-- irc (!commands, only accessible from irc)

place your custom <command>.tcl script into the appropriate folder, and note - currently a script can cause ap+ to crasch or lose irc connection - so test them well before going live ;-)

== callbacks ==
custom !commands and callbacks all take place in the same namespace, namely ::ap::callback. dont overwrite it, dont create child namespaces - unless you know what you are doing ;-)

direct callbacks (executed on a certain event) are the following:
autopilot/scripts/callback/on_irc_connect.tcl
when the irc connection has been established (rfc conform, after end of /MOTD has been received)
autopilot/scripts/callback/on_irc_kick.tcl
when the bot has been kicked (default is to rejoin the channel immediately)
autopilot/scripts/callback/on_game_join.tcl
when a client joins the game, this allows to send an in-game MOTD to the client privately
autopilot/scripts/callback/on_game_serverpw.tcl
when autopilot changes the server password (not when the password is changed manually)

=== callback environment commands ===
[who]
returns a string, nick of who called the command
[private]
returns a boolean (true or false) depending on the command being issued in private or public chat
(callback files - as in those in autopilot/scripts/callback - all are set to public)
[target]
returns a string, the namespace of the calling environment (e.g. ::mod_irc::say or ::ap::game::say)
mainly for internal use only
[numArgs]
number of args passed to the callback
[getArg <number>]
get the argument numbered <number>
0 is the name of the command itself, so your script arguments will most likely be startig with 1
if you fetch an argument that does not exist, an empty string is returned
<number> may also be end or end-<number> to count from the back
[getArgs [<start=0>] [<end=end>]]
start must be < end, can take any number or end-<number>, defaults to 0 (first element)
end must be > start, can take any nymber or end or end-<number>, defaults to end (last element)
say::public "message"
sends "message" to the public chat of the originating call
e.g. if !command was issued in irc, say::public will chat to the public irc channel
say::private "message"
send "message" to [who] in private
say::reply "message"
will reply to [who] (if command was issued publicly, reply in public. if command was issued privately reply privately)

=== global ap+ commands ===
::ap::say::everywhere "message"
send "message" to all possible outlets (game/irc/mysql)
::ap::say::fromGame "message"
same as ::ap::say::everywyere, jsut dont send "message" to the game

::ap::game::pause
pause the game
::ap::game::unpause
unpause the game
::ap::game::save <savename>
save the game to the file <savename>.sav (if <savename> is not specified, it saves to game.sav)
::ap::game::console "command\r"
send command to the dedicated console (please note the \r it gives the console command it's life!)
::ap::game::say::public [who] "message"
say "message" publicly in the game (use this if say::public would send to irc for example)
only use [who] if you want to address [who] prefixing your message with "[who]: "

::ap::func::map_string "string"
map certain strings to values
::ap::func::getClientId [who]
get the in-game client id from a nick name (returns 0 if [who] is not found in the clients list)

=== irc related commands ===
::mod_irc::say::public [who] "message"
force say something in the irc channel (only pass [who] if you want to address someone, see above)
::mod_irc::nickIsOp [who]
returns a boolean, check if [who] is op in the irc channel

NOTE:
only use irc related commands from irc commands (e.g. files in autopilot/scripts/irc/<command>.tcl)
or wrap them in namespace checks
if {[namespace exists ::mod_irc]} {
# your code here
}
Note:
as i am working on a cleaner callback environment please note that these details are bound to change / expand

==useful commands==
find useful custom commands at http://pub.dihedral.de/openttd/ap+

==svn==
svn co http://svn.openttdcoop.org/tools/autopilot/branches/ap+

Autopilot/ap+

2010-02-06T19:04:42Z

Petert: /* about */

{|
|
= ap+ =
|rowspan=3|__TOC__
|-
|
== About ==
ap+ is a branch of [[Autopilot]] - Trying to not lose too many features while providing many more. Development is at version ap+ 3.0-beta (Started counting after AutoPilot's 2.x)
|-
|

== license ==
for license information please see [[Autopilot#License]]
|}
== features ==
=== standard ===
features from autopilot:
* Periodic automatic server password changes
* <s>Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)</s>
* Implementation of net_frame_freq setting in openttd.cfg
* Automatic pausing of the server when the number of connected clients is below a user-defined threshold
* Greeting of players, by name, as they join the server (up to three chat lines)
* Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server
* Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified
* adds '''version''' and '''license''' commands to console
* adds an admin pager facility to the game

features introduced in ap+:
* callback environment (used for all !commands and callbacks)
* custom in-game !commands (see [[#custom commands|custom !commands]] for more details)
* callback on client joining the game (MOTD now takes place in here and can be sent to the new client privately)
* callback on changed server password

=== irc ===
requires: tcllib
features from autopilot:
* Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.
* Provides channel and privmsg commands to query the players and companies on the server
* Provides channel and privmsg commands to show server version and newgrf settings
* Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server
* Provides channel and privmsg commands allowing IRC users to learn the current password
* Supports CTCP VERSION and can identify to IRC services

features added in ap+:
* !rcon command can now be used by channel op's (from channel or privmsg) without rcon password (e.g. !rcon pause)
* custom !commands (see [[#custom commands|custom !commands]] for more details)
* callback on kick (autopilot/scripts/callback/on_irc_kick.tcl) auto-rejoin after kick now takes place here
* callback on irc connection established (autopilot/scripts/callback/on_irc_connect.tcl) (after MOTD)
* !leave command (leave the channel, make bot rejoin with /invite)

features planed for ap+:
* capture console output and return to the command issueing irc client
* private chat between irc client and game client

=== mysql ===
unchanged, see [[Autopilot#MySQL module]]

=== signals ===
requires [http://tclx.sf.net tclx]
ap+ provides kill signal catching and sourcing files from autopilot/signals/ appropriately
please note that not all os's support all the signals that ap+ has support for. ap+ will filter the unsupported signals out of the list and output a warning. bin/ap-signal.sh links the kill signals to actions their respective signal tcl script performes (making it easier to determin what signal to send)
(e.g. bin/ap-signal.sh IRC_QUIT will disconnect form the irc server)

== custom commands ==
custom commands are sourced on every call, meanting they can be edited without needing ap+ to be restarted / rehashed. they are executed in the callback namespace (see [[#callbacks|callbacks]] for more details)

ap+
`-- autopilot
`-- scripts
|-- callback (callback files, creating your own has no affect)
|-- game (!commands, only accessible from the game)
|-- global (!commands, accessible from game and irc)
`-- irc (!commands, only accessible from irc)

place your custom <command>.tcl script into the appropriate folder, and note - currently a script can cause ap+ to crasch or lose irc connection - so test them well before going live ;-)

== callbacks ==
custom !commands and callbacks all take place in the same namespace, namely ::ap::callback. dont overwrite it, dont create child namespaces - unless you know what you are doing ;-)

direct callbacks (executed on a certain event) are the following:
autopilot/scripts/callback/on_irc_connect.tcl
when the irc connection has been established (rfc conform, after end of /MOTD has been received)
autopilot/scripts/callback/on_irc_kick.tcl
when the bot has been kicked (default is to rejoin the channel immediately)
autopilot/scripts/callback/on_game_join.tcl
when a client joins the game, this allows to send an in-game MOTD to the client privately
autopilot/scripts/callback/on_game_serverpw.tcl
when autopilot changes the server password (not when the password is changed manually)

=== callback environment commands ===
[who]
returns a string, nick of who called the command
[private]
returns a boolean (true or false) depending on the command being issued in private or public chat
(callback files - as in those in autopilot/scripts/callback - all are set to public)
[target]
returns a string, the namespace of the calling environment (e.g. ::mod_irc::say or ::ap::game::say)
mainly for internal use only
[numArgs]
number of args passed to the callback
[getArg <number>]
get the argument numbered <number>
0 is the name of the command itself, so your script arguments will most likely be startig with 1
if you fetch an argument that does not exist, an empty string is returned
<number> may also be end or end-<number> to count from the back
[getArgs [<start=0>] [<end=end>]]
start must be < end, can take any number or end-<number>, defaults to 0 (first element)
end must be > start, can take any nymber or end or end-<number>, defaults to end (last element)
say::public "message"
sends "message" to the public chat of the originating call
e.g. if !command was issued in irc, say::public will chat to the public irc channel
say::private "message"
send "message" to [who] in private
say::reply "message"
will reply to [who] (if command was issued publicly, reply in public. if command was issued privately reply privately)

=== global ap+ commands ===
::ap::say::everywhere "message"
send "message" to all possible outlets (game/irc/mysql)
::ap::say::fromGame "message"
same as ::ap::say::everywyere, jsut dont send "message" to the game

::ap::game::pause
pause the game
::ap::game::unpause
unpause the game
::ap::game::save <savename>
save the game to the file <savename>.sav (if <savename> is not specified, it saves to game.sav)
::ap::game::console "command\r"
send command to the dedicated console (please note the \r it gives the console command it's life!)
::ap::game::say::public [who] "message"
say "message" publicly in the game (use this if say::public would send to irc for example)
only use [who] if you want to address [who] prefixing your message with "[who]: "

::ap::func::map_string "string"
map certain strings to values
::ap::func::getClientId [who]
get the in-game client id from a nick name (returns 0 if [who] is not found in the clients list)

=== irc related commands ===
::mod_irc::say::public [who] "message"
force say something in the irc channel (only pass [who] if you want to address someone, see above)
::mod_irc::nickIsOp [who]
returns a boolean, check if [who] is op in the irc channel

NOTE:
only use irc related commands from irc commands (e.g. files in autopilot/scripts/irc/<command>.tcl)
or wrap them in namespace checks
if {[namespace exists ::mod_irc]} {
# your code here
}
Note:
as i am working on a cleaner callback environment please note that these details are bound to change / expand

==useful commands==
find useful custom commands at http://pub.dihedral.de/openttd/ap+

==svn==
svn co http://svn.openttdcoop.org/tools/autopilot/branches/ap+

Autopilot/ap+

2010-02-06T19:04:30Z

Petert: /* about */

{|
|
= ap+ =
|rowspan=3|__TOC__
|-
|
== about ==
ap+ is a branch of [[Autopilot]] - Trying to not lose too many features while providing many more. Development is at version ap+ 3.0-beta (Started counting after AutoPilot's 2.x)
|-
|

== license ==
for license information please see [[Autopilot#License]]
|}
== features ==
=== standard ===
features from autopilot:
* Periodic automatic server password changes
* <s>Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)</s>
* Implementation of net_frame_freq setting in openttd.cfg
* Automatic pausing of the server when the number of connected clients is below a user-defined threshold
* Greeting of players, by name, as they join the server (up to three chat lines)
* Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server
* Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified
* adds '''version''' and '''license''' commands to console
* adds an admin pager facility to the game

features introduced in ap+:
* callback environment (used for all !commands and callbacks)
* custom in-game !commands (see [[#custom commands|custom !commands]] for more details)
* callback on client joining the game (MOTD now takes place in here and can be sent to the new client privately)
* callback on changed server password

=== irc ===
requires: tcllib
features from autopilot:
* Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.
* Provides channel and privmsg commands to query the players and companies on the server
* Provides channel and privmsg commands to show server version and newgrf settings
* Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server
* Provides channel and privmsg commands allowing IRC users to learn the current password
* Supports CTCP VERSION and can identify to IRC services

features added in ap+:
* !rcon command can now be used by channel op's (from channel or privmsg) without rcon password (e.g. !rcon pause)
* custom !commands (see [[#custom commands|custom !commands]] for more details)
* callback on kick (autopilot/scripts/callback/on_irc_kick.tcl) auto-rejoin after kick now takes place here
* callback on irc connection established (autopilot/scripts/callback/on_irc_connect.tcl) (after MOTD)
* !leave command (leave the channel, make bot rejoin with /invite)

features planed for ap+:
* capture console output and return to the command issueing irc client
* private chat between irc client and game client

=== mysql ===
unchanged, see [[Autopilot#MySQL module]]

=== signals ===
requires [http://tclx.sf.net tclx]
ap+ provides kill signal catching and sourcing files from autopilot/signals/ appropriately
please note that not all os's support all the signals that ap+ has support for. ap+ will filter the unsupported signals out of the list and output a warning. bin/ap-signal.sh links the kill signals to actions their respective signal tcl script performes (making it easier to determin what signal to send)
(e.g. bin/ap-signal.sh IRC_QUIT will disconnect form the irc server)

== custom commands ==
custom commands are sourced on every call, meanting they can be edited without needing ap+ to be restarted / rehashed. they are executed in the callback namespace (see [[#callbacks|callbacks]] for more details)

ap+
`-- autopilot
`-- scripts
|-- callback (callback files, creating your own has no affect)
|-- game (!commands, only accessible from the game)
|-- global (!commands, accessible from game and irc)
`-- irc (!commands, only accessible from irc)

place your custom <command>.tcl script into the appropriate folder, and note - currently a script can cause ap+ to crasch or lose irc connection - so test them well before going live ;-)

== callbacks ==
custom !commands and callbacks all take place in the same namespace, namely ::ap::callback. dont overwrite it, dont create child namespaces - unless you know what you are doing ;-)

direct callbacks (executed on a certain event) are the following:
autopilot/scripts/callback/on_irc_connect.tcl
when the irc connection has been established (rfc conform, after end of /MOTD has been received)
autopilot/scripts/callback/on_irc_kick.tcl
when the bot has been kicked (default is to rejoin the channel immediately)
autopilot/scripts/callback/on_game_join.tcl
when a client joins the game, this allows to send an in-game MOTD to the client privately
autopilot/scripts/callback/on_game_serverpw.tcl
when autopilot changes the server password (not when the password is changed manually)

=== callback environment commands ===
[who]
returns a string, nick of who called the command
[private]
returns a boolean (true or false) depending on the command being issued in private or public chat
(callback files - as in those in autopilot/scripts/callback - all are set to public)
[target]
returns a string, the namespace of the calling environment (e.g. ::mod_irc::say or ::ap::game::say)
mainly for internal use only
[numArgs]
number of args passed to the callback
[getArg <number>]
get the argument numbered <number>
0 is the name of the command itself, so your script arguments will most likely be startig with 1
if you fetch an argument that does not exist, an empty string is returned
<number> may also be end or end-<number> to count from the back
[getArgs [<start=0>] [<end=end>]]
start must be < end, can take any number or end-<number>, defaults to 0 (first element)
end must be > start, can take any nymber or end or end-<number>, defaults to end (last element)
say::public "message"
sends "message" to the public chat of the originating call
e.g. if !command was issued in irc, say::public will chat to the public irc channel
say::private "message"
send "message" to [who] in private
say::reply "message"
will reply to [who] (if command was issued publicly, reply in public. if command was issued privately reply privately)

=== global ap+ commands ===
::ap::say::everywhere "message"
send "message" to all possible outlets (game/irc/mysql)
::ap::say::fromGame "message"
same as ::ap::say::everywyere, jsut dont send "message" to the game

::ap::game::pause
pause the game
::ap::game::unpause
unpause the game
::ap::game::save <savename>
save the game to the file <savename>.sav (if <savename> is not specified, it saves to game.sav)
::ap::game::console "command\r"
send command to the dedicated console (please note the \r it gives the console command it's life!)
::ap::game::say::public [who] "message"
say "message" publicly in the game (use this if say::public would send to irc for example)
only use [who] if you want to address [who] prefixing your message with "[who]: "

::ap::func::map_string "string"
map certain strings to values
::ap::func::getClientId [who]
get the in-game client id from a nick name (returns 0 if [who] is not found in the clients list)

=== irc related commands ===
::mod_irc::say::public [who] "message"
force say something in the irc channel (only pass [who] if you want to address someone, see above)
::mod_irc::nickIsOp [who]
returns a boolean, check if [who] is op in the irc channel

NOTE:
only use irc related commands from irc commands (e.g. files in autopilot/scripts/irc/<command>.tcl)
or wrap them in namespace checks
if {[namespace exists ::mod_irc]} {
# your code here
}
Note:
as i am working on a cleaner callback environment please note that these details are bound to change / expand

==useful commands==
find useful custom commands at http://pub.dihedral.de/openttd/ap+

==svn==
svn co http://svn.openttdcoop.org/tools/autopilot/branches/ap+

Autopilot

2010-02-06T17:53:56Z

Petert: /* Windows */ Fixed link to post

autopilot is a [http://tcl.tk/ Tcl] script which uses Tcl's [http://expect.nist.gov/ Expect] package to interface with [http://www.openttd.org/ OpenTTD's] dedicated server console to provide network games with additional features not normally available with the game alone. This is the operator's manual for version 2.0 of autopilot.

==Branches==
===AP+===
[[Autopilot/ap+|ap+]] is a branch of Autopilot - trying to not lose too many features and to provide many more. development is at version ap+ 3.0 beta (started counting after autopilot's 2.x)

===Avignon===
Avignon is a new ground-up approach of the known autopilot or ap+
it is written in TCL8.5 using some (slightly modified) modules from tcllib

Homepage: http://www.codecubes.org/wiki/Avignon

==License==
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

Additionally, this operator's manual is Copyright © 2006 Brian Ronald.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is available [http://www.gnu.org/licenses/fdl.txt here].

== Overview ==
'''autopilot''' is a modular script. It comes as a set of Tcl source files. Some of these require that additional Tcl packages be installed in order to run.

=== Base module ===
The base module consists of ''autopilot.tcl'', ''autopilot-lib.tcl'' and a language file. Alone, it provides the following features:
* Periodic automatic server password changes
* Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)
* Implementation of net_frame_freq setting in openttd.cfg
* Automatic pausing of the server when the number of connected clients is below a user-defined threshold
* Greeting of players, by name, as they join the server (up to three chat lines)
* Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server
* Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified
* adds '''version''' and '''license''' commands to console
* adds an admin pager facility to the game

'''autopilot''' takes control of the server's dedicated console. Optionally, it can allow pass-through commands so that the server's operator can use the console as normal, although this comes at the price of slightly reduced responsiveness.

=== IRC module ===
The IRC module consists of ''autopilot-irc.tcl'', and requires that tcllib is installed. When enabled, it provides the following additional features:
* Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.
* Provides channel and privmsg commands to query the players and companies on the server
* Provides channel and privmsg commands to show server version and newgrf settings
* Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server
* Provides channel and privmsg commands allowing IRC users to learn the current password
* Supports CTCP VERSION and can identify to IRC services

=== MySQL module ===
The [http://www.mysql.com/ MySQL] module consists of ''autopilot-mysql.tcl'', and requires that [http://www.xdobry.de/mysqltcl/ mysqltcl] is installed. When enabled, it provides the following additional features:
* Storage of the current server password in the database, to allow database aware applications to reveal it
* Logging of in-game chat, client joins, quits and name changes to a database, including logical separation of games and servers to allow for many servers to log to the same database
The module supports database table prefixing, to allow easy co-existence with other database applications.

=== Language ===
autopilot's messages can be easily translated to other languages by including additional language files. Version 2.0 comes with one language file, ''lang_english.tcl'', which can be copied and modified to facilitate translation. The server requires that openttd be in English (at present).

== Configuration ==
'''autopilot''' is configured through ''openttd.cfg''. If a different configuration file is to be used, it must be specified to '''autopilot''' through the OTTD_CONFIG environment variable. Included with '''autopilot''' is the file ''openttd_additional.cfg'', which contains the additional sections required to operate the script. '''autopilot''' will fail to run without this configuration.

=== IRC ===
If you wish '''autopilot''' to have its IRC nickname identified with services on your chosen network, it is necessary for the nickname to be registered in advance.

=== MySQL ===
In order to use the MySQL module, the script must have access to a properly configured MySQL server in which the tables can be found. Such configuration is beyond the scope of this document, except to say that the file ''autopilot.sql'' contains the necessary CREATE TABLE commands for a MySQL 5.0 server.

=== openttd.cfg ===
Here follows a line by line description of all the new openttd.cfg options used by '''autopilot'''. They are all specified in the form of '''option = value'''. Boolean values can be ''yes'', ''true'' or ''on'' to set a feature, and anything else to un-set it.
==== network section ====
In the <nowiki>[network]</nowiki> section, the following commands are added:
;max_companies
:Set to an integer (maximum of 8 is the default). Specify the maximum number of companies allowed in the game.
;max_players
:Set to an integer (10 is the default, maximum is 11). Specify the maximum number of players allowed to connect to the game.
;max_spectators
:Set to an integer (maximum of 10 is the default). Specify the maximum number of spectators allowed to connect to the game.
;net_frame_freq
:Set to an integer. Usual default is 1, autopilot changes the default to 2. See openttd documentation for effect.

==== autopilot section ====
In the <nowiki>[autopilot]</nowiki> section, the following commands are added:
;command
:String value. Specifies the filename of the openttd executable ('''./openttd''' for Linux, '''openttd.exe''' for Windows, etc)
;language
:String value. Selects the language file ''lang_language.tcl'' where ''language'' is the content of this setting.
;responsiveness
:Integer value. Used when the console is enabled (see below). Amount of time, in seconds, between '''autopilot''' switching its attention between the console (for command entry) and the server. Lower numbers make the server more responsive to commands and events, higher numbers decrease CPU use slightly.
;email
:String value. Specifies the email address of the admin. This can be used in variable substitution and is the email address used by the admin pager.
;url
:String value. Specifies a URL which can be used in variable subsitution.
;use_irc
:Boolean value. Specifies whether to load the IRC module.
;use_mysql
:Boolean value. Specifies whether to load the MySQL module.
;use_console
:Boolean value. Specifies whether to enable pass-through commands to the user of the console. If turned off, the server ismuch more responsive, but control can only be taken through the server's rcon facility.
;randomize_password
:Boolean value. Enables the periodic password change feature.
;password_list
:String value. Filename of a text file containing a list of possible passwords to choose from. The format should be one password per line.
;password_frequency
:Boolean value. Number of milliseconds between password changes. 300000 is 5 minutes.
;pause_level
:Integer value. '''autopilot''' will pause the game if this many clients, or less, are connected to the server.
;irc_server
:String value, used only by the IRC module. The domain name or IP address of the IRC server.
;irc_port
:Integer value, used only by the IRC module. The port on which to connect to the IRC server.
;irc_user
:String value, used only by the IRC module. The IRC username to connect with.
;irc_channel
:String value, used only by the IRC module. The IRC channel to join after connecting. Must use one of # for global channels, and @ for local channels.
;irc_bridge
:Boolean value, used only by the IRC module. Specifies whether '''autopilot''' will show the game chat in the IRC channel, and vice versa.
;irc_explicit_say
:Boolean value, used only by the IRC module. If set, IRC users must use !say to communicate with game players.
;irc_rcon
:Boolean value, used only by the IRC module. Enables use of the rcon command from IRC.
;irc_nickserv
:String value, used only by the IRC module. A string to be quoted to the server in order to authenticate to services.
;motd1
:String value. A string to be sent to game chat when a player joins the server. Uses variable substitution.
;motd2
:as motd1
;motd3
:as motd1
;recount_frequency
:Integer value. Number of milliseconds between client recounts (300000 is 5 minutes). Used to maintain an accurate count for the '''pause_level''' setting in the event that clients join or quit without messages (rare, but does happen).
;mysql_server
:String value, used only by the MySQL module. The domain name or IP address of the MySQL server.
;mysql_database
:String value, used only by the MySQL module. The name of the databse which contains the database tables.
;mysql_user
:String value, used only by the MySQL module. The user with which to log in to the database.
;mysql_pass
:String value, used only by the MySQL module. The password associated with the user.
;mysql_prefix
:String value, used only by the MySQL module. The table prefix used to distinguish autopilot's tables in the database.
;mysql_gameserver
:Integer value, used only by the MySQL module. The integer value of this server, which must be a key in the '''server''' table in the database.
;smtp_server
:String value. SMTP relay server used for the admin pager command. leave empty to disable.
===responses section===
The <nowiki>[responses]</nowiki> section is used for '''keyword = response''' style command definitions. These responses are used solely by the IRC module to provide (and override) commands in the channel and by private message. Variable substitutions are supported in the responses.

=== Variable substitutions ===
Variable substitution is a means of making responses more dynamic. They are supported in the motd1, motd2 and motd3 settings, as well as in the <nowiki>[responses]</nowiki> section. The variables are specified as all-capital keywords. Wherever one o fthese keywords is found in these settings, the keyword is replaced with a substituted string. The substitutions are as follows.
;NAME
:Only used in motd1, motd2 and motd3. This is replaced with the name of the client that has joined the server.
;COMPANIES
:Replaced with an integer, being the number of companies in the game the last time that '''autopilot''' counted them.
;EMAIL
:Replaced with the email address specified in the '''email'''setting in the <nowiki>[autopilot]</nowiki> section.
;LICENSE
:Replaced with the license string, as defined in the language file.
;PASSWORD
:Replaced with the current server password.
;PLAYERS
:Replaced with an integer, being the number of connected clients.
;URL
:Replaced with the URL specified in the '''url'''setting in the <nowiki>[autopilot]</nowiki> section.
;VERSION
:Replaced with the current autopilot version string
;OTTD
:Replaced with the current OpenTTD revision or release number.

== Use ==
Once configured, starting autopilot is simply a matter of running the file ''autopilot.tcl'' from a terminal. Optionally, the command line parameter '''load''' will load the game in ''save/game.sav''. An optional second parameter is the name of a specific saved game to load:
./autopilot.tcl
This starts a new game according to what's defined in openttd.cfg
./autopilot.tcl load
This loads and continues ''save/game.sav''
./autopilot.tcl load save/special.sav
This loads and continues ''save/special.sav''

===Chat commands===
From within the game chat, three commands are acted upon by autopilot.
!page admin
This command will attempt to send an email to the admin email address.
!version
This command will show the autopilot version to players.
show autopilot version
This command will show the autopilot version to players (and has been supported since the very first version).

===MySQL module===
Use of the MySQL server requires a little more preparation. The following steps must be taken:
#The server must be named in the server table, and its key specified in openttd.cfg
#The game must have a name in the game table, and the server's key must be inserted in the server field as a foreign key
#A record must be inserted into the setup table specifying the setting of current_game, the server's key in th server field and the key of the game in the game table as a foreign key in the value field.
There is currently no tool to do this included with '''autopilot'''.
Once this is done, '''autopilot''' will automatically log the game's chat to the chatlog table (if enabled) and will write the server password to the setup table whenever it has changed. The password will be the '''value''' field in a record where '''setting''' is ''password'' and '''server''' is the server's key, as specified in openttd.cfg.

===IRC module===
The autopilot will use it's own playername as its IRC nickname. It will attempt to join its channel. If kicked, it will not rejoin unless invited. If it is invited (to anywhere, by anybody) it will take that as its cue to attempt to join its own channel.

All commands are sent by private message or in the channel. If sent in the channel, they are preceded with an exclamation mark (!).

If IRC bridging is enabled, players can converse with the IRC channel simply by using the in-game chat.
If irc_explicit_say is disabled, IRC users can converse with players simply by talking in the IRC channel. If it is enabled, they must use the !say command in the channel to be seen in the game:
!say Hi there.
This command must also be used, even if irc_explicit_say is disabled, if an IRC user wishes what they said to be logged with the in-game chat by the MySQL module.

If irc_enable_rcon is on, then any IRC user with the rcon password can execute rcon commands on the OpenTTD server by sending a private message to the autopilot:
/msg autopilot rcon password net_frame_freq 1
This command would set the OpenTTD variable net_frame_freq to 1 if autopilot's rcon password was ''password''. '''rcon''' cannot be used in the channel.

Other commands which can be used by default, either by private message or in channel:
;version
:shows the autopilot version
;newgrf
:lists the newgrf lines you’d need in your openttd.cfg
;companies
:lists the companies that are in the game
;players
:lists the players and spectators that are in the game
;url
:gives the #openttdcoop web site address
;wiki
:gives the URL of the wiki
;blog
:gives the URL of this blog
;email
:gives the email address of an admin (er, mine, as it happens…)
;revision
:shows the revision number of the openttd server
;playercount
:shows you the number of players inthe game
;companycount
:shows you the number of companies in the game

Most of these are defined in the <nowiki>[responses]</nowiki> section of ''openttd.cfg'' and can be altered or removed by autopilot's operator. New commands can be added the same way.

The newgrf command, if disabled, will still work by private message. This is by design, and allows players to request the newgrf list from the server whilst still allowing the option of not dumping huge amounts of text into the channel.

== Windows ==
Whilst '''autopilot''' works perfectly with [http://www.activestate.com/Products/ActiveTcl/ ActiveTcl], it is unfortunate that its Expect package is unable to take control over a Windows based openttd dedicated server without modification of the latter. A modification tool is available [http://www.tt-forums.net/viewtopic.php?p=490231#p490231 in this post on tt-forums.net] which will convert the Windows openttd.exe to a console application capable of being controlled.

==Support==
Because '''autopilot''' is free software, it is provided without any warranty. That said, the author (Brian Ronald, aka Brianetta) is normally happy to provide help with '''autopilot''' to those who ask nicely.

[[Category:Guides]] [[Category:IRC]]

IRC

2010-02-02T23:27:39Z

Petert: Free alternative to XChat

User:Petert

2010-01-06T21:17:11Z

Petert:

== Personal Information ==
'''Real Name:''' Peter Tarkoy

'''Born:''' November 06, 1995

'''Home:''' Around Boston, Massechusetts {{Flag|us}}

'''Email:''' [[Special:Emailuser/Petert|Wiki]]

'''Started playing TTD:''' When I was about 5 or 6, then stopped for a while, and just a year ago remembered that it still exists

'''Joined #openttdcoop:''' Late 2008

'''First Public Server Game:''' [[PublicServer:Archive_-_Games_131_-_140#gameid_138|PSG 138]]

'''Specialist on:''' Archives

'''Prefers:''' Terminus Stations, Junctions, Presignals

'''Dislikes:''' Games focused on PAX (eg ICE, SBAHN)

User:Petert

2010-01-06T21:16:38Z

Petert:

== Personal Information ==
'''Real Name:''' Peter Tarkoy

'''Born:''' November 06, 1995

'''Home:''' Around Boston, Massechusetts {{Flag|us}}

'''Email:''' [[Special:Emailuser/Petert|Wiki]]

'''Started playing TTD:''' When I was about 5 or 6, then stopped for a while, and just a year ago remembered that it still exists

'''Joined #openttdcoop:''' Late 2008

'''First Public Server Game:''' PSG 138

'''Specialist on:''' Archives

'''Prefers:''' Terminus Stations, Junctions, Presignals

'''Dislikes:''' Games focused on PAX (eg ICE, SBAHN)

PublicServer:Archive - Games 171 - 180

2010-01-05T03:29:53Z

Petert: PSG 172 archive basic outline

<noinclude>{{PublicServerArchiveMenu}}</noinclude>



{{Archive_PublicServer|Public Server Game 171|30.12.09-02.01.10| {{User|Pm}}, {{User|Mark}}, {{User|Combuster}}, {{User|KenjiE20}}, {{User|V453000}}, {{User|Sparr}}, {{User|Sam}}, {{User|ZarenorD}}, {{User|csuke}}, {{User|Petert}} | RV [[Gametype:Cargo_Concept|Cargo]] & [[Gametype:ICE SBahn|PAX]] | TL0 (RV) | 256 x 256 Sub-Arctic | r18669 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A new-year minigame. RV only, supplying two cities with food, goods and PAX from each other. In the early stages we had trouble with the very low snowline preventing from prospecting farms. After this problem solved, the game was very quick (just few days) as it was a small map and a RV game. Probably the most remarkable thing is the RV balancer which has been used a lot during the game. The game ended with 1709 road vehicles. |171|File:PSG171.png|One of the multiple-version SLH and a balancer (Chahill balancer) }}

PublicServer:Archive - Games 171 - 180

2010-01-05T03:24:40Z

Petert:

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 171|30.12.09-02.01.10| {{User|Pm}}, {{User|Mark}}, {{User|Combuster}}, {{User|KenjiE20}}, {{User|V453000}}, {{User|Sparr}}, {{User|Sam}}, {{User|ZarenorD}}, {{User|csuke}}, {{User|Petert}} | RV [[Gametype:Cargo_Concept|Cargo]] & [[Gametype:ICE SBahn|PAX]] | TL0 (RV) | 256 x 256 Sub-Arctic | r18669 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A new-year minigame. RV only, supplying two cities with food, goods and PAX from each other. In the early stages we had trouble with the very low snowline preventing from prospecting farms. After this problem solved, the game was very quick (just few days) as it was a small map and a RV game. Probably the most remarkable thing is the RV balancer which has been used a lot during the game. The game ended with 1709 road vehicles. |171|File:PSG171.png|One of the multiple-version SLH and a balancer (Chahill balancer) }}

PublicServer:Archive - Games 161 - 170

2010-01-02T00:07:58Z

Petert:

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 170|21.12.09-30.12.09| {{User|Mark}}, {{User|^Spike^}}, {{User|Csuke}}, {{User|Technica}}, {{User|Sparr}}, {{User|V453000}}, {{User|Petert}} | [[Gametype:Cargo_Concept|Cargo]] | TL | 512x512 Temperate-Alpine| r18594 [[GRF|#openttdcoop-GRF-Pack 7.3]] | This game was all about wood. We had four wood drops along the map, one of them SRNW. The network got separated into two as the goods trains had their own and wood trains as well. In the late stages of the game, we had also trouble with cash, as the inflation went strange. SRNW with a subnetwork was tested as well as a "tightly packed" station exit. |170|File:PSG170.png|Station exit compressing the trains together. For normal people: Just rails everywhere :P.}}

{{Archive_PublicServer|Public Server Game 169|11.12.09-21.12.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|KenjiE20}}, {{User|Pm}}, {{User|Petert}}, {{User|^Spike^}}, {{User|Csuke}}, {{User|Zuu}}, {{User|V453000}}, {{User|Intexon}}, {{User|jondisti}}, {{User|Simonzzz}}, {{User|Yashkir}}, {{User|Technica}}, {{User|Sparr}}, {{User|puk}}, {{User|Hirundo}} | [[Gametype:Cargo_Concept|Cargo]] (Experimental PZ-like Plan) | TL3 | 512 x 512 Temperate| r18577 [[GRF|#openttdcoop-GRF-Pack 7.3]] | Quoting from Mark's plan itself, "Experimental pz-like plan", "Mainlines start off with LR, expand when needed". |169|File:PSG169.png|A twist to the PSG screenshots, a picture of the !! BUILDER'S BOARD, with nice eye-candy.}}

{{Archive_PublicServer|Public Server Game 168|03.12.09-11.12.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|jondisti}}, {{User|Petert}}, {{User|Damalix}}, {{User|sepp}}, {{User|Techinica}}, {{User|Sietse}}, {{User|csuke}}, {{User|V453000}}, {{User|Kolo}}, {{User|sparr}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 512 Arctic | r18400 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A tightly confined network nestled in the valleys with a total of 10 BBHs and 11 SLHs |168|File:PSG168.png|A medium-sized BBH (09) created by Sietse. Notice how the tracks conform to the land, and terraforming is used very minimally.}}

{{Archive_PublicServer|Public Server Game 167|25.11.09-03.12.09| {{User|Gleeb}}, {{User|XeryusTC}}, {{User|SmatZ}}, {{User|Mark}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|Sietse}}, {{User|FiCE}}, {{User|csuke}}, {{User|Sedontane}}, {{User|jondisti}}, {{User|^Spike^}} | [[Gametype:Cargo_Concept|Cargo]] | TL4 | 1024 x 512 Temperate | r18279 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A massive game has to include massive hubs, and it did. Gleeb's plan won over Chris Booth's and the building started, the [[Mainline|LLLL_RRRR]] two way roundabout hub was the major part of the game, but it caused some jamming problems later in the game. The major cargo of the game was oil. One "Major Oil Pick up" produced a million litres a month. The [[Sideline|SL]] had to be expanded to LL RR to fit the need of the growing number of trains. The game ended with 1,000 trains. |167|File:PSG167.png|The Wood/Ore drops, and the Steel/Goods pickup, created by {{User|Chris Booth}} using a unique station which can be entered from both sides.}}

{{Archive_PublicServer|Public Server Game 166|17.11.09-25.11.09| {{User|Chris Booth}}, {{User|Gleeb}}, {{User|KenjiE20}}, {{User|Petert}}, {{User|csuke}}, {{User|Kalaidos}}, {{User|Mark}}, {{User|XeryusTC}}, {{User|A3aan}}, {{User|Dam}}, {{User|Barbaar}}, {{User|Damalix}}, {{User|jondisti}}, {{User| Kolo}}, {{User|Paul}}, {{User|raz}}, {{User|Thraxian}} | [[Gametype:Back_to_Basics|B2B]] | TL3 | 256 x 512 Sub-Tropic | r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A return of the B2B (back-to-basics) gamestyle, with an unexpectedly good result.|166|File:PSG166.png|The factory drop and pickup re-worked a total of 3 times}}

{{Archive_PublicServer|Public Server Game 165|31.10.09-17.11.09| {{User|Chris Booth}}, {{User|tneo}}, {{User|Mark}}, {{User|Petert}}, {{User|^Spike^}}, {{User|csuke}}, {{User|A3aan}}, {{User|XeryusTC}}, {{User|planetmaker}}, {{User|Damalix}}, {{User|kais58}}, {{User|sepp}}, {{User|Gleeb}}, {{User|Xaroth}} | [[Gametype:Cargo_Concept|Cargo]] | TL5 | 512 x 512 Temperate| r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A mountainous, free terraforming game, with one of the major goals to hit 1,000 trains, plan by tneo|165|File:PSG165.png|BBH01 by {{User|Chris Booth}}. An epicentre for the massive train network built}}

{{Archive_PublicServer|Public Server Game 164|25.10.09-31.10.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|^Spike^}}, {{User|pugi}}, {{User|DJNekkid}}, {{User|planetmaker}}, {{User|Nickman}}, {{User|XeryusTC}}, {{User|Damalix}}, {{User|Razaekel}}, {{User|Petert}} | [[Gametype:ICE_SBahn|PAX (SBahn)]] | TL7 | 1024 x 256 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A PAX game over a long stretch of map, connecting towns using the Japanese TrainSet.|164|File:PSG164.png|Nice view of the small and large island/sbahn/boat transfer (by Damalix and {{User|Mark}})}}

{{Archive_PublicServer|Public Server Game 163|20.10.09-25.10.09| {{User|insulfrog}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|atdt}}, {{User|Mark}}, {{User|jondisti}}, {{User|tneo}}, {{User|Gleeb}}, {{User|Spuuukie}}, {{User|pugi}}| [[Gametype:Cargo_Concept|Cargo]] | TL3 | 256 x 512 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| An exciting mountainous game, led by {{User|insulfrog}} constructed over a period of 4-5 days made the map look covered head to toe, except for some small spaces containing no industries. The beauty of the plan was it's simplicity.|163|File:PSG163.png|BBH 01 by Mark, what one could consider the structure of the entire network.}}

{{Archive_PublicServer|Public Server Game 162|11.10.09-20.10.09| {{User|Chris Booth}}, {{User|Thraxian}}, {{User|ZarenorDarkstalker}}, {{User|Petert}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 1024 Temperate| r17814 [[GRF|#openttdcoop-GRF-Pack 7.3]]| It all started with a two-way SML ML loop with main stations on the corners and a single BBH on each edge. Over 1650 trains later, most of the farms had closed - wood, coal, and oil became the chief exports. Later in the game, balancing the loads on the sidelines became the challenge, as some sidelines were sparse while others were over capacity. Shifting some stations from one mainline to another helped alleviate a lot of the congestion.|162|File:PSG162.png| One of several high-output wood stations}}

{{Archive_PublicServer|Public Server Game 161|03.10.09-11.10.09| {{User|Chris Booth}}, {{User|DCritic}}, {{User|AlexanderB}}, {{User|Petert}}, {{User|Tussengas}}, {{User|tneo}}, {{User|^Spike^}}, {{User|Stoffe}} | [[Gametype:Cargo_Concept|Cargo]] & RV | TL7 | 128 x 2048 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| Originally intended to be an RV-only game, the 2048 dimension made several players rethink that strategy. Instead, local RV networks were connected by a backbone rail line. 2000 cars and 600 trains carried cargo as fast as they could - which wasn't very fast (iron trucks carried 19 tons each at 80km/h). |161|File:PSG161.png| Don't drink and drive - you might get lost!}}

PublicServer:Archive - Games 161 - 170

2009-12-21T21:08:42Z

Petert: PSG 169 Additions

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 169|11.12.09-21.12.yy| {{User|Mark}}, {{User|Chris Booth}}, , {{User|KenjiE20}}, {{User|pm}}, {{User|Petert}}, {{User|^Spike^}}, {{User|csuke}}, {{User|Zuu}}, {{User|V453000}}, {{User|Intexon}}, {{User|jondisti}}, {{User|Simonzzz}}, {{User|Yashkir}}, {{User|Technica}}, {{User|sparr}} {{User|puk}}, {{User|Hirundo}} | Experimental ProZone-like Plan | TL3 | 512 x 512 Temperate| r18594 [[GRF|#openttdcoop-GRF-Pack 7.3]] | Quoting from Mark's plan itself, "Experimental pz-like plan", "Mainlines start off with LR, expand when needed", and "Goal: 1200 Trains". |169|File:PSG169.png|A twist to the PSG screenshots, a picture of the !! BUILDER'S BOARD, with nice eyecandy.}}

{{Archive_PublicServer|Public Server Game 168|03.12.09-11.12.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|jondisti}}, {{User|Petert}}, {{User|Damalix}}, {{User|sepp}}, {{User|Techinica}}, {{User|Sietse}}, {{User|csuke}}, {{User|V453000}}, {{User|Kolo}}, {{User|sparr}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 512 Arctic | r18400 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A tightly confined network nestled in the valleys with a total of 10 BBHs and 11 SLHs |168|File:PSG168.png|A medium-sized BBH (09) created by Sietse. Notice how the tracks conform to the land, and terraforming is used very minimally.}}

{{Archive_PublicServer|Public Server Game 167|25.11.09-03.12.09| {{User|Gleeb}}, {{User|XeryusTC}}, {{User|SmatZ}}, {{User|Mark}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|Sietse}}, {{User|FiCE}}, {{User|csuke}}, {{User|Sedontane}}, {{User|jondisti}}, {{User|^Spike^}} | [[Gametype:Cargo_Concept|Cargo]] | TL4 | 1024 x 512 Temperate | r18279 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A massive game has to include massive hubs, and it did. Gleeb's plan won over Chris Booth's and the building started, the [[Mainline|LLLL_RRRR]] two way roundabout hub was the major part of the game, but it caused some jamming problems later in the game. The major cargo of the game was oil. One "Major Oil Pick up" produced a million litres a month. The [[Sideline|SL]] had to be expanded to LL RR to fit the need of the growing number of trains. The game ended with 1,000 trains. |167|File:PSG167.png|The Wood/Ore drops, and the Steel/Goods pickup, created by {{User|Chris Booth}} using a unique station which can be entered from both sides.}}

{{Archive_PublicServer|Public Server Game 166|17.11.09-25.11.09| {{User|Chris Booth}}, {{User|Gleeb}}, {{User|KenjiE20}}, {{User|Petert}}, {{User|csuke}}, {{User|Kalaidos}}, {{User|Mark}}, {{User|XeryusTC}}, {{User|A3aan}}, {{User|Dam}}, {{User|Barbaar}}, {{User|Damalix}}, {{User|jondisti}}, {{User| Kolo}}, {{User|Paul}}, {{User|raz}}, {{User|Thraxian}} | [[Gametype:Back_to_Basics|B2B]] | TL3 | 256 x 512 Sub-Tropic | r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A return of the B2B (back-to-basics) gamestyle, with an unexpectedly good result.|166|File:PSG166.png|The factory drop and pickup re-worked a total of 3 times}}

{{Archive_PublicServer|Public Server Game 165|31.10.09-17.11.09| {{User|Chris Booth}}, {{User|tneo}}, {{User|Mark}}, {{User|Petert}}, {{User|^Spike^}}, {{User|csuke}}, {{User|A3aan}}, {{User|XeryusTC}}, {{User|planetmaker}}, {{User|Damalix}}, {{User|kais58}}, {{User|sepp}}, {{User|Gleeb}}, {{User|Xaroth}} | [[Gametype:Cargo_Concept|Cargo]] | TL5 | 512 x 512 Temperate| r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A mountainous, free terraforming game, with one of the major goals to hit 1,000 trains, plan by tneo|165|File:PSG165.png|BBH01 by {{User|Chris Booth}}. An epicentre for the massive train network built}}

{{Archive_PublicServer|Public Server Game 164|25.10.09-31.10.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|^Spike^}}, {{User|pugi}}, {{User|DJNekkid}}, {{User|planetmaker}}, {{User|Nickman}}, {{User|XeryusTC}}, {{User|Damalix}}, {{User|Razaekel}}, {{User|Petert}} | [[Gametype:ICE_SBahn|PAX (SBahn)]] | TL7 | 1024 x 256 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A PAX game over a long stretch of map, connecting towns using the Japanese TrainSet.|164|File:PSG164.png|Nice view of the small and large island/sbahn/boat transfer (by Damalix and {{User|Mark}})}}

{{Archive_PublicServer|Public Server Game 163|20.10.09-25.10.09| {{User|insulfrog}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|atdt}}, {{User|Mark}}, {{User|jondisti}}, {{User|tneo}}, {{User|Gleeb}}, {{User|Spuuukie}}, {{User|pugi}}| [[Gametype:Cargo_Concept|Cargo]] | TL3 | 256 x 512 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| An exciting mountainous game, led by {{User|insulfrog}} constructed over a period of 4-5 days made the map look covered head to toe, except for some small spaces containing no industries. The beauty of the plan was it's simplicity.|163|File:PSG163.png|BBH 01 by Mark, what one could consider the structure of the entire network.}}

{{Archive_PublicServer|Public Server Game 162|11.10.09-20.10.09| {{User|Chris Booth}}, {{User|Thraxian}}, {{User|ZarenorDarkstalker}}, {{User|Petert}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 1024 Temperate| r17814 [[GRF|#openttdcoop-GRF-Pack 7.3]]| It all started with a two-way SML ML loop with main stations on the corners and a single BBH on each edge. Over 1650 trains later, most of the farms had closed - wood, coal, and oil became the chief exports. Later in the game, balancing the loads on the sidelines became the challenge, as some sidelines were sparse while others were over capacity. Shifting some stations from one mainline to another helped alleviate a lot of the congestion.|162|File:PSG162.png| One of several high-output wood stations}}

{{Archive_PublicServer|Public Server Game 161|03.10.09-11.10.09| {{User|Chris Booth}}, {{User|DCritic}}, {{User|AlexanderB}}, {{User|Petert}}, {{User|Tussengas}}, {{User|tneo}}, {{User|^Spike^}}, {{User|Stoffe}} | [[Gametype:Cargo_Concept|Cargo]] & RV | TL7 | 128 x 2048 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| Originally intended to be an RV-only game, the 2048 dimension made several players rethink that strategy. Instead, local RV networks were connected by a backbone rail line. 2000 cars and 600 trains carried cargo as fast as they could - which wasn't very fast (iron trucks carried 19 tons each at 80km/h). |161|File:PSG161.png| Don't drink and drive - you might get lost!}}

File:PSG169.png

2009-12-21T20:58:32Z

Petert: PSG169 screenshot

PSG169 screenshot

PublicServer:Archive - Games 161 - 170

2009-12-21T20:45:40Z

Petert: PSG169 Archived

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 169|11.12.09-dd.mm.yy| {{User|Mark}}, {{User|Chris Booth}}, {{User|jondisti}}, {{User|Petert}}, Expand me | Experimental PZ-like Plan | TL3 | 512 x 512 Temperate| r18461 [[GRF|#openttdcoop-GRF-Pack 7.3]] | Game Desc |169|File:PSG169.png|Picture Description}}

{{Archive_PublicServer|Public Server Game 168|03.12.09-11.12.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|jondisti}}, {{User|Petert}}, {{User|Damalix}}, {{User|sepp}}, {{User|Techinica}}, {{User|Sietse}}, {{User|csuke}}, {{User|V453000}}, {{User|Kolo}}, {{User|sparr}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 512 Arctic | r18400 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A tightly confined network nestled in the valleys with a total of 10 BBHs and 11 SLHs |168|File:PSG168.png|A medium-sized BBH (09) created by Sietse. Notice how the tracks conform to the land, and terraforming is used very minimally.}}

{{Archive_PublicServer|Public Server Game 167|25.11.09-03.12.09| {{User|Gleeb}}, {{User|XeryusTC}}, {{User|SmatZ}}, {{User|Mark}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|Sietse}}, {{User|FiCE}}, {{User|csuke}}, {{User|Sedontane}}, {{User|jondisti}}, {{User|^Spike^}} | [[Gametype:Cargo_Concept|Cargo]] | TL4 | 1024 x 512 Temperate | r18279 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A massive game has to include massive hubs, and it did. Gleeb's plan won over Chris Booth's and the building started, the [[Mainline|LLLL_RRRR]] two way roundabout hub was the major part of the game, but it caused some jamming problems later in the game. The major cargo of the game was oil. One "Major Oil Pick up" produced a million litres a month. The [[Sideline|SL]] had to be expanded to LL RR to fit the need of the growing number of trains. The game ended with 1,000 trains. |167|File:PSG167.png|The Wood/Ore drops, and the Steel/Goods pickup, created by {{User|Chris Booth}} using a unique station which can be entered from both sides.}}

{{Archive_PublicServer|Public Server Game 166|17.11.09-25.11.09| {{User|Chris Booth}}, {{User|Gleeb}}, {{User|KenjiE20}}, {{User|Petert}}, {{User|csuke}}, {{User|Kalaidos}}, {{User|Mark}}, {{User|XeryusTC}}, {{User|A3aan}}, {{User|Dam}}, {{User|Barbaar}}, {{User|Damalix}}, {{User|jondisti}}, {{User| Kolo}}, {{User|Paul}}, {{User|raz}}, {{User|Thraxian}} | [[Gametype:Back_to_Basics|B2B]] | TL3 | 256 x 512 Sub-Tropic | r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A return of the B2B (back-to-basics) gamestyle, with an unexpectedly good result.|166|File:PSG166.png|The factory drop and pickup re-worked a total of 3 times}}

{{Archive_PublicServer|Public Server Game 165|31.10.09-17.11.09| {{User|Chris Booth}}, {{User|tneo}}, {{User|Mark}}, {{User|Petert}}, {{User|^Spike^}}, {{User|csuke}}, {{User|A3aan}}, {{User|XeryusTC}}, {{User|planetmaker}}, {{User|Damalix}}, {{User|kais58}}, {{User|sepp}}, {{User|Gleeb}}, {{User|Xaroth}} | [[Gametype:Cargo_Concept|Cargo]] | TL5 | 512 x 512 Temperate| r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A mountainous, free terraforming game, with one of the major goals to hit 1,000 trains, plan by tneo|165|File:PSG165.png|BBH01 by {{User|Chris Booth}}. An epicentre for the massive train network built}}

{{Archive_PublicServer|Public Server Game 164|25.10.09-31.10.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|^Spike^}}, {{User|pugi}}, {{User|DJNekkid}}, {{User|planetmaker}}, {{User|Nickman}}, {{User|XeryusTC}}, {{User|Damalix}}, {{User|Razaekel}}, {{User|Petert}} | [[Gametype:ICE_SBahn|PAX (SBahn)]] | TL7 | 1024 x 256 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A PAX game over a long stretch of map, connecting towns using the Japanese TrainSet.|164|File:PSG164.png|Nice view of the small and large island/sbahn/boat transfer (by Damalix and {{User|Mark}})}}

{{Archive_PublicServer|Public Server Game 163|20.10.09-25.10.09| {{User|insulfrog}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|atdt}}, {{User|Mark}}, {{User|jondisti}}, {{User|tneo}}, {{User|Gleeb}}, {{User|Spuuukie}}, {{User|pugi}}| [[Gametype:Cargo_Concept|Cargo]] | TL3 | 256 x 512 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| An exciting mountainous game, led by {{User|insulfrog}} constructed over a period of 4-5 days made the map look covered head to toe, except for some small spaces containing no industries. The beauty of the plan was it's simplicity.|163|File:PSG163.png|BBH 01 by Mark, what one could consider the structure of the entire network.}}

{{Archive_PublicServer|Public Server Game 162|11.10.09-20.10.09| {{User|Chris Booth}}, {{User|Thraxian}}, {{User|ZarenorDarkstalker}}, {{User|Petert}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 1024 Temperate| r17814 [[GRF|#openttdcoop-GRF-Pack 7.3]]| It all started with a two-way SML ML loop with main stations on the corners and a single BBH on each edge. Over 1650 trains later, most of the farms had closed - wood, coal, and oil became the chief exports. Later in the game, balancing the loads on the sidelines became the challenge, as some sidelines were sparse while others were over capacity. Shifting some stations from one mainline to another helped alleviate a lot of the congestion.|162|File:PSG162.png| One of several high-output wood stations}}

{{Archive_PublicServer|Public Server Game 161|03.10.09-11.10.09| {{User|Chris Booth}}, {{User|DCritic}}, {{User|AlexanderB}}, {{User|Petert}}, {{User|Tussengas}}, {{User|tneo}}, {{User|^Spike^}}, {{User|Stoffe}} | [[Gametype:Cargo_Concept|Cargo]] & RV | TL7 | 128 x 2048 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| Originally intended to be an RV-only game, the 2048 dimension made several players rethink that strategy. Instead, local RV networks were connected by a backbone rail line. 2000 cars and 600 trains carried cargo as fast as they could - which wasn't very fast (iron trucks carried 19 tons each at 80km/h). |161|File:PSG161.png| Don't drink and drive - you might get lost!}}

PublicServer:Archive - Games 161 - 170

2009-12-15T19:19:14Z

Petert: PSG 169 Archive (comments)

<noinclude>{{PublicServerArchiveMenu}}</noinclude>



{{Archive_PublicServer|Public Server Game 168|03.12.09-11.12.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|jondisti}}, {{User|Petert}}, {{User|Damalix}}, {{User|sepp}}, {{User|Techinica}}, {{User|Sietse}}, {{User|csuke}}, {{User|V453000}}, {{User|Kolo}}, {{User|sparr}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 512 Arctic | r18400 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A tightly confined network nestled in the valleys with a total of 10 BBHs and 11 SLHs |168|File:PSG168.png|A medium-sized BBH (09) created by Sietse. Notice how the tracks conform to the land, and terraforming is used very minimally.}}

{{Archive_PublicServer|Public Server Game 167|25.11.09-03.12.09| {{User|Gleeb}}, {{User|XeryusTC}}, {{User|SmatZ}}, {{User|Mark}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|Sietse}}, {{User|FiCE}}, {{User|csuke}}, {{User|Sedontane}}, {{User|jondisti}}, {{User|^Spike^}} | [[Gametype:Cargo_Concept|Cargo]] | TL4 | 1024 x 512 Temperate | r18279 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A massive game has to include massive hubs, and it did. Gleeb's plan won over Chris Booth's and the building started, the [[Mainline|LLLL_RRRR]] two way roundabout hub was the major part of the game, but it caused some jamming problems later in the game. The major cargo of the game was oil. One "Major Oil Pick up" produced a million litres a month. The [[Sideline|SL]] had to be expanded to LL RR to fit the need of the growing number of trains. The game ended with 1,000 trains. |167|File:PSG167.png|The Wood/Ore drops, and the Steel/Goods pickup, created by {{User|Chris Booth}} using a unique station which can be entered from both sides.}}

{{Archive_PublicServer|Public Server Game 166|17.11.09-25.11.09| {{User|Chris Booth}}, {{User|Gleeb}}, {{User|KenjiE20}}, {{User|Petert}}, {{User|csuke}}, {{User|Kalaidos}}, {{User|Mark}}, {{User|XeryusTC}}, {{User|A3aan}}, {{User|Dam}}, {{User|Barbaar}}, {{User|Damalix}}, {{User|jondisti}}, {{User| Kolo}}, {{User|Paul}}, {{User|raz}}, {{User|Thraxian}} | [[Gametype:Back_to_Basics|B2B]] | TL3 | 256 x 512 Sub-Tropic | r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]] | A return of the B2B (back-to-basics) gamestyle, with an unexpectedly good result.|166|File:PSG166.png|The factory drop and pickup re-worked a total of 3 times}}

{{Archive_PublicServer|Public Server Game 165|31.10.09-17.11.09| {{User|Chris Booth}}, {{User|tneo}}, {{User|Mark}}, {{User|Petert}}, {{User|^Spike^}}, {{User|csuke}}, {{User|A3aan}}, {{User|XeryusTC}}, {{User|planetmaker}}, {{User|Damalix}}, {{User|kais58}}, {{User|sepp}}, {{User|Gleeb}}, {{User|Xaroth}} | [[Gametype:Cargo_Concept|Cargo]] | TL5 | 512 x 512 Temperate| r18081 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A mountainous, free terraforming game, with one of the major goals to hit 1,000 trains, plan by tneo|165|File:PSG165.png|BBH01 by {{User|Chris Booth}}. An epicentre for the massive train network built}}

{{Archive_PublicServer|Public Server Game 164|25.10.09-31.10.09| {{User|Mark}}, {{User|Chris Booth}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|^Spike^}}, {{User|pugi}}, {{User|DJNekkid}}, {{User|planetmaker}}, {{User|Nickman}}, {{User|XeryusTC}}, {{User|Damalix}}, {{User|Razaekel}}, {{User|Petert}} | [[Gametype:ICE_SBahn|PAX (SBahn)]] | TL7 | 1024 x 256 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| A PAX game over a long stretch of map, connecting towns using the Japanese TrainSet.|164|File:PSG164.png|Nice view of the small and large island/sbahn/boat transfer (by Damalix and {{User|Mark}})}}

{{Archive_PublicServer|Public Server Game 163|20.10.09-25.10.09| {{User|insulfrog}}, {{User|Chris Booth}}, {{User|Petert}}, {{User|ZarenorDarkstalker}}, {{User|Thraxian}}, {{User|atdt}}, {{User|Mark}}, {{User|jondisti}}, {{User|tneo}}, {{User|Gleeb}}, {{User|Spuuukie}}, {{User|pugi}}| [[Gametype:Cargo_Concept|Cargo]] | TL3 | 256 x 512 Temperate| r17847 [[GRF|#openttdcoop-GRF-Pack 7.3]]| An exciting mountainous game, led by {{User|insulfrog}} constructed over a period of 4-5 days made the map look covered head to toe, except for some small spaces containing no industries. The beauty of the plan was it's simplicity.|163|File:PSG163.png|BBH 01 by Mark, what one could consider the structure of the entire network.}}

{{Archive_PublicServer|Public Server Game 162|11.10.09-20.10.09| {{User|Chris Booth}}, {{User|Thraxian}}, {{User|ZarenorDarkstalker}}, {{User|Petert}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 1024 Temperate| r17814 [[GRF|#openttdcoop-GRF-Pack 7.3]]| It all started with a two-way SML ML loop with main stations on the corners and a single BBH on each edge. Over 1650 trains later, most of the farms had closed - wood, coal, and oil became the chief exports. Later in the game, balancing the loads on the sidelines became the challenge, as some sidelines were sparse while others were over capacity. Shifting some stations from one mainline to another helped alleviate a lot of the congestion.|162|File:PSG162.png| One of several high-output wood stations}}

{{Archive_PublicServer|Public Server Game 161|03.10.09-11.10.09| {{User|Chris Booth}}, {{User|DCritic}}, {{User|AlexanderB}}, {{User|Petert}}, {{User|Tussengas}}, {{User|tneo}}, {{User|^Spike^}}, {{User|Stoffe}} | [[Gametype:Cargo_Concept|Cargo]] & RV | TL7 | 128 x 2048 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| Originally intended to be an RV-only game, the 2048 dimension made several players rethink that strategy. Instead, local RV networks were connected by a backbone rail line. 2000 cars and 600 trains carried cargo as fast as they could - which wasn't very fast (iron trucks carried 19 tons each at 80km/h). |161|File:PSG161.png| Don't drink and drive - you might get lost!}}

File:Standard prio and two-way.png

2009-12-15T00:53:11Z

Petert: A two-way prio and standard prio mixed.

A two-way prio and standard prio mixed.

Priority

2009-12-15T00:48:33Z

Petert: Standard + two-way signal priorities

Priorities, or prios, are constructions we use to give an important track priority over another, less important track. Priority can be made in many ways, all which will be covered here.

==Using two-way signals==
This is the easiest way to create priority. Use it with care though; when you have multiple two-way combo signals in a row the entire row will be red if one further down the line is, which will cause trains behind the one triggering the prio to stop. This kind of prio should be limited to one combo signal and an exit signal, making it only useful for very short trains or to avoid obstacles in more advanced prios.

[[File:twoway_prio.PNG|400px|thumb|none|Showing the maximum length a prio of this kind should be]]

==Standard prios==
This is the preferred way to make prios; it can be made infinitely long without causing any delays. It works as follows: a train on the mainline triggers the first of the combo signals on the parallel prio track, which then triggers all combos in the row, effectively making trains on the sideline wait when a train on the mainline is within 9 tiles of the merging point.

[[File:standard_prio.PNG|400px|thumb|none|A standard priority using a parallel track; the most common in our games]]

Note that you don't actually have to connect the parallel track to every gap between the signals, as long as the gap between the connections is not longer than the shortest trains on the network you're fine.

==Standard prio and two-way signals combined==
If you run out of room, sometimes using two-way signals ''and'' standard priorities is necessary.

[[File:standard_prio_and_two-way.png|400px|thumb|none|A standard prio combined with two-way signals.]]

==Standard prio over a bridge==
When you're building compact hubs you'll often find this trick to come in handy.

[[File:standard_prio_bridge.PNG|400px|thumb|none|A standard prio over a bridge using a parallel track.]]

The risk using this construction is that the gap between the connections to the parallel track becomes longer than the train on the mainline, in which case the prio won't trigger. This makes it pretty much un-usable for networks with trainlengths shorter than 4.

==PBS prio==
PBS introduced some interesting ways to make prios. This prio does exactly the same as the pre-signalled one:

[[File:standard_prio_pbs.PNG|400px|thumb|none|A standard 9-tile long PBS prio]]

==PBS prio over bridge==
The most interesting prio PBS introduces is the prio over a bridge. Using this technique you don't need a parallel track to have priority over a bridge, also you don't have to worry about the long gap between the connections anymore.

[[File:pbs_prio_bridge.PNG|400px|thumb|none|Using this mix of PBS and pre-signalling you can have prio over bridges without parallel tracks]]

==Limited space==
Facing limited space is proverbial daily bread when it comes to joining or merging lines. Here are two examples using knowledge explained above how to build priority while keeping space used at minimum.

[[File:Same side prio.png|400px|thumb|none|Priority built at the same side as the joining track using combo pre-signal on the main track]]

[[File:Used tunnel prio.png|400px|thumb|none|Priority built over used tunnel using PBS and combo pre-signal]]

File:Strange regular signal prio.png

2009-12-13T05:44:24Z

Petert: Priority with regular block signals

Priority with regular block signals

Priority

2009-12-13T05:43:38Z

Petert: Prio with regular Signals

Priorities, or prios, are constructions we use to give an important track priority over another, less important track. Priority can be made in many ways, all which will be covered here.

==Using two-way signals==
This is the easiest way to create priority. Use it with care though; when you have multiple two-way combo signals in a row the entire row will be red if one further down the line is, which will cause trains behind the one triggering the prio to stop. This kind of prio should be limited to one combo signal and an exit signal, making it only useful for very short trains or to avoid obstacles in more advanced prios.

[[File:twoway_prio.PNG|400px|thumb|none|Showing the maximum length a prio of this kind should be]]

==Standard prios==
This is the preferred way to make prios; it can be made infinitely long without causing any delays. It works as follows: a train on the mainline triggers the first of the combo signals on the parallel prio track, which then triggers all combos in the row, effectively making trains on the sideline wait when a train on the mainline is within 9 tiles of the merging point.

[[File:standard_prio.PNG|400px|thumb|none|A standard priority using a parallel track; the most common in our games]]

Note that you don't actually have to connect the parallel track to every gap between the signals, as long as the gap between the connections is not longer than the shortest trains on the network you're fine.

==Standard prio over a bridge==
When you're building compact hubs you'll often find this trick to come in handy.

[[File:standard_prio_bridge.PNG|400px|thumb|none|A standard prio over a bridge using a parallel track.]]

The risk using this construction is that the gap between the connections to the parallel track becomes longer than the train on the mainline, in which case the prio won't trigger. This makes it pretty much un-usable for networks with trainlengths shorter than 4.

==PBS prio==
PBS introduced some interesting ways to make prios. This prio does exactly the same as the pre-signalled one:

[[File:standard_prio_pbs.PNG|400px|thumb|none|A standard 9-tile long PBS prio]]

==PBS prio over bridge==
The most interesting prio PBS introduces is the prio over a bridge. Using this technique you don't need a parallel track to have priority over a bridge, also you don't have to worry about the long gap between the connections anymore.

[[File:pbs_prio_bridge.PNG|400px|thumb|none|Using this mix of PBS and pre-signalling you can have prio over bridges without parallel tracks]]

==Limited space==
Facing limited space is proverbial daily bread when it comes to joining or merging lines. Here are two examples using knowledge explained above how to build priority while keeping space used at minimum.

[[File:Same side prio.png|400px|thumb|none|Priority built at the same side as the joining track using combo pre-signal on the main track]]

[[File:Used tunnel prio.png|400px|thumb|none|Priority built over used tunnel using PBS and combo pre-signal]]

==Prio using regular signals==
It is possible to have a very strange looking, quite buggy priority in OpenTTD. This is using regular block signals. Note that this should not be used during PSG games.
[[File:Strange_regular_signal_prio.png|400px|thumb|none|Priority using regular signals and connecting some lines.]]

Priority

2009-12-13T04:21:54Z

Petert: /* Standard prio over a bridge */ Two apostrophes at "you'll" caused italcs to be used

Priorities, or prios, are constructions we use to give an important track priority over another, less important track. Priority can be made in many ways, all which will be covered here.

==Using two-way signals==
This is the easiest way to create priority. Use it with care though; when you have multiple two-way combo signals in a row the entire row will be red if one further down the line is, which will cause trains behind the one triggering the prio to stop. This kind of prio should be limited to one combo signal and an exit signal, making it only useful for very short trains or to avoid obstacles in more advanced prios.

[[File:twoway_prio.PNG|400px|thumb|none|Showing the maximum length a prio of this kind should be]]

==Standard prios==
This is the preferred way to make prios; it can be made infinitely long without causing any delays. It works as follows: a train on the mainline triggers the first of the combo signals on the parallel prio track, which then triggers all combos in the row, effectively making trains on the sideline wait when a train on the mainline is within 9 tiles of the merging point.

[[File:standard_prio.PNG|400px|thumb|none|A standard priority using a parallel track; the most common in our games]]

Note that you don't actually have to connect the parallel track to every gap between the signals, as long as the gap between the connections is not longer than the shortest trains on the network you're fine.

==Standard prio over a bridge==
When you're building compact hubs you'll often find this trick to come in handy.

[[File:standard_prio_bridge.PNG|400px|thumb|none|A standard prio over a bridge using a parallel track.]]

The risk using this construction is that the gap between the connections to the parallel track becomes longer than the train on the mainline, in which case the prio won't trigger. This makes it pretty much un-usable for networks with trainlengths shorter than 4.

==PBS prio==
PBS introduced some interesting ways to make prios. This prio does exactly the same as the pre-signalled one:

[[File:standard_prio_pbs.PNG|400px|thumb|none|A standard 9-tile long PBS prio]]

==PBS prio over bridge==
The most interesting prio PBS introduces is the prio over a bridge. Using this technique you don't need a parallel track to have priority over a bridge, also you don't have to worry about the long gap between the connections anymore.

[[File:pbs_prio_bridge.PNG|400px|thumb|none|Using this mix of PBS and pre-signalling you can have prio over bridges without parallel tracks]]

==Limited space==
Facing limited space is proverbial daily bread when it comes to joining or merging lines. Here are two examples using knowledge explained above how to build priority while keeping space used at minimum.

[[File:Same side prio.png|400px|thumb|none|Priority built at the same side as the joining track using combo pre-signal on the main track]]

[[File:Used tunnel prio.png|400px|thumb|none|Priority built over used tunnel using PBS and combo pre-signal]]

PublicServer:Archive - Games 51 - 60

2009-12-11T21:16:48Z

Petert:

<noinclude>{{PublicServerArchiveMenu}}</noinclude>

{{Archive_PublicServer|Public Server Game 60|31.08.07 - 03.09.07|{{User|Psyco}}, {{User|Kommer}}, {{User|Mark}}, {{User|raWt}}, {{User|Progman}}, {{User|AntB}}, {{User|SmatZ}}, {{User|Ewanm89}} |[[Gametype:Cargo_Concept|Cargo]]|(3 tiles|256x512|r10996 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]]|This game featured a 3x3 SML mainline loop and dual-RoRo stations (as shown on the right). The sidelines originally connected opposite sides of the main loop, but were severed to discourage shortcuts. Towards the end, a flooded lake became home to a Dubai-esque settlement.|60|Image:PublicServerGame60.png|A PreSignal Bypass station.}}

{{Archive_PublicServer|Public Server Game 58|20.08.07 (?) - 23.08.07|{{User|Psyco}}, {{User|PhazorX}}, {{User|Kommer}}, {{User|Mark}}, {{User|raWt}}, {{User|Addi}}, {{User|SmatZ}} |[[Gametype:Cargo_Concept|Cargo]]|(7 tiles|512x512|r10927 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]]|...|58|Image:PublicServerGame58.png|The center of the map with the names of the players}}

{{Archive_PublicServer|Public Server Game 56|12.08.07 - 17.08.07|{{User|Psyco}}, {{User|Shader}}, {{User|Kyevan}}, {{User|Kommer}}, {{User|Sian}}, {{User|Farden}} |[[Gametype:Cargo_Concept|Cargo]] and [[Gametype:TGV_Concept|Pax]]|(8 tiles|1024x128|r10827 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]]|...|56|Image:PublicServerGame56.png|}}

{{Archive_PublicServer|Public Server Game 55|07.08.07 - 12.08.07|{{User|Kommer}}, {{User|Shader}}, {{User|Farden}}, {{User|Phazorx}}, {{User|raWt}}, {{User|Sian}}, {{User|Mark}} |[[Gametype:Cargo_Concept|Cargo]] and [[Gametype:TGV_Concept|Pax]]|(8 tiles|512x512|r10827 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]] (tropical)|This game we tried to increase the population of towns as high as possible using passenger/mail, water and food trains|55|Image:PublicServerGame55.png|}}

{{Archive_PublicServer|Public Server Game 54|04.08.07 - 07.08.07|{{User|S_m_w}}, {{User|raWt}}, {{User|Shader}}, {{User|Kommer}}, {{User|Sian}} |[[Gametype:Cargo_Concept|Cargo]] |(10 tiles|1024x1024|r10737 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]] with Canadian Trainset|(Add me)|54|Image:PublicServerGame54.png|}}

{{Archive_PublicServer|Public Server Game 53|02.08.07 - 04.08.07|{{User|Doke}}, {{User|Progman}}, {{User|kezza}}, {{User|Ammler}}, {{User|Phazorx}}, {{User|PaV}}, {{User|Kommer}}, {{User|Sedontane}}, {{User|Shader}} |[[Gametype:Cargo_Concept|Cargo]] |(RVs only)|512x128|r10737 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]] with 4LV|Road vehicle only game.|53|Image:PublicServerGame53.png|}}

{{Archive_PublicServer|Public Server Game 52|24.07.07 - 02.08.07|{{User|Shader}}, {{User|Kommer}}, {{User|Ammler}}, {{User|Doke}}, {{User|Phazorx}}, {{User|Sedontane}} |[[Gametype:Cargo_Concept|Cargo]] |5 tiles|512x512|r10620 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]] with NARS|In this game we made two separate lines. The first was bringing cargo to one station which was connected to a sawmill, a factory and an oil refinery. The second line was transporting goods from the industries to a town.|52|Image:PublicServerGame52.png|The dropoff station}}

{{Archive_PublicServer|Public Server Game 51|18.07.07 - 05.08.07|{{User|Phazorx}}, {{User|Ammler}}, {{User|Adm.Spock}}, {{User|raWt}}, {{User|Dark_Link}}, {{User|Mark}} |[[Gametype:Cargo_Concept|Cargo]] |5 tiles|1024x512|r10620 + [[Guides:Glossary:GRF|#openttdcoop-GRF-Set]] with DBSetXL|One network, 4 BBHs, lots of junctions. SML and 1610 trains, not CPU friendly, but amazing network capacity.|51|Image:PublicServerGame51.jpg|North factory entry, in wait of a better picture}}