https://wiki.openttdcoop.org/api.php?action=feedcontributions&feedformat=atom&user=Brianetta 2026-05-14T16:46:21Z User contributions MediaWiki 1.25.2 https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8482 2008-08-22T11:30:33Z

<p>Brianetta: /* modular / customizable (without the need of editing ap source directly) */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Periodically change the server's password<br /> * Storing information in a database, so that a web page can query this information and display it (including the password)<br /> ** Including a log of in-game chat<br /> * Restarting the game from a new scenario or random game once it gets old enough, and nobody's still playing<br /> * OpenTTD itself ''can'' send an MOTD when a client joins, however this is sent into global chat. provide a way to greet / send the MOTD to the new client in private<br /> <br /> === Bridge to IRC / IRC bot ===<br /> ==== Chat bridging ====<br /> The main reason for being connected to IRC is so that users connected to IRC can converse with players connected to the game, and vice-versa. Chat should be relayed from IRC into the game, and from the game into IRC, without feeding back or being unclear as to the origin of any message.<br /> <br /> It should also relay to the IRC channel when players join, leave or change name in the game. For traffic reasons (the game only has a few lines to display chat) joins and parts from IRC do not need to be relayed into the game.<br /> ==== IRC bot ====<br /> The IRC connection can also be used in channel to provide information about the game to the IRC channel. Users on IRC should be able to query the bot for the number of players and companies, a list of their names and colours, and other pertinent information such as the current game password.<br /> <br /> It's also envisaged that console commands can be sent to the game server directly from IRC.<br /> <br /> === Modular / Customizable (without the need of editing ''autopilot'' source directly) ===<br /> Most of the initialisation variables in ''autopilot'' 2.0 are read from '''openttd.cfg'''. It might be necessary to separate this out, though, especially in the event that ''autopilot'' will be manipulating different configuration files in order to start a new game with new settings.<br /> <br /> The configuration of ''autopilot'' should, from the user's perspective, be a matter of providing settings in an &quot;Windows INI&quot; style configuration file (similar to openttd.cfg) and perhaps the modification of auxiliary scripts kept separate from the canonical source files. These scripts might contain Tcl commands, but it's worth considering writing a parser for something a little simpler.<br /> <br /> === Security ===<br /> ''autopilot'' should implement all of these features without leaving the game, the database, the IRC channel or any third parties vulnerable to the malicious activities of a few.<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8479 2008-08-22T11:24:02Z

<p>Brianetta: /* bridge to irc / irc bot */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Periodically change the server's password<br /> * Storing information in a database, so that a web page can query this information and display it (including the password)<br /> ** Including a log of in-game chat<br /> * Restarting the game from a new scenario or random game once it gets old enough, and nobody's still playing<br /> * OpenTTD itself ''can'' send an MOTD when a client joins, however this is sent into global chat. provide a way to greet / send the MOTD to the new client in private<br /> <br /> === Bridge to IRC / IRC bot ===<br /> ==== Chat bridging ====<br /> The main reason for being connected to IRC is so that users connected to IRC can converse with players connected to the game, and vice-versa. Chat should be relayed from IRC into the game, and from the game into IRC, without feeding back or being unclear as to the origin of any message.<br /> <br /> It should also relay to the IRC channel when players join, leave or change name in the game. For traffic reasons (the game only has a few lines to display chat) joins and parts from IRC do not need to be relayed into the game.<br /> ==== IRC bot ====<br /> The IRC connection can also be used in channel to provide information about the game to the IRC channel. Users on IRC should be able to query the bot for the number of players and companies, a list of their names and colours, and other pertinent information such as the current game password.<br /> <br /> It's also envisaged that console commands can be sent to the game server directly from IRC.<br /> <br /> === modular / customizable (without the need of editing ap source directly) ===<br /> === Security ===<br /> ''autopilot'' should implement all of these features without leaving the game, the database, the IRC channel or any third parties vulnerable to the malicious activities of a few.<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8477 2008-08-22T10:49:17Z

<p>Brianetta: /* Aims */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Periodically change the server's password<br /> * Storing information in a database, so that a web page can query this information and display it (including the password)<br /> ** Including a log of in-game chat<br /> * Restarting the game from a new scenario or random game once it gets old enough, and nobody's still playing<br /> <br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> === Security ===<br /> ''autopilot'' should implement all of these features without leaving the game, the database, the IRC channel or any third parties vulnerable to the malicious activities of a few.<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8476 2008-08-22T10:43:05Z

<p>Brianetta: /* Information and automation */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Periodically change the server's password<br /> * Storing information in a database, so that a web page can query this information and display it (including the password)<br /> ** Including a log of in-game chat<br /> * Restarting the game from a new scenario or random game once it gets old enough, and nobody's still playing<br /> <br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8475 2008-08-22T10:40:50Z

<p>Brianetta: /* Information and automation */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> * Periodically change the server's password<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Storing information in a database, so that a web page can query this information and display it (including the password)<br /> ** Including a log of in-game chat<br /> <br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8474 2008-08-22T10:38:56Z

<p>Brianetta: /* Aims */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Storing information in a database, so that a web page can query this information and display it.<br /> ** Including a log of in-game chat<br /> <br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8473 2008-08-22T10:38:19Z

<p>Brianetta: /* Information and automation */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> <br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Storing information in a database, so that a web page can query this information and display it.<br /> ** Including a log of in-game chat<br /> <br /> === minute-to-minute management of the game ===<br /> === provide admin / website with information ===<br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8472 2008-08-22T10:37:57Z

<p>Brianetta: /* Information and automation */</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> The original goal of the first ''autopilot'' was to provide some necessary feaures which weren't present in the OpenTTD dedicated server at that time, such that the server's admin did not have to be at or near the console at all times to keep things on track. An autopilot in the sense of not having to sit at the yoke of your aeroplane all the time. The first features implemented were as follows:<br /> * Set some game parameters which weren't in the game's config file (such as net_frame_freq)<br /> * Keep a count of connected players, and pause the game if there weren't any<br /> * Greet each player and show the location of a web page giving the rules, etc<br /> All of these are now possible without ''autopilot''. This is a good thing; it shows that the features are widely desirable. Now it falls to ''autopilot'' to provide additional features. They're more of a luxury than a necessity now, but should include the following:<br /> * Saving the game regularly; specifically, when people leave or join, or when somebody requests it by command from within the game.<br /> * Storing information in a database, so that a web page can query this information and display it.<br /> ** Including a log of in-game chat<br /> <br /> === minute-to-minute management of the game ===<br /> === provide admin / website with information ===<br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8471 2008-08-22T10:25:53Z

<p>Brianetta: Layout change - more info needed than bullets, so they're headers now</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> === Information and automation ===<br /> === minute-to-minute management of the game ===<br /> === provide admin / website with information ===<br /> === bridge to irc / irc bot ===<br /> === modular / customizable (without the need of editing ap source directly) ===<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot/Development&diff=8470 2008-08-22T10:24:22Z

<p>Brianetta: tidy-up</p> <hr /> <div>Outline of future autopilot development<br /> <br /> == Aims ==<br /> * Information and automation<br /> * minute-to-minute management of the game<br /> * provide admin / website with information<br /> * bridge to irc / irc bot<br /> * modular / customizable (without the need of editing ap source directly)<br /> <br /> == IRC bot ==<br /> === RFC compliance ===<br /> * use [http://tcllib.sourceforge.net/doc/irc.html irc package] (0.6 or later) from [http://libtcl.sourceforge.net/ tcllib] (1.10 or later) <br /> * standard eol-style: crlf (handled by irc package, however allow this to be configured as some networks are not rfc conform e.g. euirc.net)<br /> * ping reply asap (handeld by irc package)<br /> * join channel only after /end of MOTD received<br /> <br /> === Important callbacks ===<br /> * '''376''' /end of MOTD (code to join channel in this callback)<br /> * '''332''' joined channel (send /NAMES to keep internal nick list of channel)<br /> * '''353''' reply from /NAMES (/NAMES response can appear multiple times depending on the number of clients in the channel, accumulate them)<br /> * '''366''' /end of NAMES (process the accumulated list of channel nicks)<br /> * '''MODE''' a mode change occured, send /NAMES to update the internal list<br /> * '''NICK''' nickchange, send /NAMES<br /> * '''QUIT''' a user from our channel quit, send /NAMES<br /> * '''PART''' a user from our channel left, send /NAMES<br /> * '''KICK''' we were kicked from the channel<br /> * '''INVITE''' we have been invited to a channel<br /> * '''PRIVMSG''' a channel or private message (detect private message by comparing [target] with the bot's irc nick name, do this case insensitive)</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=IRC_Commands&diff=2858 2007-01-01T22:17:30Z

<p>Brianetta: </p> <hr /> <div>In our channel #openttdcoop there are 2 bots active. One bot is called '''&quot;sandbox&quot;''' and whenever it is on IRC you know that there is a Sandbox Game running. The second bo is called '''&quot;_42_&quot;''' which is giving us some additional features to the IRC channel itself.<br /> <br /> <br /> '''Sandbox''' understands several commands and gives you the the ability to communicate with people on The Sandbox Server via our IRC channel. Just type this command in your chatline. You can also send commands to sandbox by private message (/msg) if you do not wish to disturb the flow of the channel.<br /> <br /> &lt;center&gt;<br /> {| border=&quot;1&quot; style=&quot;border: 1px solid black;&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; align=&quot;center&quot; width=&quot;75%&quot;<br /> |- style=&quot;border: 1px solid black;&quot;<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;25%&quot; | Command<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;75%&quot;| Description<br /> {{IRC_Channel_Commands|!password|Shows the actual password of the Sandbox Server in our channel, once in a blue moon. Go to the [http://openttdcoop.ppcis.org/sandbox.php Sandbox server page] instead.}}<br /> {{IRC_Channel_Commands|!playercount|Tells you how many people are playing on the Sandbox Server}}<br /> {{IRC_Channel_Commands|!players|Lists the people who are playing on the Sandbox Server, if any}}<br /> {{IRC_Channel_Commands|!companies|Lists the companies on the Sandbox Server (should just be one)}}<br /> {{IRC_Channel_Commands|!url|Shows the link to the Sandbox-Server helppage}}<br /> {{IRC_Channel_Commands|!version|The version of Autopilot}}<br /> {{IRC_Channel_Commands|!revision|The version of OpenTTD}}<br /> {{IRC_Channel_Commands|!wiki|Shows the link to our wiki}}<br /> {{IRC_Channel_Commands|!blog|Shows the link to our blog}}<br /> |}<br /> &lt;/center&gt;<br /> <br /> <br /> '''_42_''' logs our channel and gives you some statistics as well as other nice stuff:<br /> &lt;center&gt;<br /> {| border=&quot;1&quot; style=&quot;border: 1px solid black;&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; align=&quot;center&quot; width=&quot;75%&quot;<br /> |- style=&quot;border: 1px solid black;&quot;<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;25%&quot; | Command<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;75%&quot;| Description<br /> {{IRC_Channel_Commands|!stats|Shows channel statistics}}<br /> {{IRC_Channel_Commands|!translate xx_yy| &lt;nowiki&gt;translate from xx to yy (xx/yy = en/nl/fr/de/ru/ja/etc..)&lt;/nowiki&gt; }}<br /> {{IRC_Channel_Commands|!calc a+b+c|Do a calculation}}<br /> {{IRC_Channel_Commands|!openttd commit XXXX|Shows the changes in OTTD revision XXXX}}<br /> {{IRC_Channel_Commands|!seen username|Shows, when a user was online last time and sends him a msg when returning}}<br /> |}<br /> &lt;/center&gt;<br /> <br /> <br /> <br /> <br /> [[Category:Guides]]</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=IRC_Commands&diff=2857 2007-01-01T22:16:42Z

<p>Brianetta: </p> <hr /> <div>In our channel #openttdcoop there are 2 bots active. One bot is called '''&quot;sandbox&quot;''' and whenever it is on IRC you know that there is a Sandbox Game running. The second bo is called '''&quot;_42_&quot;''' which is giving us some additional features to the IRC channel itself.<br /> <br /> <br /> '''Sandbox''' understands several commands and gives you the the ability to communicate with people on The Sandbox Server via our IRC channel. Just type this command in your chatline. You can also send commands to sandbox by private message (/msg) if you do not wish to disturb the flow of the channel.<br /> <br /> &lt;center&gt;<br /> {| border=&quot;1&quot; style=&quot;border: 1px solid black;&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; align=&quot;center&quot; width=&quot;75%&quot;<br /> |- style=&quot;border: 1px solid black;&quot;<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;25%&quot; | Command<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;75%&quot;| Description<br /> {{IRC_Channel_Commands|!password|Shows the actual password of the Sandbox Server in our channel, once in a blue moon. Go to the [http://openttdcoop.ppcis.org/sandbox.php Sandbox server page] instead.}}<br /> {{IRC_Channel_Commands|!playercount|Tells you how many people are playing on the Sandbox Server}}<br /> {{IRC_Channel_Commands|!players|Lists the people who are playing on the Sandbox Server, if any}}<br /> {{IRC_Channel_Commands|!companies|Lists the companies on the Sandbox Server (should just be one)}}<br /> {{IRC_Channel_Commands|!url|Shows the link to the Sandbox-Server helppage}}<br /> {{IRC_Channel_Commands|!version|The version of Autopilot}}<br /> {{IRC_Channel_Commands|!wiki|Shows the link to our wiki}}<br /> {{IRC_Channel_Commands|!blog|Shows the link to our blog}}<br /> |}<br /> &lt;/center&gt;<br /> <br /> <br /> '''_42_''' logs our channel and gives you some statistics as well as other nice stuff:<br /> &lt;center&gt;<br /> {| border=&quot;1&quot; style=&quot;border: 1px solid black;&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; align=&quot;center&quot; width=&quot;75%&quot;<br /> |- style=&quot;border: 1px solid black;&quot;<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;25%&quot; | Command<br /> ! style=&quot;background:#800000 ;&quot; width=&quot;75%&quot;| Description<br /> {{IRC_Channel_Commands|!stats|Shows channel statistics}}<br /> {{IRC_Channel_Commands|!translate xx_yy| &lt;nowiki&gt;translate from xx to yy (xx/yy = en/nl/fr/de/ru/ja/etc..)&lt;/nowiki&gt; }}<br /> {{IRC_Channel_Commands|!calc a+b+c|Do a calculation}}<br /> {{IRC_Channel_Commands|!openttd commit XXXX|Shows the changes in OTTD revision XXXX}}<br /> {{IRC_Channel_Commands|!seen username|Shows, when a user was online last time and sends him a msg when returning}}<br /> |}<br /> &lt;/center&gt;<br /> <br /> <br /> <br /> <br /> [[Category:Guides]]</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot&diff=2797 2006-09-12T00:53:39Z

<p>Brianetta: /* network section */</p> <hr /> <div>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.<br /> <br /> ==License==<br /> This program is free software; you can redistribute it and/or<br /> modify it under the terms of the GNU General Public License<br /> as published by the Free Software Foundation; either version 2<br /> of the License, or (at your option) any later version.<br /> <br /> This program is distributed in the hope that it will be useful,<br /> but WITHOUT ANY WARRANTY; without even the implied warranty of<br /> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br /> GNU General Public License for more details.<br /> <br /> Additionally, this operator's manual is Copyright © 2006 Brian Ronald.<br /> <br /> Permission is granted to copy, distribute and/or modify this document<br /> under the terms of the GNU Free Documentation License, Version 1.2<br /> or any later version published by the Free Software Foundation;<br /> with no Invariant Sections, no Front-Cover Texts, and no Back-Cover<br /> Texts. A copy of the license is available [http://www.gnu.org/licenses/fdl.txt here].<br /> <br /> == Overview ==<br /> '''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.<br /> <br /> === Base module ===<br /> The base module consists of ''autopilot.tcl'', ''autopilot-lib.tcl'' and a language file. Alone, it provides the following features:<br /> * Periodic automatic server password changes<br /> * Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)<br /> * Implementation of net_frame_freq setting in openttd.cfg<br /> * Automatic pausing of the server when the number of connected clients is below a user-defined threshold<br /> * Greeting of players, by name, as they join the server (up to three chat lines)<br /> * Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server<br /> * Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified<br /> * adds '''version''' and '''license''' commands to console<br /> * adds an admin pager facility to the game<br /> <br /> '''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.<br /> <br /> === IRC module ===<br /> The IRC module consists of ''autopilot-irc.tcl'', and requires that tcllib is installed. When enabled, it provides the following additional features:<br /> * Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.<br /> * Provides channel and privmsg commands to query the players and companies on the server<br /> * Provides channel and privmsg commands to show server version and newgrf settings<br /> * Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server<br /> * Provides channel and privmsg commands allowing IRC users to learn the current password<br /> * Supports CTCP VERSION and can identify to IRC services<br /> <br /> === MySQL module ===<br /> 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:<br /> * Storage of the current server password in the database, to allow database aware applications to reveal it<br /> * 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<br /> The module supports database table prefixing, to allow easy co-existence with other database applications.<br /> <br /> === Language ===<br /> 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).<br /> <br /> == Configuration ==<br /> '''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.<br /> <br /> === IRC ===<br /> 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.<br /> <br /> === MySQL ===<br /> 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.<br /> <br /> === openttd.cfg ===<br /> 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.<br /> ==== network section ====<br /> In the &lt;nowiki&gt;[network]&lt;/nowiki&gt; section, the following commands are added:<br /> ;max_companies<br /> :Set to an integer (maximum of 8 is the default). Specify the maximum number of companies allowed in the game.<br /> ;max_players<br /> :Set to an integer (maximum of 10 is the default). Specify the maximum number of players allowed to connect to the game.<br /> ;max_spectators<br /> :Set to an integer (maximum of 10 is the default). Specify the maximum number of spectators allowed to connect to the game.<br /> ;net_frame_freq<br /> :Set to an integer. Usual default is 1, autopilot changes the default to 2. See openttd documentation for effect.<br /> <br /> ==== autopilot section ====<br /> In the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section, the following commands are added:<br /> ;command<br /> :String value. Specifies the filename of the openttd executable ('''./openttd''' for Linux, '''openttd.exe''' for Windows, etc)<br /> ;language<br /> :String value. Selects the language file ''lang_language.tcl'' where ''language'' is the content of this setting.<br /> ;responsiveness<br /> :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.<br /> ;email<br /> :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.<br /> ;url<br /> :String value. Specifies a URL which can be used in variable subsitution.<br /> ;use_irc<br /> :Boolean value. Specifies whether to load the IRC module.<br /> ;use_mysql<br /> :Boolean value. Specifies whether to load the MySQL module.<br /> ;use_console<br /> :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.<br /> ;randomize_password<br /> :Boolean value. Enables the periodic password change feature.<br /> ;password_list<br /> :String value. Filename of a text file containing a list of possible passwords to choose from. The format should be one password per line.<br /> ;password_frequency<br /> :Boolean value. Number of milliseconds between password changes. 300000 is 5 minutes.<br /> ;pause_level<br /> :Integer value. '''autopilot''' will pause the game if this many clients, or less, are connected to the server.<br /> ;irc_server<br /> :String value, used only by the IRC module. The domain name or IP address of the IRC server.<br /> ;irc_port<br /> :Integer value, used only by the IRC module. The port on which to connect to the IRC server.<br /> ;irc_user<br /> :String value, used only by the IRC module. The IRC username to connect with.<br /> ;irc_channel<br /> :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.<br /> ;irc_bridge<br /> :Boolean value, used only by the IRC module. Specifies whether '''autopilot''' will show the game chat in the IRC channel, and vice versa.<br /> ;irc_explicit_say<br /> :Boolean value, used only by the IRC module. If set, IRC users must use !say to communicate with game players.<br /> ;irc_rcon<br /> :Boolean value, used only by the IRC module. Enables use of the rcon command from IRC.<br /> ;irc_nickserv<br /> :String value, used only by the IRC module. A string to be quoted to the server in order to authenticate to services.<br /> ;motd1<br /> :String value. A string to be sent to game chat when a player joins the server. Uses variable substitution.<br /> ;motd2<br /> :as motd1<br /> ;motd3<br /> :as motd1<br /> ;recount_frequency<br /> :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).<br /> ;mysql_server<br /> :String value, used only by the MySQL module. The domain name or IP address of the MySQL server.<br /> ;mysql_database<br /> :String value, used only by the MySQL module. The name of the databse which contains the database tables.<br /> ;mysql_user<br /> :String value, used only by the MySQL module. The user with which to log in to the database.<br /> ;mysql_pass<br /> :String value, used only by the MySQL module. The password associated with the user.<br /> ;mysql_prefix<br /> :String value, used only by the MySQL module. The table prefix used to distinguish autopilot's tables in the database.<br /> ;mysql_gameserver<br /> :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.<br /> ;smtp_server<br /> :String value. SMTP relay server used for the admin pager command. leave empty to disable.<br /> ===responses section===<br /> The &lt;nowiki&gt;[responses]&lt;/nowiki&gt; 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.<br /> <br /> === Variable substitutions ===<br /> 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 &lt;nowiki&gt;[responses]&lt;/nowiki&gt; 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.<br /> ;NAME<br /> :Only used in motd1, motd2 and motd3. This is replaced with the name of the client that has joined the server.<br /> ;COMPANIES<br /> :Replaced with an integer, being the number of companies in the game the last time that '''autopilot''' counted them.<br /> ;EMAIL<br /> :Replaced with the email address specified in the '''email'''setting in the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section.<br /> ;LICENSE<br /> :Replaced with the license string, as defined in the language file.<br /> ;PASSWORD<br /> :Replaced with the current server password.<br /> ;PLAYERS<br /> :Replaced with an integer, being the number of connected clients.<br /> ;URL<br /> :Replaced with the URL specified in the '''url'''setting in the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section.<br /> ;VERSION<br /> :Replaced with the current autopilot version string<br /> ;OTTD<br /> :Replaced with the current OpenTTD revision or release number.<br /> <br /> == Use ==<br /> 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:<br /> ./autopilot.tcl<br /> This starts a new game according to what's defined in openttd.cfg<br /> ./autopilot.tcl load<br /> This loads and continues ''save/game.sav''<br /> ./autopilot.tcl load save/special.sav<br /> This loads and continues ''save/special.sav''<br /> <br /> ===Chat commands===<br /> From within the game chat, three commands are acted upon by autopilot.<br /> !page admin<br /> This command will attempt to send an email to the admin email address.<br /> !version<br /> This command will show the autopilot version to players.<br /> show autopilot version<br /> This command will show the autopilot version to players (and has been supported since the very first version).<br /> <br /> ===MySQL module===<br /> Use of the MySQL server requires a little more preparation. The following steps must be taken:<br /> #The server must be named in the server table, and its key specified in openttd.cfg<br /> #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<br /> #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.<br /> There is currently no tool to do this included with '''autopilot'''.<br /> 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.<br /> <br /> ===IRC module===<br /> 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.<br /> <br /> All commands are sent by private message or in the channel. If sent in the channel, they are preceded with an exclamation mark (!).<br /> <br /> If IRC bridging is enabled, players can converse with the IRC channel simply by using the in-game chat.<br /> 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:<br /> !say Hi there.<br /> 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.<br /> <br /> 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:<br /> /msg autopilot rcon password net_frame_freq 1<br /> 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.<br /> <br /> Other commands which can be used by default, either by private message or in channel:<br /> ;version<br /> :shows the autopilot version<br /> ;newgrf<br /> :lists the newgrf lines you’d need in your openttd.cfg<br /> ;companies<br /> :lists the companies that are in the game<br /> ;players<br /> :lists the players and spectators that are in the game<br /> ;url<br /> :gives the #openttdcoop web site address<br /> ;wiki<br /> :gives the URL of the wiki<br /> ;blog<br /> :gives the URL of this blog<br /> ;email<br /> :gives the email address of an admin (er, mine, as it happens…)<br /> ;revision<br /> :shows the revision number of the openttd server<br /> ;playercount<br /> :shows you the number of players inthe game<br /> ;companycount<br /> :shows you the number of companies in the game<br /> <br /> Most of these are defined in the &lt;nowiki&gt;[responses]&lt;/nowiki&gt; section of ''openttd.cfg'' and can be altered or removed by autopilot's operator. New commands can be added the same way.<br /> <br /> 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.<br /> <br /> == Windows ==<br /> 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#490231 in this post on tt-forums.net] which will convert the Windows openttd.exe to a console application capable of being controlled.<br /> <br /> ==Support==<br /> 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.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot&diff=2796 2006-09-12T00:11:43Z

<p>Brianetta: </p> <hr /> <div>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.<br /> <br /> ==License==<br /> This program is free software; you can redistribute it and/or<br /> modify it under the terms of the GNU General Public License<br /> as published by the Free Software Foundation; either version 2<br /> of the License, or (at your option) any later version.<br /> <br /> This program is distributed in the hope that it will be useful,<br /> but WITHOUT ANY WARRANTY; without even the implied warranty of<br /> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br /> GNU General Public License for more details.<br /> <br /> Additionally, this operator's manual is Copyright © 2006 Brian Ronald.<br /> <br /> Permission is granted to copy, distribute and/or modify this document<br /> under the terms of the GNU Free Documentation License, Version 1.2<br /> or any later version published by the Free Software Foundation;<br /> with no Invariant Sections, no Front-Cover Texts, and no Back-Cover<br /> Texts. A copy of the license is available [http://www.gnu.org/licenses/fdl.txt here].<br /> <br /> == Overview ==<br /> '''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.<br /> <br /> === Base module ===<br /> The base module consists of ''autopilot.tcl'', ''autopilot-lib.tcl'' and a language file. Alone, it provides the following features:<br /> * Periodic automatic server password changes<br /> * Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)<br /> * Implementation of net_frame_freq setting in openttd.cfg<br /> * Automatic pausing of the server when the number of connected clients is below a user-defined threshold<br /> * Greeting of players, by name, as they join the server (up to three chat lines)<br /> * Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server<br /> * Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified<br /> * adds '''version''' and '''license''' commands to console<br /> * adds an admin pager facility to the game<br /> <br /> '''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.<br /> <br /> === IRC module ===<br /> The IRC module consists of ''autopilot-irc.tcl'', and requires that tcllib is installed. When enabled, it provides the following additional features:<br /> * Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.<br /> * Provides channel and privmsg commands to query the players and companies on the server<br /> * Provides channel and privmsg commands to show server version and newgrf settings<br /> * Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server<br /> * Provides channel and privmsg commands allowing IRC users to learn the current password<br /> * Supports CTCP VERSION and can identify to IRC services<br /> <br /> === MySQL module ===<br /> 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:<br /> * Storage of the current server password in the database, to allow database aware applications to reveal it<br /> * 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<br /> The module supports database table prefixing, to allow easy co-existence with other database applications.<br /> <br /> === Language ===<br /> 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).<br /> <br /> == Configuration ==<br /> '''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.<br /> <br /> === IRC ===<br /> 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.<br /> <br /> === MySQL ===<br /> 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.<br /> <br /> === openttd.cfg ===<br /> 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.<br /> ==== network section ====<br /> In the &lt;nowiki&gt;[network]&lt;/nowiki&gt; section, the following commands are added:<br /> ;max_companies<br /> :Set to an integer (maximum of 8 is the default). Specify the maximum number of companies allowed in the game.<br /> ;max_players<br /> :Set to an integer (maximum of 10 is the default). Specify the maximum number of players allowed to connect to the game.<br /> ;max_spectators<br /> :Set to an integer (maximum of 10 is the default). Specify the maximum number of spectators allowed to connect to the game.<br /> ==== autopilot section ====<br /> In the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section, the following commands are added:<br /> ;command<br /> :String value. Specifies the filename of the openttd executable ('''./openttd''' for Linux, '''openttd.exe''' for Windows, etc)<br /> ;language<br /> :String value. Selects the language file ''lang_language.tcl'' where ''language'' is the content of this setting.<br /> ;responsiveness<br /> :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.<br /> ;email<br /> :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.<br /> ;url<br /> :String value. Specifies a URL which can be used in variable subsitution.<br /> ;use_irc<br /> :Boolean value. Specifies whether to load the IRC module.<br /> ;use_mysql<br /> :Boolean value. Specifies whether to load the MySQL module.<br /> ;use_console<br /> :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.<br /> ;randomize_password<br /> :Boolean value. Enables the periodic password change feature.<br /> ;password_list<br /> :String value. Filename of a text file containing a list of possible passwords to choose from. The format should be one password per line.<br /> ;password_frequency<br /> :Boolean value. Number of milliseconds between password changes. 300000 is 5 minutes.<br /> ;pause_level<br /> :Integer value. '''autopilot''' will pause the game if this many clients, or less, are connected to the server.<br /> ;irc_server<br /> :String value, used only by the IRC module. The domain name or IP address of the IRC server.<br /> ;irc_port<br /> :Integer value, used only by the IRC module. The port on which to connect to the IRC server.<br /> ;irc_user<br /> :String value, used only by the IRC module. The IRC username to connect with.<br /> ;irc_channel<br /> :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.<br /> ;irc_bridge<br /> :Boolean value, used only by the IRC module. Specifies whether '''autopilot''' will show the game chat in the IRC channel, and vice versa.<br /> ;irc_explicit_say<br /> :Boolean value, used only by the IRC module. If set, IRC users must use !say to communicate with game players.<br /> ;irc_rcon<br /> :Boolean value, used only by the IRC module. Enables use of the rcon command from IRC.<br /> ;irc_nickserv<br /> :String value, used only by the IRC module. A string to be quoted to the server in order to authenticate to services.<br /> ;motd1<br /> :String value. A string to be sent to game chat when a player joins the server. Uses variable substitution.<br /> ;motd2<br /> :as motd1<br /> ;motd3<br /> :as motd1<br /> ;recount_frequency<br /> :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).<br /> ;mysql_server<br /> :String value, used only by the MySQL module. The domain name or IP address of the MySQL server.<br /> ;mysql_database<br /> :String value, used only by the MySQL module. The name of the databse which contains the database tables.<br /> ;mysql_user<br /> :String value, used only by the MySQL module. The user with which to log in to the database.<br /> ;mysql_pass<br /> :String value, used only by the MySQL module. The password associated with the user.<br /> ;mysql_prefix<br /> :String value, used only by the MySQL module. The table prefix used to distinguish autopilot's tables in the database.<br /> ;mysql_gameserver<br /> :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.<br /> ;smtp_server<br /> :String value. SMTP relay server used for the admin pager command. leave empty to disable.<br /> ===responses section===<br /> The &lt;nowiki&gt;[responses]&lt;/nowiki&gt; 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.<br /> <br /> === Variable substitutions ===<br /> 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 &lt;nowiki&gt;[responses]&lt;/nowiki&gt; 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.<br /> ;NAME<br /> :Only used in motd1, motd2 and motd3. This is replaced with the name of the client that has joined the server.<br /> ;COMPANIES<br /> :Replaced with an integer, being the number of companies in the game the last time that '''autopilot''' counted them.<br /> ;EMAIL<br /> :Replaced with the email address specified in the '''email'''setting in the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section.<br /> ;LICENSE<br /> :Replaced with the license string, as defined in the language file.<br /> ;PASSWORD<br /> :Replaced with the current server password.<br /> ;PLAYERS<br /> :Replaced with an integer, being the number of connected clients.<br /> ;URL<br /> :Replaced with the URL specified in the '''url'''setting in the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section.<br /> ;VERSION<br /> :Replaced with the current autopilot version string<br /> ;OTTD<br /> :Replaced with the current OpenTTD revision or release number.<br /> <br /> == Use ==<br /> 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:<br /> ./autopilot.tcl<br /> This starts a new game according to what's defined in openttd.cfg<br /> ./autopilot.tcl load<br /> This loads and continues ''save/game.sav''<br /> ./autopilot.tcl load save/special.sav<br /> This loads and continues ''save/special.sav''<br /> <br /> ===Chat commands===<br /> From within the game chat, three commands are acted upon by autopilot.<br /> !page admin<br /> This command will attempt to send an email to the admin email address.<br /> !version<br /> This command will show the autopilot version to players.<br /> show autopilot version<br /> This command will show the autopilot version to players (and has been supported since the very first version).<br /> <br /> ===MySQL module===<br /> Use of the MySQL server requires a little more preparation. The following steps must be taken:<br /> #The server must be named in the server table, and its key specified in openttd.cfg<br /> #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<br /> #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.<br /> There is currently no tool to do this included with '''autopilot'''.<br /> 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.<br /> <br /> ===IRC module===<br /> 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.<br /> <br /> All commands are sent by private message or in the channel. If sent in the channel, they are preceded with an exclamation mark (!).<br /> <br /> If IRC bridging is enabled, players can converse with the IRC channel simply by using the in-game chat.<br /> 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:<br /> !say Hi there.<br /> 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.<br /> <br /> 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:<br /> /msg autopilot rcon password net_frame_freq 1<br /> 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.<br /> <br /> Other commands which can be used by default, either by private message or in channel:<br /> ;version<br /> :shows the autopilot version<br /> ;newgrf<br /> :lists the newgrf lines you’d need in your openttd.cfg<br /> ;companies<br /> :lists the companies that are in the game<br /> ;players<br /> :lists the players and spectators that are in the game<br /> ;url<br /> :gives the #openttdcoop web site address<br /> ;wiki<br /> :gives the URL of the wiki<br /> ;blog<br /> :gives the URL of this blog<br /> ;email<br /> :gives the email address of an admin (er, mine, as it happens…)<br /> ;revision<br /> :shows the revision number of the openttd server<br /> ;playercount<br /> :shows you the number of players inthe game<br /> ;companycount<br /> :shows you the number of companies in the game<br /> <br /> Most of these are defined in the &lt;nowiki&gt;[responses]&lt;/nowiki&gt; section of ''openttd.cfg'' and can be altered or removed by autopilot's operator. New commands can be added the same way.<br /> <br /> 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.<br /> <br /> == Windows ==<br /> 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#490231 in this post on tt-forums.net] which will convert the Windows openttd.exe to a console application capable of being controlled.<br /> <br /> ==Support==<br /> 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.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot&diff=2795 2006-09-12T00:04:21Z

<p>Brianetta: </p> <hr /> <div>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.<br /> <br /> ==License==<br /> This program is free software; you can redistribute it and/or<br /> modify it under the terms of the GNU General Public License<br /> as published by the Free Software Foundation; either version 2<br /> of the License, or (at your option) any later version.<br /> <br /> This program is distributed in the hope that it will be useful,<br /> but WITHOUT ANY WARRANTY; without even the implied warranty of<br /> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br /> GNU General Public License for more details.<br /> <br /> Additionally, this operator's manual is Copyright © 2006 Brian Ronald.<br /> <br /> Permission is granted to copy, distribute and/or modify this document<br /> under the terms of the GNU Free Documentation License, Version 1.2<br /> or any later version published by the Free Software Foundation;<br /> with no Invariant Sections, no Front-Cover Texts, and no Back-Cover<br /> Texts. A copy of the license is available [http://www.gnu.org/licenses/fdl.txt here].<br /> <br /> == Overview ==<br /> '''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.<br /> <br /> === Base module ===<br /> The base module consists of ''autopilot.tcl'', ''autopilot-lib.tcl'' and a language file. Alone, it provides the following features:<br /> * Periodic automatic server password changes<br /> * Implementation of max_clients, max_companies and max_spectators settings in openttd.cfg (not normally available in OpenTTD revision 6280 and earlier)<br /> * Implementation of net_frame_freq setting in openttd.cfg<br /> * Automatic pausing of the server when the number of connected clients is below a user-defined threshold<br /> * Greeting of players, by name, as they join the server (up to three chat lines)<br /> * Changes behaviour of '''exit''' console command to save the game to ''game.sav'' before closing the server<br /> * Changes behaviour of '''save''' console command to use a default of ''game.sav'' if no file is specified<br /> * adds '''version''' and '''license''' commands to console<br /> * adds an admin pager facility to the game<br /> <br /> '''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.<br /> <br /> === IRC module ===<br /> The IRC module consists of ''autopilot-irc.tcl'', and requires that tcllib is installed. When enabled, it provides the following additional features:<br /> * Bridging of in-game chat with IRC channel, allowing IRC users to converse with players, and vice-versa.<br /> * Provides channel and privmsg commands to query the players and companies on the server<br /> * Provides channel and privmsg commands to show server version and newgrf settings<br /> * Provides privmsg rcon commands, allowing IRC users with the rcon password to control the server<br /> * Provides channel and privmsg commands allowing IRC users to learn the current password<br /> * Supports CTCP VERSION and can identify to IRC services<br /> <br /> === MySQL module ===<br /> 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:<br /> * Storage of the current server password in the database, to allow database aware applications to reveal it<br /> * 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<br /> The module supports database table prefixing, to allow easy co-existence with other database applications.<br /> <br /> === Language ===<br /> 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).<br /> <br /> == Configuration ==<br /> '''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.<br /> <br /> === IRC ===<br /> 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.<br /> <br /> === MySQL ===<br /> 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.<br /> <br /> === openttd.cfg ===<br /> 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.<br /> ==== network section ====<br /> In the &lt;nowiki&gt;[network]&lt;/nowiki&gt; section, the following commands are added:<br /> ;max_companies<br /> :Set to an integer (maximum of 8 is the default). Specify the maximum number of companies allowed in the game.<br /> ;max_players<br /> :Set to an integer (maximum of 10 is the default). Specify the maximum number of players allowed to connect to the game.<br /> ;max_spectators<br /> :Set to an integer (maximum of 10 is the default). Specify the maximum number of spectators allowed to connect to the game.<br /> ==== autopilot section ====<br /> In the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section, the following commands are added:<br /> ;command<br /> :String value. Specifies the filename of the openttd executable ('''./openttd''' for Linux, '''openttd.exe''' for Windows, etc)<br /> ;language<br /> :String value. Selects the language file ''lang_language.tcl'' where ''language'' is the content of this setting.<br /> ;responsiveness<br /> :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.<br /> ;email<br /> :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.<br /> ;url<br /> :String value. Specifies a URL which can be used in variable subsitution.<br /> ;use_irc<br /> :Boolean value. Specifies whether to load the IRC module.<br /> ;use_mysql<br /> :Boolean value. Specifies whether to load the MySQL module.<br /> ;use_console<br /> :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.<br /> ;randomize_password<br /> :Boolean value. Enables the periodic password change feature.<br /> ;password_list<br /> :String value. Filename of a text file containing a list of possible passwords to choose from. The format should be one password per line.<br /> ;password_frequency<br /> :Boolean value. Number of milliseconds between password changes. 300000 is 5 minutes.<br /> ;pause_level<br /> :Integer value. '''autopilot''' will pause the game if this many clients, or less, are connected to the server.<br /> ;irc_server<br /> :String value, used only by the IRC module. The domain name or IP address of the IRC server.<br /> ;irc_port<br /> :Integer value, used only by the IRC module. The port on which to connect to the IRC server.<br /> ;irc_user<br /> :String value, used only by the IRC module. The IRC username to connect with.<br /> ;irc_channel<br /> :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.<br /> ;irc_bridge<br /> :Boolean value, used only by the IRC module. Specifies whether '''autopilot''' will show the game chat in the IRC channel, and vice versa.<br /> ;irc_explicit_say<br /> :Boolean value, used only by the IRC module. If set, IRC users must use !say to communicate with game players.<br /> ;irc_rcon<br /> :Boolean value, used only by the IRC module. Enables use of the rcon command from IRC.<br /> ;irc_nickserv<br /> :String value, used only by the IRC module. A string to be quoted to the server in order to authenticate to services.<br /> ;motd1<br /> :String value. A string to be sent to game chat when a player joins the server. Uses variable substitution.<br /> ;motd2<br /> :as motd1<br /> ;motd3<br /> :as motd1<br /> ;recount_frequency<br /> :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).<br /> ;mysql_server<br /> :String value, used only by the MySQL module. The domain name or IP address of the MySQL server.<br /> ;mysql_database<br /> :String value, used only by the MySQL module. The name of the databse which contains the database tables.<br /> ;mysql_user<br /> :String value, used only by the MySQL module. The user with which to log in to the database.<br /> ;mysql_pass<br /> :String value, used only by the MySQL module. The password associated with the user.<br /> ;mysql_prefix<br /> :String value, used only by the MySQL module. The table prefix used to distinguish autopilot's tables in the database.<br /> ;mysql_gameserver<br /> :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.<br /> ;smtp_server<br /> :String value. SMTP relay server used for the admin pager command. leave empty to disable.<br /> ===responses section===<br /> The &lt;nowiki&gt;[responses]&lt;/nowiki&gt; 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.<br /> <br /> === Variable substitutions ===<br /> 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 &lt;nowiki&gt;[responses]&lt;/nowiki&gt; 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.<br /> ;NAME<br /> :Only used in motd1, motd2 and motd3. This is replaced with the name of the client that has joined the server.<br /> ;COMPANIES<br /> :Replaced with an integer, being the number of companies in the game the last time that '''autopilot''' counted them.<br /> ;EMAIL<br /> :Replaced with the email address specified in the '''email'''setting in the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section.<br /> ;LICENSE<br /> :Replaced with the license string, as defined in the language file.<br /> ;PASSWORD<br /> :Replaced with the current server password.<br /> ;PLAYERS<br /> :Replaced with an integer, being the number of connected clients.<br /> ;URL<br /> :Replaced with the URL specified in the '''url'''setting in the &lt;nowiki&gt;[autopilot]&lt;/nowiki&gt; section.<br /> ;VERSION<br /> :Replaced with the current autopilot version string<br /> ;OTTD<br /> :Replaced with the current OpenTTD revision or release number.<br /> <br /> == Use ==<br /> 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:<br /> ./autopilot.tcl<br /> This starts a new game according to what's defined in openttd.cfg<br /> ./autopilot.tcl load<br /> This loads and continues ''save/game.sav''<br /> ./autopilot.tcl load save/special.sav<br /> This loads and continues ''save/special.sav''<br /> <br /> ===Chat commands===<br /> From within the game chat, three commands are acted upon by autopilot.<br /> !page admin<br /> This command will attempt to send an email to the admin email address.<br /> !version<br /> This command will show the autopilot version to players.<br /> show autopilot version<br /> This command will show the autopilot version to players (and has been supported since the very first version).<br /> <br /> ===MySQL module===<br /> Use of the MySQL server requires a little more preparation. The following steps must be taken:<br /> #The server must be named in the server table, and its key specified in openttd.cfg<br /> #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<br /> #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.<br /> There is currently no tool to do this included with '''autopilot'''.<br /> 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.<br /> <br /> ===IRC module===<br /> 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.<br /> <br /> All commands are sent by private message or in the channel. If sent in the channel, they are preceded with an exclamation mark (!).<br /> <br /> If IRC bridging is enabled, players can converse with the IRC channel simply by using the in-game chat.<br /> 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:<br /> !say Hi there.<br /> 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.<br /> <br /> 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:<br /> /msg autopilot rcon password net_frame_freq 1<br /> 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.<br /> <br /> Other commands which can be used by default, either by private message or in channel:<br /> ;version<br /> :shows the autopilot version<br /> ;newgrf<br /> :lists the newgrf lines you’d need in your openttd.cfg<br /> ;companies<br /> :lists the companies that are in the game<br /> ;players<br /> :lists the players that are int he game<br /> ;url<br /> :gives the #openttdcoop web site address<br /> ;wiki<br /> :gives the URL of the wiki<br /> ;blog<br /> :gives the URL of this blog<br /> ;email<br /> :gives the email address of an admin (er, mine, as it happens…)<br /> ;revision<br /> :shows the revision number of the openttd server<br /> ;playercount<br /> :shows you the number of players inthe game<br /> ;companycount<br /> :shows you the number of companies in the game<br /> <br /> Most of these are defined in the &lt;nowiki&gt;[responses]&lt;/nowiki&gt; section of ''openttd.cfg'' and can be altered or removed by autopilot's operator. New commands can be added the same way.<br /> <br /> 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.<br /> <br /> == Windows ==<br /> 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#490231 in this post on tt-forums.net] which will convert the Windows openttd.exe to a console application capable of being controlled.<br /> <br /> ==Support==<br /> 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.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=IRC&diff=2515 2006-08-12T23:21:56Z

<p>Brianetta: Updated IRC information</p> <hr /> <div>IRC (Internet Relay Chat) is used to improve the communication between all players and friends of #openttdcoop.<br /> <br /> If you want to join our community, you will need an '''IRC client'''. We therefore recommend one of these clients:<br /> <br /> <br /> ----<br /> http://www.xchat.org/ (Many OS'es)<br /> <br /> http://bersirc.free2code.net/index.php/home (Microsoft Windows Only)<br /> <br /> http://www.hydrairc.com/ (Microsoft Windows Only)<br /> <br /> http://www.mirc.com/ (Mircosoft Windows Only)<br /> <br /> http://colloquy.info/ (Mac OS X)<br /> ----<br /> <br /> <br /> If you installed the client, connect to the OFTC IRC network. For further details and FAQ see http://www.oftc.net/ .<br /> <br /> To join our channel, simply type: ''/join #openttdcoop'', or join via irc://irc.oftc.net/openttdcoop . Be sure to have [[Guides:Glossary:IRC Hightlighting|IRC Hightlighting]] enabled.<br /> <br /> [[Category:Guides]]</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Public_Server&diff=2514 2006-08-12T23:20:22Z

<p>Brianetta: updated IRC details</p> <hr /> <div>'''For a list of games which took place on our sandbox server, look at [[Sandbox:Archive]]'''<br /> <br /> If you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at [[Membership]] and [[Sandbox_Server]]. Feel free to join our community of aspirants for #openttdcoop membership. Connection details are available on the [http://openttdcoop.ppcis.org/sandbox.php Sandbox server page].<br /> <br /> ''rcon on the sandbox server is granted to every full member of #openttdcoop and SerriaRomero, Hans, ChrisM, Osai and uLiKo, last and not least is Brianetta the server owner.''<br /> <br /> <br /> =&lt;center&gt;The #openttdcoop &quot;Sandbox Server&quot;&lt;/center&gt;=<br /> <br /> Since new players on #openttdcoop often face rather complex games on our mainserver, we decided to set up a so-called &quot;sandbox server&quot; where players have the chance to learn the very basic concepts of cooperative gameplay. On this page, you will find a guide for the first steps into our sandbox.<br /> <br /> '''All members of #openttdcoop have rcon to the sandbox server.''' <br /> <br /> ===What are the keypoints of the sandbox server?===<br /> <br /> * First of all: '''BE SURE TO CONNECT TO THE IRC CHANNEL!''' No games can take place if we do not meet up in the channel! If you are not willing to join us in the channel it is not possible for you to become a player/member of #openttdcoop due to the lack of communication between the community and you.<br /> * New players will get some tutorial guidance by full members of #openttdcoop but start playing right from the start<br /> * Smaller maps will be played (256*256 - max. 512*512). One map lasts until everything is connected and/or optimized. <br /> * There will be some kind of &quot;building convention&quot; like a &quot;coding convention&quot; on programming. This convention consists of some basic rules of &quot;clever building&quot;. Be sure to know this convention (as listed below).<br /> * Feel free to build whatever you want - you'll see the errors coming up in a growing network. Our [http://atlantis.beetjevreemd.nl:8080/wiki/index.php/Guides Guides] will help you on the very basics of good networking etc.<br /> * This server is run by an autopilot - basically an answering machine for OpenTTD servers. It is configured to keep the game paused unless at least two players are connected.<br /> <br /> ===How / Where / When ?===<br /> <br /> First of all, be sure to join our [irc://irc.freenode.org/openttdcoop IRC channel]. You will get information on games and servers. Players find together in the channel and start new or continue existing games. Also, passwords are exchanged in the channel. <br /> <br /> An advantage of having a channel on the OFTC IRC network is the circumstance of being &quot;next to&quot; the [irc://irc.oftc.org/openttd IRC channel] (#openttdcoop started there, when it was on Freenode). <br /> <br /> If you live in the european part of this planet you probably will have no problem related to our usual playing times. We mostly play between 18.00 to 01.00 (sometimes open ended) GMT during the weekdays and some afternoon sessions on weekends.<br /> <br /> ===The Sandbox Building Convention===<br /> <br /> * First of all: set your signaling length to &quot;2 tiles&quot; (Patch Options).<br /> * React on the ingame chat, we are not typing for nothing.<br /> * If you build a Hub, name it like &quot;Slh number / Name&quot; for a Sidelinehub (which is, relating to our Guides, a Sideline-to-Mainline-Hub) or &quot;Bbh number / name&quot; for a Mainline-to-Mainline-Hub. Be sure to use '''''exactly''''' this string (with spaces etc) - if you view the signlist, the Hubs will be sorted in the right way then and only then. Also: if we are talking about Hubs and you want to discuss about them too, simply follow the signlist to the corresponding Hub.<br /> * Cooperation is about communication! Always tell your collegues what you are doing and discuss planed tracks/junctions etc. Our members can - of course - help you on some decisions.<br /> * Unilateral decisions by players are against the rules. Major changes to landscape, network and so on are to be discussed with other players beforehand, and agreed upon before implementation. Players should be on the IRC channel if the in-game chat is insufficient.<br /> * There could be a network plan. In this case, the network plan should be followed. If players decide to do something different, the plan has to be changed first.<br /> * After you build new station and connect it to the sideline say &quot;station_name connected&quot;.<br /> * If you build big and complicated station like pick up or drop off, place a sign with your name near it.<br /> * Take care about the rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.<br /> * If you need depot and no one is nearby, build service center. Never build depot at side line.<br /> * Don't log in as player. Change your name before connecting to our server.<br /> * Network takes precedence over trains. Don't build hundreds of trains until the network is proven.<br /> * Enjoy the cooperation.<br /> <br /> ===Links to the Chatlog for the Sandbox===<br /> <br /> &lt;center&gt;Full Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog&lt;/center&gt;<br /> <br /> &lt;center&gt;Running Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog/last20.php&lt;/center&gt;<br /> <br /> ===Overview of Games so Far===<br /> <br /> Visit the [[Sandbox:Archive]] !</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Membership&diff=2513 2006-08-12T23:17:47Z

<p>Brianetta: updated IRC server</p> <hr /> <div>==&lt;center&gt;Membership at #openttdcoop?&lt;/center&gt;==<br /> <br /> ===The basic issue===<br /> As a community founded in order to develop concepts for huge train networks in OTTD our networks nowadays are far more complex compared to the tracks we built at the very beginnings of #openttdcoop. Despite this positive development we have to face the problem that it is more and more challenging for new players to join us. Regarding this challenge we aim to support new players that try to join us as much as possible and tutor them ingame.<br /> <br /> ===Our approach===<br /> To achieve a good tutorial guidance ingame we decided to restructure our community a bit. From now on players will have a certain status. On the one hand there are members who know the rules, the usual tricks and concepts of our community. On the other hand there are the apprentice OTTD players who are very welcome to watch and build with us under the guidance of our active members. Since our active members want to play by themselves and we want to ensure a high quality tutorial help to our new members we decided to restrict the numer of apprentices in our games to one per full member playing. Therefore we frequently change our company password. Playing issues are discussed - as usual - in our [irc://irc.oftc.org/openttdcoop IRC channel].<br /> <br /> ===Our members===<br /> Current '''active Members''' are: e1ko, Mucht, Osai, StarLite, thgergo and valhallasw.<br /> <br /> Current '''inactive Members''' are: dp, guru3, Roo, ShaggZ, StarLite, ottd-king and Xahodo.<br /> <br /> And last but not least our '''honorary members''': Brianetta (thx for hosting and helping) and TrueLight (thx for bugtrackings).<br /> <br /> ==&lt;center&gt;How to become a member at #openttdcoop?&lt;/center&gt;==<br /> <br /> ===Six steps to become a member===<br /> '''First''' of all, be sure to join us in our IRC channel.<br /> <br /> '''Second''', be sure you know something about the very basics of OTTD. The [http://wiki.openttd.org/index.php OTTD Wiki] will help you on this. Basics are things like signaling, laying tracks, purchasing trains and so on. <br /> <br /> '''Third''', be sure to know what we are talking about. Therefore, read our [[Guides|Guides]] and the [[Ruleset|Rules]] page. Furthermore, register on this wiki and feel welcome to edit your own userpage - an admin will help you on IRC to put your userpage to the right place.<br /> <br /> The '''fourth''' step is joining a Sandbox server game. On our sandbox server there are many players who are new to our community. You have the possibility to interact in a cooperative group without having strict rules about building but it is highly recommended to stick to our common ruleset and building suggestions.<br /> <br /> '''Fifth''', if you have been around some time on our Sandbox and built some nice hubs and stations (don't forget to name them), you may be invited by some members of #openttdcoop to our main server to show up your skills. Remember: rules are more strictly on the main server due to the fact that we want to build effective networks. We therefore recommend to stick to our basic construction rules as early as you start playing on the sandbox.<br /> <br /> '''Sixth''', you have proven your construction and creative skills and therefore got promoted by a ''two-third majority of '''active''' #optenttdcoop-members'' to a full member of #openttdcoop.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot_in_Coopetition&diff=2480 2006-08-07T22:21:49Z

<p>Brianetta: /* Client Counting */</p> <hr /> <div>''by [[User:Osai|Osai]]<br /> <br /> After our first successful [[Coopetition|Coopetition Game]] I thought about the usage of Brianettas Autopilot in Coopetition Games.<br /> <br /> '''Note:''' Some of this ideas are already in preparation for a possible league/ladder system and we are far away from it. The first three ideas are important for Coopetition Games in general.<br /> <br /> Autopilot should handle a lot of technical things I am going to list here:<br /> <br /> <br /> == Handling the Game Start ==<br /> Autopilot should manage the game start, after starting the server both teams have time to get in contact with the map (the rules define the time). After this time Autopilot will start the game with an announcement.<br /> &lt;pre&gt;<br /> 5 minutes until the game starts.<br /> 1 minute until the game starts.<br /> 10 seconds until the game starts.<br /> 3<br /> 2<br /> 1<br /> Game Started - Good luck and enjoy your ride!<br /> &lt;/pre&gt;<br /> ''Brianetta says: This can be done, but will require a specially re-written autopilot.''<br /> == Handling the Companies and Players ==<br /> If the game is in progress, Autopilot should automatically pause the game when a player de-syncs or looses his connection. Actually OpenTTD can not restrict the company count to a special value.''Brianetta says: Yes, it can...'' But Autopilot could check if there are more then two companies in the game and delete the third company. And of course Autopilot should manage the player count, any fifth player should be kicked out immediately!<br /> &lt;pre&gt;<br /> Player 3 lost his connection. Game Paused.<br /> Game will continue in 3, 2, 1 second/s.<br /> Game continued.<br /> &lt;/pre&gt;<br /> ''Brianetta says: Again, a rewrite is needed, but it's possible.''<br /> <br /> == Handling of the Game Time ==<br /> As we play always until 1.1.1968 (this date can maybe change too if we have clearer rules) game should be paused at this day by the Autopilot. All players should be announcend if another year is over by our lovely Autopilot to be informed when the last year starts.<br /> &lt;pre&gt;<br /> 6 Years until game ends<br /> 2 Years until game ends<br /> This is the final year, from now on your train income counts<br /> The game is over - Congratulations to all Players<br /> &lt;/pre&gt;<br /> ''Brianetta says: Unfortunately, autopilot has no way of retreiving the date from the console. It might be possible with network code, but that's a ''major'' re-write.''<br /> == Auto-Savegame ==<br /> If possible the game should be saved to a special folder where we can check all the data.<br /> &lt;pre&gt;<br /> Game successfully saved.<br /> &lt;/pre&gt;<br /> ''Brianetta says: This is intended to be a feature of autopilot 2''<br /> == Easy Administration via Webinterface ==<br /> I am not sure if Autopilot is able to interact with a Database yet. But it would be awesome to be able to configure the Autopilot via an easy-to-use Interface before the game starts! Some other great possibilities came with this thing, but I wont talk about them!<br /> ''Brianetta says: Not at the moment it isn't possible. Settings are kept in openttd.cfg, so what you really need is a web based editor for that. It's something I might work on.''<br /> <br /> ==Client Counting==<br /> If possible, there should be a counting of clients refering to the company. Since Coopetition is a 2vs2 game, the server should pause when there are less than 4 players on the player-companies.<br /> ''Brianetta says: This is possible, but has issues. Clients joining the server will only be checked for team or company membership after a short delay. Of course, when clients quit, autopilot can know immediately if they were in a company, because it can store that information.''<br /> <br /> == The progress ==<br /> <br /> {{R&amp;D_header|Autopilot features for Coopetition}}<br /> {{R&amp;D_content|Handling the Game Start|[[User:Osai|Osai]]| wip |first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Handling the Companies and Players|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Handling of the game time|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Auto-Savegame|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Easy Administration via Webinterface|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> <br /> [[Category:Research]]</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot_in_Coopetition&diff=2479 2006-08-07T22:10:46Z

<p>Brianetta: /* Handling the Companies and Players */</p> <hr /> <div>''by [[User:Osai|Osai]]<br /> <br /> After our first successful [[Coopetition|Coopetition Game]] I thought about the usage of Brianettas Autopilot in Coopetition Games.<br /> <br /> '''Note:''' Some of this ideas are already in preparation for a possible league/ladder system and we are far away from it. The first three ideas are important for Coopetition Games in general.<br /> <br /> Autopilot should handle a lot of technical things I am going to list here:<br /> <br /> <br /> == Handling the Game Start ==<br /> Autopilot should manage the game start, after starting the server both teams have time to get in contact with the map (the rules define the time). After this time Autopilot will start the game with an announcement.<br /> &lt;pre&gt;<br /> 5 minutes until the game starts.<br /> 1 minute until the game starts.<br /> 10 seconds until the game starts.<br /> 3<br /> 2<br /> 1<br /> Game Started - Good luck and enjoy your ride!<br /> &lt;/pre&gt;<br /> ''Brianetta says: This can be done, but will require a specially re-written autopilot.''<br /> == Handling the Companies and Players ==<br /> If the game is in progress, Autopilot should automatically pause the game when a player de-syncs or looses his connection. Actually OpenTTD can not restrict the company count to a special value.''Brianetta says: Yes, it can...'' But Autopilot could check if there are more then two companies in the game and delete the third company. And of course Autopilot should manage the player count, any fifth player should be kicked out immediately!<br /> &lt;pre&gt;<br /> Player 3 lost his connection. Game Paused.<br /> Game will continue in 3, 2, 1 second/s.<br /> Game continued.<br /> &lt;/pre&gt;<br /> ''Brianetta says: Again, a rewrite is needed, but it's possible.''<br /> <br /> == Handling of the Game Time ==<br /> As we play always until 1.1.1968 (this date can maybe change too if we have clearer rules) game should be paused at this day by the Autopilot. All players should be announcend if another year is over by our lovely Autopilot to be informed when the last year starts.<br /> &lt;pre&gt;<br /> 6 Years until game ends<br /> 2 Years until game ends<br /> This is the final year, from now on your train income counts<br /> The game is over - Congratulations to all Players<br /> &lt;/pre&gt;<br /> ''Brianetta says: Unfortunately, autopilot has no way of retreiving the date from the console. It might be possible with network code, but that's a ''major'' re-write.''<br /> == Auto-Savegame ==<br /> If possible the game should be saved to a special folder where we can check all the data.<br /> &lt;pre&gt;<br /> Game successfully saved.<br /> &lt;/pre&gt;<br /> ''Brianetta says: This is intended to be a feature of autopilot 2''<br /> == Easy Administration via Webinterface ==<br /> I am not sure if Autopilot is able to interact with a Database yet. But it would be awesome to be able to configure the Autopilot via an easy-to-use Interface before the game starts! Some other great possibilities came with this thing, but I wont talk about them!<br /> ''Brianetta says: Not at the moment it isn't possible. Settings are kept in openttd.cfg, so what you really need is a web based editor for that. It's something I might work on.''<br /> <br /> ==Client Counting==<br /> If possible, there should be a counting of clients refering to the company. Since Coopetition is a 2vs2 game, the server should pause when there are less than 4 players on the player-companies.<br /> <br /> <br /> == The progress ==<br /> <br /> {{R&amp;D_header|Autopilot features for Coopetition}}<br /> {{R&amp;D_content|Handling the Game Start|[[User:Osai|Osai]]| wip |first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Handling the Companies and Players|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Handling of the game time|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Auto-Savegame|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Easy Administration via Webinterface|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> <br /> [[Category:Research]]</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Autopilot_in_Coopetition&diff=2477 2006-08-07T22:01:37Z

<p>Brianetta: </p> <hr /> <div>''by [[User:Osai|Osai]]<br /> <br /> After our first successful [[Coopetition|Coopetition Game]] I thought about the usage of Brianettas Autopilot in Coopetition Games.<br /> <br /> '''Note:''' Some of this ideas are already in preparation for a possible league/ladder system and we are far away from it. The first three ideas are important for Coopetition Games in general.<br /> <br /> Autopilot should handle a lot of technical things I am going to list here:<br /> <br /> <br /> == Handling the Game Start ==<br /> Autopilot should manage the game start, after starting the server both teams have time to get in contact with the map (the rules define the time). After this time Autopilot will start the game with an announcement.<br /> &lt;pre&gt;<br /> 5 minutes until the game starts.<br /> 1 minute until the game starts.<br /> 10 seconds until the game starts.<br /> 3<br /> 2<br /> 1<br /> Game Started - Good luck and enjoy your ride!<br /> &lt;/pre&gt;<br /> ''Brianetta says: This can be done, but will require a specially re-written autopilot.''<br /> == Handling the Companies and Players ==<br /> If the game is in progress, Autopilot should automatically pause the game when a player de-syncs or looses his connection. Actually OpenTTD can not restrict the company count to a special value. But Autopilot could check if there are more then two companies in the game and delete the third company. And of course Autopilot should manage the player count, any fifth player should be kicked out immediately!<br /> &lt;pre&gt;<br /> Player 3 lost his connection. Game Paused.<br /> Game will continue in 3, 2, 1 second/s.<br /> Game continued.<br /> &lt;/pre&gt;<br /> ''Brianetta says: Again, a rewrite is needed, but it's possible.''<br /> == Handling of the Game Time ==<br /> As we play always until 1.1.1968 (this date can maybe change too if we have clearer rules) game should be paused at this day by the Autopilot. All players should be announcend if another year is over by our lovely Autopilot to be informed when the last year starts.<br /> &lt;pre&gt;<br /> 6 Years until game ends<br /> 2 Years until game ends<br /> This is the final year, from now on your train income counts<br /> The game is over - Congratulations to all Players<br /> &lt;/pre&gt;<br /> ''Brianetta says: Unfortunately, autopilot has no way of retreiving the date from the console. It might be possible with network code, but that's a ''major'' re-write.''<br /> == Auto-Savegame ==<br /> If possible the game should be saved to a special folder where we can check all the data.<br /> &lt;pre&gt;<br /> Game successfully saved.<br /> &lt;/pre&gt;<br /> ''Brianetta says: This is intended to be a feature of autopilot 2''<br /> == Easy Administration via Webinterface ==<br /> I am not sure if Autopilot is able to interact with a Database yet. But it would be awesome to be able to configure the Autopilot via an easy-to-use Interface before the game starts! Some other great possibilities came with this thing, but I wont talk about them!<br /> ''Brianetta says: Not at the moment it isn't possible. Settings are kept in openttd.cfg, so what you really need is a web based editor for that. It's something I might work on.''<br /> <br /> <br /> == The progress ==<br /> <br /> {{R&amp;D_header|Autopilot features for Coopetition}}<br /> {{R&amp;D_content|Handling the Game Start|[[User:Osai|Osai]]| wip |first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Handling the Companies and Players|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Handling of the game time|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Auto-Savegame|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> {{R&amp;D_content|Easy Administration via Webinterface|[[User:Osai|Osai]]|wip|first version created|unclaimed|In progress|unclaimed|In progress| | }}<br /> <br /> [[Category:Research]]</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Openttdcoop_News&diff=2343 2006-07-31T20:56:44Z

<p>Brianetta: Added ICE game link</p> <hr /> <div>&lt;noinclude&gt;== Latest News ==&lt;/noinclude&gt;<br /> '''24.07.06''': A day full of news:<br /> * [[User:OwenS|OwenS]] joins our [[Main_Server|Mainserver]]-team! Congratulations!<br /> * After some hard work on this wiki, many improvements are done. To have an idea of the ongoing improvements, check our whole-new [[Sandbox:Archive|Sandbox Archive]].<br /> * [[User:Valhallasw|Valhallasw]] has made some mediawiki hacks to get new permission settings. Every registered user is now welcome to edit their [[Special:Mypage|user page]] and to discuss ideas on the talk page of every article. Experienced sandboxers are welcome to help on the wiki in the Sandbox: namespace, which, for example, hosts [[Sandbox:Archive|the Sandbox Archive]].<br /> * The team is working on some whole new concepts for our community - stay tuned!<br /> <br /> '''21.07.2006''': Due to some issues with the US-Stations-GRF we reworked our whole GRF-Set. We took the chance to implement the planeset so our games will become even more eyecandy in the future. Check our [[Guides:Glossary:GRF|related page]] to update your config file and get the new package of GRFs!<br /> <br /> '''19.07.2006''': A [[Sandbox_Server|Sandbox game]] started - again. Our [[Community:Members|Sandboxers]] are very active today. They decided to create an [[Gametype:ICE_SBahn|ICE-game]] - with the recently developed 'S-Bahn'-Idea.<br /> &lt;noinclude&gt;<br /> == July 2006 ==<br /> '''09.07.2006''': The [[Sandbox_Server|Sandbox game]] has been restarted. A new game is up.<br /> <br /> '''08.07.2006''': The [[Main_Server|Main Server Game]] is developing fast - in the meantime, the [[Sandbox_Server|Sandbox game]] seems to be almost finished and one has to expect a new Sandbox map coming up the next days.<br /> <br /> '''03.07.2006''': [[User:XeryusTC|XeryusTC]] has been invited to the mainserver - congratulations! Furthermore, the community started an all-new mainserver game based on the scenario &quot;Bigriver&quot;.<br /> <br /> == June 2006 ==<br /> '''30.06.2006''': Right after the serverupgrade our Sandboxers started a news game. Join them in their efforts and visit [[Sandbox Server]] for further details.<br /> <br /> '''30.06.2006''': #openttdcoop changes both [[Main Server]] and [[Sandbox Server]] to OTTD Nightly r5431. Additionally, we have chosen some GRFs we will use in order to enhance our gameplay. Get the whole information [[Guides:Glossary:GRF|here]].<br /> <br /> '''08.06.2006''': #openttdcoop Servers are online again, check out [[Main Server]] and [[Sandbox Server]] for new ip addresses and further information<br /> <br /> '''05.06.2006''': #openttdcoop decided to make use of additional grfs. These new grfs will enrich our gameplay and make our games more 'eyecandy'. Check [[Guides:Glossary:GRF|this page]] for further details.<br /> <br /> '''05.06.2006''': #openttdcoop started a new game on the [[Main Server]]; join our IRC channel if you are interested in our games!<br /> <br /> == Februar 2006 ==<br /> '''27.02.2006''': #openttdcoop welcomes [[User:csuke|csuke]] to our mainserver! After joining our sandbox some 3 months ago and proving his skills on loadbalancing as well as hub- and stationbuilding, csuke will support our team at the mainserver!<br /> <br /> '''16.02.2006''': Our Sandboxers have started a new map! Have fun!<br /> <br /> '''12.02.2006''': [[Community:Members|Userpages]] updated! Please check your own status + userpage and report at the IRC-Channel.<br /> <br /> '''11.02.2006''': #openttdcoop started the [http://www.tt-forums.net/viewtopic.php?t=23437 Challenge the #openttdcoop] campaign.<br /> <br /> '''10.02.2006''': [[User:Truelight|Truelight]] has been invited to the mainserver after playing several maps at the Sandbox! <br /> <br /> '''05.02.2006''': [[User:e1ko|e1ko]] joined our team as a [[Membership|full member]]!<br /> <br /> &lt;/noinclude&gt;</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2318 2006-07-30T17:19:37Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *{{User|e1ko|cz}}<br /> *{{User|Mucht|at}}<br /> *{{User|Osai|de}}<br /> *{{User|thgergo|hu}}<br /> *{{User|valhallasw|nl}}<br /> <br /> <br /> <br /> '''Currently Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *{{User|Brianetta|uk}} (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *{{User|OwenS|uk}}<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver and editing-rights on the wiki''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:Ammler|Ammler]]<br /> *[[User:bovik|bovik]]<br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Skasi|Skasi]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2317 2006-07-30T17:18:32Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *{{User|e1ko|cz}}<br /> *{{User|Mucht|at}}<br /> *{{User|Osai|de}}<br /> *{{User|thgergo|hu}}<br /> *{{User|valhallasw|nl}}<br /> <br /> <br /> <br /> '''Currently Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *[[User|Brianetta|uk]] (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *{{User|OwenS|uk}}<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver and editing-rights on the wiki''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:Ammler|Ammler]]<br /> *[[User:bovik|bovik]]<br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Skasi|Skasi]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2316 2006-07-30T17:18:00Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *{{User|e1ko|cz}}<br /> *{{User|Mucht|at}}<br /> *{{User|Osai|de}}<br /> *{{User|thgergo|hu}}<br /> *{{User|valhallasw|nl}}<br /> <br /> <br /> <br /> '''Currently Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *[[User:Brianetta|Brianetta|uk]] (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *{{User|OwenS|uk}}<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver and editing-rights on the wiki''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:Ammler|Ammler]]<br /> *[[User:bovik|bovik]]<br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Skasi|Skasi]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=IRC_Commands&diff=2061 2006-07-04T15:43:40Z

<p>Brianetta: Added note about /msg</p> <hr /> <div>In our channel #openttdcoop is a bot called &quot;sandbox&quot;.<br /> <br /> Sandbox understands several commands and gives you the the ability to communicate with people on The Sandbox Server via our IRC channel.<br /> <br /> {| border=&quot;1&quot; style=&quot;border: 1px solid black;&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; align=&quot;left&quot; width=&quot;75%&quot;<br /> |- style=&quot;border: 1px solid black;&quot;<br /> ! colspan=&quot;2&quot; | Commands<br /> |- style=&quot;border: 1px solid black;&quot;<br /> ! style=&quot;background:#ffdead;&quot; width=&quot;25%&quot; | Command<br /> ! style=&quot;background:#efefef;&quot; width=&quot;75%&quot;| Description<br /> <br /> {{IRC_Channel_Commands|!password|Shows the actual password of the Sandbox Server in our channel}}<br /> {{IRC_Channel_Commands|!players|Tells you how many people are playing on the Sandbox Server}}<br /> {{IRC_Channel_Commands|!url|Shows the link to the Sandbox-Server helppage}}<br /> {{IRC_Channel_Commands|!version|The version of Autopilot}}<br /> {{IRC_Channel_Commands|!wiki|Shows the link to our wiki}}<br /> |}<br /> <br /> You can also send commands to sandbox by private message (/msg) if you do not wish to disturb the flow of the channel.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2060 2006-07-04T15:28:40Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:e1ko|e1ko]]<br /> *[[User:Mucht|Mucht]]<br /> *[[User:Osai|Osai]]<br /> *[[User:thgergo|thgergo]]<br /> *[[User:valhallasw|valhallasw]]<br /> <br /> <br /> <br /> '''Currently Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *[[User:Brianetta|Brianetta]] (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:bovik|bovik]]<br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:OwenS|OwenS]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2059 2006-07-04T15:27:52Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:e1ko|e1ko]]<br /> *[[User:Mucht|Mucht]]<br /> *[[User:Osai|Osai]]<br /> *[[User:thgergo|thgergo]]<br /> *[[User:valhallasw|valhallasw]]<br /> <br /> <br /> <br /> '''Currently Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *[[User:Brianetta|Brianetta]] (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> *[[User:bovik|bovik]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> *[[User:OwenS|OwenS]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=User:Brianetta&diff=2022 2006-07-02T22:33:22Z

<p>Brianetta: </p> <hr /> <div>'''Born:''' 1975-05-19<br /> <br /> '''Home:''' Newcastle upon Tyne, UK<br /> <br /> '''Email:''' brian@ppcis.org<br /> <br /> '''Started playing TTD:''' December 1994<br /> <br /> '''Joined #openttdcoop:''' ~ came free with the new server<br /> <br /> '''Specialist on:''' autopilot and server admin<br /> <br /> '''Prefers:''' Realism, two-way track, small junctions<br /> <br /> Brianetta owns PPCIS.org and is on hand to provide technical support on the game servers and web sites which run on his server. He's the author of autopilot, which is a script that controls the dedicated server console when nobody is present.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2021 2006-07-02T22:30:30Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:e1ko|e1ko]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:Mucht|Mucht]]<br /> *[[User:Osai|Osai]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:thgergo|thgergo]]<br /> *[[User:valhallasw|valhallasw]]<br /> <br /> <br /> '''Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *[[User:Brianetta|Brianetta]] (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> *[[User:bovik|bovik]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Community:Members&diff=2020 2006-07-02T22:29:51Z

<p>Brianetta: </p> <hr /> <div>'''Active Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:dp|dp]]<br /> *[[User:e1ko|e1ko]]<br /> *[[User:guru3|Guru3]]<br /> *[[User:Mucht|Mucht]]<br /> *[[User:Osai|Osai]]<br /> *[[User:StarLite|StarLite]]<br /> *[[User:thgergo|thgergo]]<br /> *[[User:valhallasw|valhallasw]]<br /> <br /> <br /> '''Inactive Members of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ottd-king|ottd-king]]<br /> *[[User:Roo|Roo]]<br /> *[[User:ShaggZ|ShaggZ]]<br /> *[[User:xahodo|xahodo]]<br /> <br /> <br /> <br /> '''Honorary Members of #openttdcoop'''<br /> ----<br /> ''<br /> *[[User:Brianetta|Brianetta]] (our amiable host who is responsible for making #openttdcoop to such a vital community it is today)<br /> *[[User:TrueLight|TrueLight]]<br /> <br /> <br /> <br /> <br /> '''Aspirants of #openttdcoop'''<br /> ----<br /> <br /> *[[User:ChrisM|ChrisM]]<br /> *[[User:csuke|csuke]]<br /> *[[User:Hans|Hans]]<br /> *[[User:RichK|RichK]]<br /> *[[User:SerriaRomeo|SerriaRomeo]]<br /> *[[User:uLiKo|uLiKo]]<br /> ''Note: &quot;Aspirants&quot; have Access to the Mainserver''<br /> <br /> <br /> <br /> '''The usual suspects around the Sandbox'''<br /> ----<br /> <br /> *[[User:Cat666|Cat666]]<br /> *[[User:gryph|gryph]]<br /> *[[User:Nazirro|Nazirro]]<br /> *[[User:Thargor|Thargor]]<br /> *[[User:TMU|TMU]]<br /> *[[User:TorbenPaw|TorbenPaw]]<br /> *[[User:TrogdorX|TrogdorX]]<br /> *[[User:UnderBuilder|UnderBuilder]]<br /> *[[User:XeryusTC|XeryusTC]]<br /> *[[User:bovik|bovik]]<br /> *[[User:Ihmemies|Ihmemies]]<br /> *[[User:Osai|Osai]]<br /> ''And of course all the others above!''</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Basic_Networking&diff=2019 2006-07-01T13:33:52Z

<p>Brianetta: /* Mainline */</p> <hr /> <div>This page describes the hierarchy of line types that make up the rail nework in a standard coop game. There should never be any ambiguity at all about which sort of line a given stretch of track is a part.<br /> <br /> The hierarchy is three levels. The highest level is the [[Guides:Glossary:Mainline|Mainline]]. Mainlines make up the heavy trunk routes, and all train journeys will traverse one at some point. The intermediate level is the <br /> [[Guides:Glossary:Sideline|Sideline]]. Sidelines connect the mainlines to the branch lines. The lowest level is the Branch Line. These are the lines which run to resource stations.<br /> <br /> There is only one other type of line - a Principle Station line. These are like very heavy sidelines, and connect the principle stations directly to a mainline.<br /> <br /> == Mainline ==<br /> [[Guides:Glossary:Mainline|Mainlines]] run around the map . The provide the backbone of the network, and are fast, straight, obstruction free lines. If necessary, entire cities are sacrificed in their construction. They are connected to zero or more mainlines by [[Guides:Glossary:Backbone_Hub|Backbone Hubs]], and zero or more sidelines by [[Guides:Glossary:Sideline_Hub|Sideline Hubs]], and zero or more Priniple Station lines by modified [[Guides:Glossary:Backbone_Hub|Backbone Hubs]]. They can be left unterminated. Mainlines should be named and numbered.<br /> <br /> == Sideline ==<br /> [[Guides:Glossary:Sideline|Sidelines]] are connected to exactly one [[Guides:Glossary:Mainline|Mainline]], no more, no less. They are connected to zero or more Branch lines. They are not connected to stations, and they are not terminated by anything - they simply end, ready to be extended in future if necessary. Sidelines should be numbered, and occasionally named.<br /> <br /> == Branch line ==<br /> Branch lines are connected to exactly one [[Guides:Glossary:Sideline|Sideline]], no more, no less. They are connected to exactly one station, no more, no less. A branch line's purpose is as a dedicated line connecting a station to its Sideline. If further stations are built, they must be connected to the Sideline by their own dedicated branch line.<br /> <br /> ==Principal Station line==<br /> Principle Station lines are the major exception to the strict hierarchy, and are used where there is a single station used as the single drop-off for a given resource, or a single station used as the single pickup for a secondary cargo. These commonly include power stations, factories, food processing plants, sawmills, paper mills and so forth. They are Principle Stations. In general there is only one Princilpe Station handling a given cargo in the game, and it may be expected to handle several hundred trains. The Principle Station line is an extremely high bandwidth line connecting the Mainline directly to that station. They should be extremely well signposted.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Ruleset&diff=2017 2006-07-01T13:28:43Z

<p>Brianetta: /* Network Design */</p> <hr /> <div>==Note==<br /> Rules are used to ease the cooperative gameplay. Do not think of rules as laws, beeing punished if you don't follow them, but rules as a keypoint to play together.<br /> &lt;!-- &quot;keypoint&quot; wouldn't &quot;cornerstone&quot; be a better word? Not sure, that's why I didn't implement it --&gt;<br /> <br /> Please note: individual games may have different rulesets. These rules are a default set, and in different games different rules may be needed.<br /> <br /> =&lt;center&gt;Rules of our games&lt;/center&gt;=<br /> <br /> <br /> 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. <br /> <br /> 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. <br /> <br /> ===Communication===<br /> * '''You should be on IRC''' in case we need to have a discussion for which in game chat is not sufficient.<br /> * 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.<br /> * Try not to disrupt the whole network. If that's necessary, talk to everyone else; so they know what's going on.<br /> &lt;!-- Not sure if this sentence is needed, uncomment if it actually is needed:<br /> That's the point after all. --&gt;<br /> * Two people building in the same place is generally about as many as can be without a large ammount of confusion. So communicate what and where you are doing something.<br /> * 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. <br /> * ''No Sign overkill is needed!'' If you see obsolete signs, delete them (if you are not sure, keep them).<br /> * Language is english (due to popular demand ;-) )<br /> * We usually name our hubs; the first hub in a game with a sign &quot;Hub 1&quot;, and so on. This makes communication about routing simpler.<br /> <br /> ===Game Start===<br /> Games always start with coal, because it's the resource with the best distance/profit margins. The route should go a reasonable distance in a straight line. We should all discuss the start in IRC and all 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.<br /> The company color is always orange. Don't question this. It leads to nothing at all ;-)<br /> <br /> ===Construction===<br /> *Stick to our construction guides for a proper building style.<br /> *Avoid having a full loan like the plauge. 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.<br /> *Signals every second rail. It may look bad but tests have proven it is the most effective.<br /> *No 90 degree turns; make everything nice and smooth. This works better and acceleration math makes it go faster.<br /> *No 2*45 degree curves, due to too high speed penalties with the new train acceleration.<br /> *Stations are all equally long - depending on game type and strategy. In small games, there is rarely a need of more than 2 platforms - in larger games, like 1024x1024, you should stick to larger stations.<br /> *Avoid building diagonal tracks. You know why.<br /> *Use the &quot;[http://wiki.openttd.org/index.php/Stations#Ro-Ro Ro-Ro]&quot; style train stations whenever possible.<br /> *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).<br /> *We (well most of us) drive on the right side of the road, the trains should too ;-).<br /> *Never build industries until the entire map is connected. This is because the max industry limit could be reached accidently, which would prevent the building of a necessary industry such as a factory or oil refinery.<br /> <br /> ===Network Design===<br /> *The entire network is connected. Nothing off to the side.<br /> *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]].<br /> *We build sidelines (LR) that access the mainlines via Hubs. <br /> *Never, ever build dead-end lines ([[Guides:Glossary:Mainline|mainlines]] or [[Guides:Glossary:Sideline|sidelines]] that end at a station). Dead-end lines lead to uncomprehensive networks, and makes connections to further station via the same sideline unnecessary difficult, slow and/or clumsy.<br /> *Never ever connect a station directly to the mainline. This makes a fast mainline slow. Always connect a station via a sideline.<br /> *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.<br /> <br /> ===Trains===<br /> &lt;!-- The following rule may be obsolete by now --&gt;<br /> *Trainlength is depending on the gametype and strategy for the current map.<br /> *Shared orders are a must if more than one vehicle shares the same route.<br /> <br /> <br /> ===Sandbox===<br /> *The [[Sandbox_Server]] is a special case. Rules must be observed even more stringently than elsewhere.<br /> *The password for the Sandbox server is available only from [http://openttdcoop.ppcis.org/sandbox.php this page]. Bookmarking the page directly is not effective - you must visit the Wiki before you can play.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Basic_Networking&diff=2016 2006-07-01T13:23:10Z

<p>Brianetta: /* Sideline */</p> <hr /> <div>This page describes the hierarchy of line types that make up the rail nework in a standard coop game. There should never be any ambiguity at all about which sort of line a given stretch of track is a part.<br /> <br /> The hierarchy is three levels. The highest level is the [[Guides:Glossary:Mainline|Mainline]]. Mainlines make up the heavy trunk routes, and all train journeys will traverse one at some point. The intermediate level is the <br /> [[Guides:Glossary:Sideline|Sideline]]. Sidelines connect the mainlines to the branch lines. The lowest level is the Branch Line. These are the lines which run to resource stations.<br /> <br /> There is only one other type of line - a Principle Station line. These are like very heavy sidelines, and connect the principle stations directly to a mainline.<br /> <br /> == Mainline ==<br /> [[Guides:Glossary:Mainline|Mainlines]] run around the map . The provide the backbone of the network, and are fast, straight, obstruction free lines. If necessary, entire cities are sacrificed in their construction. They are connected to zero or more mainlines by [[Guides:Glossary:Backbone_Hub|Backbone Hubs]], and zero or more sidelines by [[Guides:Glossary:Sideline_Hub|Sideline Hubs]]. They can be left unterminated. Mainlines should be named and numbered.<br /> <br /> == Sideline ==<br /> [[Guides:Glossary:Sideline|Sidelines]] are connected to exactly one [[Guides:Glossary:Mainline|Mainline]], no more, no less. They are connected to zero or more Branch lines. They are not connected to stations, and they are not terminated by anything - they simply end, ready to be extended in future if necessary. Sidelines should be numbered, and occasionally named.<br /> <br /> == Branch line ==<br /> Branch lines are connected to exactly one [[Guides:Glossary:Sideline|Sideline]], no more, no less. They are connected to exactly one station, no more, no less. A branch line's purpose is as a dedicated line connecting a station to its Sideline. If further stations are built, they must be connected to the Sideline by their own dedicated branch line.<br /> <br /> ==Principal Station line==<br /> Principle Station lines are the major exception to the strict hierarchy, and are used where there is a single station used as the single drop-off for a given resource, or a single station used as the single pickup for a secondary cargo. These commonly include power stations, factories, food processing plants, sawmills, paper mills and so forth. They are Principle Stations. In general there is only one Princilpe Station handling a given cargo in the game, and it may be expected to handle several hundred trains. The Principle Station line is an extremely high bandwidth line connecting the Mainline directly to that station. They should be extremely well signposted.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Basic_Networking&diff=2015 2006-07-01T13:22:04Z

<p>Brianetta: </p> <hr /> <div>This page describes the hierarchy of line types that make up the rail nework in a standard coop game. There should never be any ambiguity at all about which sort of line a given stretch of track is a part.<br /> <br /> The hierarchy is three levels. The highest level is the [[Guides:Glossary:Mainline|Mainline]]. Mainlines make up the heavy trunk routes, and all train journeys will traverse one at some point. The intermediate level is the <br /> [[Guides:Glossary:Sideline|Sideline]]. Sidelines connect the mainlines to the branch lines. The lowest level is the Branch Line. These are the lines which run to resource stations.<br /> <br /> There is only one other type of line - a Principle Station line. These are like very heavy sidelines, and connect the principle stations directly to a mainline.<br /> <br /> == Mainline ==<br /> [[Guides:Glossary:Mainline|Mainlines]] run around the map . The provide the backbone of the network, and are fast, straight, obstruction free lines. If necessary, entire cities are sacrificed in their construction. They are connected to zero or more mainlines by [[Guides:Glossary:Backbone_Hub|Backbone Hubs]], and zero or more sidelines by [[Guides:Glossary:Sideline_Hub|Sideline Hubs]]. They can be left unterminated. Mainlines should be named and numbered.<br /> <br /> == Sideline ==<br /> [[Guides:Glossary:Sideline|Sidelines]] are connected to exactly one [Guides:Glossary:Mainline|Mainline]], no more, no less. They are connected to zero or more Branch lines. They are not connected to stations, and they are not terminated by anything - they simply end, ready to be extended in future if necessary. Sidelines should be numbered, and occasionally named.<br /> <br /> == Branch line ==<br /> Branch lines are connected to exactly one [[Guides:Glossary:Sideline|Sideline]], no more, no less. They are connected to exactly one station, no more, no less. A branch line's purpose is as a dedicated line connecting a station to its Sideline. If further stations are built, they must be connected to the Sideline by their own dedicated branch line.<br /> <br /> ==Principal Station line==<br /> Principle Station lines are the major exception to the strict hierarchy, and are used where there is a single station used as the single drop-off for a given resource, or a single station used as the single pickup for a secondary cargo. These commonly include power stations, factories, food processing plants, sawmills, paper mills and so forth. They are Principle Stations. In general there is only one Princilpe Station handling a given cargo in the game, and it may be expected to handle several hundred trains. The Principle Station line is an extremely high bandwidth line connecting the Mainline directly to that station. They should be extremely well signposted.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Servers&diff=2002 2006-06-25T20:33:27Z

<p>Brianetta: </p> <hr /> <div>Our community #openttdcoop consists of '''two servers''':<br /> <br /> <br /> ----<br /> <br /> <br /> [[Main_Server|'''The mainserver:''']] feel free to watch us playing: search for the '''server name &quot;#openttdcoop&quot;'''. The password needed to join as a watching client is '''&quot;coop&quot;'''. Playing access (company password) is granted to many people, see [[Membership]] for further details.<br /> <br /> <br /> For a list of games which took place on our mainserver, look at [[Mainserver:Archive]]<br /> <br /> <br /> ''rcon on the mainserver is granted to every full member of #openttdcoop.''<br /> <br /> <br /> ----<br /> <br /> <br /> [[Sandbox_Server|'''The Sandbox:''']] if you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at [[Membership]] and [[Sandbox_Server]]. Feel free to join our community of aspirants for #openttdcoop membership.<br /> <br /> <br /> For a list of games which took place on our sandbox server, look at [[Sandbox:Archive]]<br /> <br /> <br /> ''rcon on the sandbox server is granted to every full member of #openttdcoop and SerriaRomero, Hans, ChrisM, Osai and uLiKo.''<br /> <br /> ----</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Ruleset&diff=2001 2006-06-25T18:33:37Z

<p>Brianetta: </p> <hr /> <div>==Note==<br /> Rules are used to ease the cooperative gameplay. Do not think of rules as laws, beeing punished if you don't follow them, but rules as a keypoint to play together.<br /> &lt;!-- &quot;keypoint&quot; wouldn't &quot;cornerstone&quot; be a better word? Not sure, that's why I didn't implement it --&gt;<br /> <br /> Please note: individual games may have different rulesets. These rules are a default set, and in different games different rules may be needed.<br /> <br /> =&lt;center&gt;Rules of our games&lt;/center&gt;=<br /> <br /> <br /> 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. <br /> <br /> 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. <br /> <br /> ===Communication===<br /> * '''You should be on IRC''' in case we need to have a discussion for which in game chat is not sufficient.<br /> * 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.<br /> * Try not to disrupt the whole network. If that's necessary, talk to everyone else; so they know what's going on.<br /> &lt;!-- Not sure if this sentence is needed, uncomment if it actually is needed:<br /> That's the point after all. --&gt;<br /> * Two people building in the same place is generally about as many as can be without a large ammount of confusion. So communicate what and where you are doing something.<br /> * 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. <br /> * ''No Sign overkill is needed!'' If you see obsolete signs, delete them (if you are not sure, keep them).<br /> * Language is english (due to popular demand ;-) )<br /> * We usually name our hubs; the first hub in a game with a sign &quot;Hub 1&quot;, and so on. This makes communication about routing simpler.<br /> <br /> ===Game Start===<br /> Games always start with coal, because it's the resource with the best distance/profit margins. The route should go a reasonable distance in a straight line. We should all discuss the start in IRC and all 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.<br /> The company color is always orange. Don't question this. It leads to nothing at all ;-)<br /> <br /> ===Construction===<br /> *Stick to our construction guides for a proper building style.<br /> *Avoid having a full loan like the plauge. 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.<br /> *Signals every second rail. It may look bad but tests have proven it is the most effective.<br /> *No 90 degree turns; make everything nice and smooth. This works better and acceleration math makes it go faster.<br /> *No 2*45 degree curves, due to too high speed penalties with the new train acceleration.<br /> *Stations are all equally long - depending on game type and strategy. In small games, there is rarely a need of more than 2 platforms - in larger games, like 1024x1024, you should stick to larger stations.<br /> *Avoid building diagonal tracks. You know why.<br /> *Use the &quot;[http://wiki.openttd.org/index.php/Stations#Ro-Ro Ro-Ro]&quot; style train stations whenever possible.<br /> *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).<br /> *We (well most of us) drive on the right side of the road, the trains should too ;-).<br /> *Never build industries until the entire map is connected. This is because the max industry limit could be reached accidently, which would prevent the building of a necessary industry such as a factory or oil refinery.<br /> <br /> ===Network Design===<br /> *The entire network is connected. Nothing off to the side.<br /> *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.<br /> *We build sidelines (LR) that access the mainlines via Hubs. <br /> *Never, ever build dead-end lines ([[Guides:Glossary:Mainline|mainlines]] or [[Guides:Glossary:Sideline|sidelines]] that end at a station). Dead-end lines lead to uncomprehensive networks, and makes connections to further station via the same sideline unnecessary difficult, slow and/or clumsy.<br /> *Never ever connect a station directly to the mainline. This makes a fast mainline slow. Always connect a station via a sideline.<br /> *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.<br /> <br /> ===Trains===<br /> &lt;!-- The following rule may be obsolete by now --&gt;<br /> *Trainlength is depending on the gametype and strategy for the current map.<br /> *Shared orders are a must if more than one vehicle shares the same route.<br /> <br /> <br /> ===Sandbox===<br /> *The [[Sandbox_Server]] is a special case. Rules must be observed even more stringently than elsewhere.<br /> *The password for the Sandbox server is available only from [http://openttdcoop.ppcis.org/sandbox.php this page]. Bookmarking the page directly is not effective - you must visit the Wiki before you can play.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Public_Server&diff=2000 2006-06-25T18:33:33Z

<p>Brianetta: </p> <hr /> <div>'''For a list of games which took place on our sandbox server, look at [[Sandbox:Archive]]'''<br /> <br /> If you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at [[Membership]] and [[Sandbox_Server]]. Feel free to join our community of aspirants for #openttdcoop membership. Connection details are available on the [http://openttdcoop.ppcis.org/sandbox.php Sandbox server page].<br /> <br /> ''rcon on the sandbox server is granted to every full member of #openttdcoop and SerriaRomero, Hans, ChrisM, Osai and uLiKo, last and not least is Brianetta the server owner.''<br /> <br /> <br /> =&lt;center&gt;The #openttdcoop &quot;Sandbox Server&quot;&lt;/center&gt;=<br /> <br /> Since new players on #openttdcoop often face rather complex games on our mainserver, we decided to set up a so-called &quot;sandbox server&quot; where players have the chance to learn the very basic concepts of cooperative gameplay. On this page, you will find a guide for the first steps into our sandbox.<br /> <br /> '''All members of #openttdcoop have rcon to the sandbox server.''' <br /> <br /> ===What are the keypoints of the sandbox server?===<br /> <br /> * First of all: '''BE SURE TO CONNECT TO THE IRC CHANNEL!''' No games can take place if we do not meet up in the channel! If you are not willing to join us in the channel it is not possible for you to become a player/member of #openttdcoop due to the lack of communication between the community and you.<br /> * New players will get some tutorial guidance by full members of #openttdcoop but start playing right from the start<br /> * Smaller maps will be played (256*256 - max. 512*512). One map lasts until everything is connected and/or optimized. <br /> * There will be some kind of &quot;building convention&quot; like a &quot;coding convention&quot; on programming. This convention consists of some basic rules of &quot;clever building&quot;. Be sure to know this convention (as listed below).<br /> * Feel free to build whatever you want - you'll see the errors coming up in a growing network. Our [http://atlantis.beetjevreemd.nl:8080/wiki/index.php/Guides Guides] will help you on the very basics of good networking etc.<br /> * This server is run by an autopilot - basically an answering machine for OpenTTD servers. It is configured to keep the game paused unless at least two players are connected.<br /> <br /> ===How / Where / When ?===<br /> <br /> First of all, be sure to join our [irc://irc.freenode.org/openttdcoop IRC channel]. You will get information on games and servers. Players find together in the channel and start new or continue existing games. Also, passwords are exchanged in the channel. <br /> <br /> An advantage of having a channel on the freenode IRC network is the circumstance of being &quot;next to&quot; the [irc://irc.freenode.org/openttd IRC channel] (#openttdcoop started there). A disadvantage of using freenode is the need for registration in order to receive/send queries. Since we use queries to send our passwords to players you should be sure of being registered (it doesnt hurt, btw).<br /> <br /> If you live in the european part of this planet you probably will have no problem related to our usual playing times. We mostly play between 18.00 to 01.00 (sometimes open ended) GMT during the weekdays and some afternoon sessions on weekends.<br /> <br /> <br /> ===The Sandbox Building Convention===<br /> <br /> * First of all: set your signaling length to &quot;2 tiles&quot; (Patch Options).<br /> * React on the ingame chat, we are not typing for nothing.<br /> * If you build a Hub, name it like &quot;Slh number / Name&quot; for a Sidelinehub (which is, relating to our Guides, a Sideline-to-Mainline-Hub) or &quot;Bbh number / name&quot; for a Mainline-to-Mainline-Hub. Be sure to use '''''exactly''''' this string (with spaces etc) - if you view the signlist, the Hubs will be sorted in the right way then and only then. Also: if we are talking about Hubs and you want to discuss about them too, simply follow the signlist to the corresponding Hub.<br /> * Cooperation is about communication! Always tell your collegues what you are doing and discuss planed tracks/junctions etc. Our members can - of course - help you on some decisions.<br /> * Unilateral decisions by players are against the rules. Major changes to landscape, network and so on are to be discussed with other players beforehand, and agreed upon before implementation. Players should be on the IRC channel if the in-game chat is insufficient.<br /> * There must be a network plan. The network plan must be followed. If players decide to do something different, the plan must change first.<br /> * After you build new station and connect it to the sideline say &quot;station_name connected&quot;.<br /> * If you build big and complicated station like pick up or drop off, place a sign with your name near it.<br /> * Take care about the rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.<br /> * If you need depot and no one is nearby, build service center. Never build depot at side line.<br /> * Don't log in as player. Change your name before connecting to our server.<br /> * Network takes precedence over trains. Don't build hundreds of trains until the network is proven.<br /> * Enjoy the cooperation.<br /> <br /> ===Links to the Chatlog for the Sandbox===<br /> <br /> &lt;center&gt;Full Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog&lt;/center&gt;<br /> <br /> &lt;center&gt;Running Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog/last20.php&lt;/center&gt;<br /> <br /> ===Overview of Games so Far===<br /> <br /> Visit the [[Sandbox:Archive]] !</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Public_Server&diff=1999 2006-06-25T17:44:37Z

<p>Brianetta: /* &lt;center&gt;The #openttdcoop &quot;Sandbox Server&quot;&lt;/center&gt; */</p> <hr /> <div>'''For a list of games which took place on our sandbox server, look at [[Sandbox:Archive]]'''<br /> <br /> If you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at [[Membership]] and [[Sandbox_Server]]. Feel free to join our community of aspirants for #openttdcoop membership. You will find the server under the '''name &quot;#openttdcoop Sandbox&quot;''', Password, again, is '''coop'''.<br /> <br /> ''rcon on the sandbox server is granted to every full member of #openttdcoop and SerriaRomero, Hans, ChrisM, Osai and uLiKo, last and not least is Brianetta the server owner.''<br /> <br /> <br /> =&lt;center&gt;The #openttdcoop &quot;Sandbox Server&quot;&lt;/center&gt;=<br /> <br /> Since new players on #openttdcoop often face rather complex games on our mainserver, we decided to set up a so-called &quot;sandbox server&quot; where players have the chance to learn the very basic concepts of cooperative gameplay. On this page, you will find a guide for the first steps into our sandbox.<br /> <br /> '''All members of #openttdcoop have rcon to the sandbox server.''' <br /> <br /> ===What are the keypoints of the sandbox server?===<br /> <br /> * First of all: '''BE SURE TO CONNECT TO THE IRC CHANNEL!''' No games can take place if we do not meet up in the channel! If you are not willing to join us in the channel it is not possible for you to become a player/member of #openttdcoop due to the lack of communication between the community and you.<br /> * New players will get some tutorial guidance by full members of #openttdcoop but start playing right from the start<br /> * Smaller maps will be played (256*256 - max. 512*512). One map lasts until everything is connected and/or optimized. <br /> * There will be some kind of &quot;building convention&quot; like a &quot;coding convention&quot; on programming. This convention consists of some basic rules of &quot;clever building&quot;. Be sure to know this convention (as listed below).<br /> * Feel free to build whatever you want - you'll see the errors coming up in a growing network. Our [http://atlantis.beetjevreemd.nl:8080/wiki/index.php/Guides Guides] will help you on the very basics of good networking etc.<br /> * This server is run by an autopilot - basically an answering machine for OpenTTD servers. It is configured to keep the game paused unless at least two players are connected.<br /> <br /> ===How / Where / When ?===<br /> <br /> First of all, be sure to join our [irc://irc.freenode.org/openttdcoop IRC channel]. You will get information on games and servers. Players find together in the channel and start new or continue existing games. Also, passwords are exchanged in the channel. <br /> <br /> An advantage of having a channel on the freenode IRC network is the circumstance of being &quot;next to&quot; the [irc://irc.freenode.org/openttd IRC channel] (#openttdcoop started there). A disadvantage of using freenode is the need for registration in order to receive/send queries. Since we use queries to send our passwords to players you should be sure of being registered (it doesnt hurt, btw).<br /> <br /> If you live in the european part of this planet you probably will have no problem related to our usual playing times. We mostly play between 18.00 to 01.00 (sometimes open ended) GMT during the weekdays and some afternoon sessions on weekends.<br /> <br /> <br /> ===The Sandbox Building Convention===<br /> <br /> * First of all: set your signaling length to &quot;2 tiles&quot; (Patch Options).<br /> * React on the ingame chat, we are not typing for nothing.<br /> * If you build a Hub, name it like &quot;Slh number / Name&quot; for a Sidelinehub (which is, relating to our Guides, a Sideline-to-Mainline-Hub) or &quot;Bbh number / name&quot; for a Mainline-to-Mainline-Hub. Be sure to use '''''exactly''''' this string (with spaces etc) - if you view the signlist, the Hubs will be sorted in the right way then and only then. Also: if we are talking about Hubs and you want to discuss about them too, simply follow the signlist to the corresponding Hub.<br /> * Cooperation is about communication! Always tell your collegues what you are doing and discuss planed tracks/junctions etc. Our members can - of course - help you on some decisions.<br /> * Unilateral decisions by players are against the rules. Major changes to landscape, network and so on are to be discussed with other players beforehand, and agreed upon before implementation. Players should be on the IRC channel if the in-game chat is insufficient.<br /> * There must be a network plan. The network plan must be followed. If players decide to do something different, the plan must change first.<br /> * After you build new station and connect it to the sideline say &quot;station_name connected&quot;.<br /> * If you build big and complicated station like pick up or drop off, place a sign with your name near it.<br /> * Take care about the rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.<br /> * If you need depot and no one is nearby, build service center. Never build depot at side line.<br /> * Don't log in as player. Change your name before connecting to our server.<br /> * Network takes precedence over trains. Don't build hundreds of trains until the network is proven.<br /> * Enjoy the cooperation.<br /> <br /> ===Links to the Chatlog for the Sandbox===<br /> <br /> &lt;center&gt;Full Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog&lt;/center&gt;<br /> <br /> &lt;center&gt;Running Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog/last20.php&lt;/center&gt;<br /> <br /> ===Overview of Games so Far===<br /> <br /> Visit the [[Sandbox:Archive]] !</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Public_Server&diff=1998 2006-06-25T17:38:47Z

<p>Brianetta: /* The Sandbox Building Convention */</p> <hr /> <div>'''For a list of games which took place on our sandbox server, look at [[Sandbox:Archive]]'''<br /> <br /> If you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at [[Membership]] and [[Sandbox_Server]]. Feel free to join our community of aspirants for #openttdcoop membership. You will find the server under the '''name &quot;#openttdcoop Sandbox&quot;''', Password, again, is '''coop'''.<br /> <br /> ''rcon on the sandbox server is granted to every full member of #openttdcoop and SerriaRomero, Hans, ChrisM, Osai and uLiKo, last and not least is Brianetta the server owner.''<br /> <br /> <br /> =&lt;center&gt;The #openttdcoop &quot;Sandbox Server&quot;&lt;/center&gt;=<br /> <br /> Since new players on #openttdcoop often face rather complex games on our mainserver, we decided to set up a so-called &quot;sandbox server&quot; where players have the chance to learn the very basic concepts of cooperative gameplay. On this page, you will find a guide for the first steps into our sandbox.<br /> <br /> '''All members of #openttdcoop have rcon to the sandbox server.''' <br /> <br /> ===What are the keypoints of the sandbox server?===<br /> <br /> * First of all: '''BE SURE TO CONNECT TO THE IRC CHANNEL!''' No games can take place if we do not meet up in the channel! If you are not willing to join us in the channel it is not possible for you to become a player/member of #openttdcoop due to the lack of communication between the community and you.<br /> * New players will get some tutorial guidance by full members of #openttdcoop but start playing right from the start<br /> * Smaller maps will be played (256*256 - max. 512*512). One map lasts until everything is connected and/or optimized. <br /> * There will be some kind of &quot;building convention&quot; like a &quot;coding convention&quot; on programming. This convention consists of some basic rules of &quot;clever building&quot;. Be sure to know this convention (as listed below).<br /> * Feel free to build whatever you want - you'll see the errors coming up in a growing network. Our [http://atlantis.beetjevreemd.nl:8080/wiki/index.php/Guides Guides] will help you on the very basics of good networking etc.<br /> * This server is run by an autopilot - basically an answering machine for OpenTTD servers. It is configured to keep the game paused unless at least two players are connected.<br /> <br /> ===How / Where / When ?===<br /> <br /> First of all, be sure to join our [irc://irc.freenode.org/openttdcoop IRC channel]. You will get information on games and servers. Players find together in the channel and start new or continue existing games. Also, passwords are exchanged in the channel. <br /> <br /> An advantage of having a channel on the freenode IRC network is the circumstance of being &quot;next to&quot; the [irc://irc.freenode.org/openttd IRC channel] (#openttdcoop started there). A disadvantage of using freenode is the need for registration in order to receive/send queries. Since we use queries to send our passwords to players you should be sure of being registered (it doesnt hurt, btw).<br /> <br /> If you live in the european part of this planet you probably will have no problem related to our usual playing times. We mostly play between 18.00 to 01.00 (sometimes open ended) GMT during the weekdays and some afternoon sessions on weekends.<br /> <br /> <br /> ===The Sandbox Building Convention===<br /> <br /> * First of all: set your signaling length to &quot;2 tiles&quot; (Patch Options).<br /> * React on the ingame chat, we are not typing for nothing.<br /> * If you build a Hub, name it like &quot;Slh number / Name&quot; for a Sidelinehub (which is, relating to our Guides, a Sideline-to-Mainline-Hub) or &quot;Bbh number / name&quot; for a Mainline-to-Mainline-Hub. Be sure to use '''''exactly''''' this string (with spaces etc) - if you view the signlist, the Hubs will be sorted in the right way then and only then. Also: if we are talking about Hubs and you want to discuss about them too, simply follow the signlist to the corresponding Hub.<br /> * Cooperation is about communication! Always tell your collegues what you are doing and discuss planed tracks/junctions etc. Our members can - of course - help you on some decisions.<br /> * After you build new station and connect it to the sideline say &quot;station_name connected&quot;.<br /> * If you build big and complicated station like pick up or drop off, place a sign with your name near it.<br /> * Take care about the rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.<br /> * If you need depot and no one is nearby, build service center. Never build depot at side line.<br /> * Don't log in as player. Change your name before connecting to our server.<br /> * Network takes precedence over trains. Don't build hundreds of trains until the network is proven.<br /> * Enjoy the cooperation.<br /> <br /> ===Links to the Chatlog for the Sandbox===<br /> <br /> &lt;center&gt;Full Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog&lt;/center&gt;<br /> <br /> &lt;center&gt;Running Log&lt;/center&gt; &lt;center&gt;http://openttdcoop.ppcis.org/chatlog/last20.php&lt;/center&gt;<br /> <br /> ===Overview of Games so Far===<br /> <br /> Visit the [[Sandbox:Archive]] !</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Removing_a_city&diff=1843 2006-01-15T02:26:15Z

<p>Brianetta: reworded, minor grammar corrections</p> <hr /> <div>Sometimes when building a station or building the main (or side) line you come across some cities. Sometimes you have to remove them so there is more room for our networks. (Please note that this isn't cheap and only perform this when we more than enough money. Else I would suggest place a sign and wait till there is more money) Removing is done in several steps:<br /> <br /> == Removing the first buildings ==<br /> First look at the rating of the authorities of that city. If it's like Very Good or better it's might be smart to remove some buildings like a football station, church and offices. These all need ratings of Very good or better. Removing a simple house will be done later. If the rating is Appaling move to the next step or else remove some houses or something.<br /> <br /> If you don't know what kind of building everything is. Use the &quot;Land area information tool&quot;. It's that last button in the topside buttons bar (with pause, settings, save, map etc.). If you still don't know if a building can only be removed with Very good rating or higher I would say you remove the buildings that look the most expensive.<br /> <br /> == Placing trees ==<br /> I expect your rating is now like Appaling so that means we need to raise that up. We don't use bribe now because that is way too expensive and dangerous. What we do first is demolish everything in a range of something like 10 - 20 squares (please avoid properties like tracks, stations, purchused land etc.). After this is done place trees in the field you just blew up. We don't need fully grown trees, just little ones are enough. Now continue with the next step<br /> <br /> == Removing some (cheap) buildings ==<br /> Now your rating is something near Good. This would not give us the abbility to remove everything but at least we can remove roads and houses which a city has a lot of. I found out you can demolish up like 7 - 8 road pieces or 2 houses + 1 road piece a time. I suggest you demolish only houses (and other buildings) untill you can't. Then try to remove some roads. If there are still houses or roads repeat the previous step again. Do this untill there only buildings left that can't be removed.<br /> <br /> == Removing the last buildings ==<br /> If it wasn't a very big city , the result you have now must be only a few buildings left. Now it's time for the expensive part (I suggest you save first before doing this because you could be caught): Bribing. To save money, make sure your rating now is 'Good'. If it isn't repeat step 2 again. If you don't think you have enough money purchase every tile around the city (and inside) to avoid them from growing again and come back later when you have enough money.<br /> <br /> Now I asume you have enough money to do this. Bribe untill your rating is Excellent and remove some buildings. Repeat this untill there is nothing left. Now purchase the land of the city. This should be like a square of 10 by 10 tiles. Now you have succesfully removed the city.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=User:Brianetta&diff=1842 2006-01-14T18:28:33Z

<p>Brianetta: </p> <hr /> <div>Brianetta owns PPCIS.org and is on hand to provide technical support on the game servers and web sites which run on his server.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=User:Brianetta&diff=1841 2006-01-14T18:28:17Z

<p>Brianetta: </p> <hr /> <div>Brianetta owns PPCIS.org and is on hand to provide technical support on the game servers and web sites which run on his server,</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=Public_Server&diff=1839 2006-01-14T00:19:35Z

<p>Brianetta: /* What are the keypoints of the sandbox server? */</p> <hr /> <div>'''For a list of games which took place on our sandbox server, look at [[Sandbox:Archive]]'''<br /> <br /> If you heard of #openttdcoop and would like to make the first steps toward a membership in our community, simply read what you have to do at [[Membership]] and [[Sandbox_Server]]. Feel free to join our community of aspirants for #openttdcoop membership. You will find the server under the '''name &quot;#openttdcoop Sandbox&quot;''', Password, again, is '''coop'''.<br /> <br /> ''rcon on the sandbox server is granted to every full member of #openttdcoop and SerriaRomero, Hans, ChrisM, Osai and uLiKo, last and not least is Brianetta the server owner.''<br /> <br /> <br /> =&lt;center&gt;The #openttdcoop &quot;Sandbox Server&quot;&lt;/center&gt;=<br /> <br /> Since new players on #openttdcoop often face rather complex games on our mainserver, we decided to set up a so-called &quot;sandbox server&quot; where players have the chance to learn the very basic concepts of cooperative gameplay. On this page, you will find a guide for the first steps into our sandbox.<br /> <br /> '''All members of #openttdcoop have rcon to the sandbox server.''' <br /> <br /> ===What are the keypoints of the sandbox server?===<br /> <br /> * First of all: '''BE SURE TO CONNECT TO THE IRC CHANNEL!''' No games can take place if we do not meet up in the channel! If you are not willing to join us in the channel it is not possible for you to become a player/member of #openttdcoop due to the lack of communication between the community and you.<br /> * New players will get some tutorial guidance by full members of #openttdcoop but start playing right from the start<br /> * Smaller maps will be played (256*256 - max. 512*512). One map lasts until everything is connected and/or optimized. <br /> * There will be some kind of &quot;building convention&quot; like a &quot;coding convention&quot; on programming. This convention consists of some basic rules of &quot;clever building&quot;. Be sure to know this convention (as listed below).<br /> * Feel free to build whatever you want - you'll see the errors coming up in a growing network. Our [http://atlantis.beetjevreemd.nl:8080/wiki/index.php/Guides Guides] will help you on the very basics of good networking etc.<br /> * This server is run by an autopilot - basically an answering machine for OpenTTD servers. It is configured to keep the game paused unless at least two players are connected.<br /> <br /> ===How / Where / When ?===<br /> <br /> First of all, be sure to join our [irc://irc.freenode.org/openttdcoop IRC channel]. You will get information on games and servers. Players find together in the channel and start new or continue existing games. Also, passwords are exchanged in the channel. <br /> <br /> An advantage of having a channel on the freenode IRC network is the circumstance of being &quot;next to&quot; the [irc://irc.freenode.org/openttd IRC channel] (#openttdcoop started there). A disadvantage of using freenode is the need for registration in order to receive/send queries. Since we use queries to send our passwords to players you should be sure of being registered (it doesnt hurt, btw).<br /> <br /> If you live in the european part of this planet you probably will have no problem related to our usual playing times. We mostly play between 18.00 to 01.00 (sometimes open ended) GMT during the weekdays and some afternoon sessions on weekends.<br /> <br /> <br /> ===The Sandbox Building Convention===<br /> <br /> * First of all: set your signaling length to &quot;2 tiles&quot; (Patch Options).<br /> * React on the ingame chat, we are not typing for nothing.<br /> * If you build a Hub, name it like &quot;Slh number / Name&quot; for a Sidelinehub (which is, relating to our Guides, a Sideline-to-Mainline-Hub) or &quot;Bbh number / name&quot; for a Mainline-to-Mainline-Hub. Be sure to use '''''exactly''''' this string (with spaces etc) - if you view the signlist, the Hubs will be sorted in the right way then and only then. Also: if we are talking about Hubs and you want to discuss about them too, simply follow the signlist to the corresponding Hub.<br /> * Cooperation is about communication! Always tell your collegues what you are doing and discuss planed tracks/junctions etc. Our members can - of course - help you on some decisions.<br /> <br /> <br /> ===Overview of Games so Far===<br /> <br /> Visit the [[Sandbox:Archive]] !</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=History&diff=1837 2006-01-14T00:10:03Z

<p>Brianetta: /* The Very Beginnings Brian was here */</p> <hr /> <div>==The Very Beginnings==<br /> <br /> ''#''openttdcoop started in late 2004/early 2005. guru3, ShaggZ, xahodo, Mucht and dp met up in the IRC channel of the OpenTTD community, #openttd on the freenode IRC network. There were many reasons for starting an all-seperate community dedicated for doing cooperative gameplay:<br /> * Teamplay is fun<br /> * Your gaming skills improve if you exchange your building styles in a non-competitive environment<br /> * The mapcycle gets faster - you don't have to play on one map for days to complete it since many players are helping to build a network. Th<br /> <br /> guru3 started to host the first dedicated server. The early maps were 256x256 only since OTTD did not support bigmaps back then.<br /> <br /> ==The Restructuring==<br /> <br /> After a period of little activity during the spring/summer period of 2005, most members of #openttdcoop got together again in September 2005. In the meantime, OpenTTD had seen heavy development, which allowed for the creation of many new strategies and styles.<br /> <br /> The community also decided to change and expand its own structure:<br /> * There would be a Wiki instead of a webpage in order to improve information flow.<br /> * There would be a definition of 'Membership' and a clear regulation on how to become a member<br /> * There would be a unified appearence of #openttdcoop (signature for [http://tt-forums.net tt-forums], logo, etc.)<br /> <br /> Thanks to valhallasw, who hosts the wiki, guru3, who hosts our signature and most members and close-to-membership players, the goals above were completed.<br /> <br /> ==The 'Finally-at-Home'-Period==<br /> <br /> One day Brianetta joined our community and offered us the possibility to host a dedicated server for our games. We gratefully agreed to his offer and are proud to have two servers online now:<br /> * The mainserver which is restricted playground for members and trusted players<br /> * The Sandbox Server which is the playground for our upcoming players, learning platform and funpark at once.<br /> <br /> After setting up the dedicated servers many aspirants joined our community. ''#''openttdcoop is now well-structured and became a known part of the OpenTTD-Universe.</div>

Brianetta https://wiki.openttdcoop.org/index.php?title=History&diff=1836 2006-01-14T00:09:10Z

<p>Brianetta: /* The Very Beginnings */</p> <hr /> <div>==The Very Beginnings Brian was here==<br /> <br /> ''#''openttdcoop started in late 2004/early 2005. guru3, ShaggZ, xahodo, Mucht and dp met up in the IRC channel of the OpenTTD community, #openttd on the freenode IRC network. There were many reasons for starting an all-seperate community dedicated for doing cooperative gameplay:<br /> * Teamplay is fun<br /> * Your gaming skills improve if you exchange your building styles in a non-competitive environment<br /> * The mapcycle gets faster - you don't have to play on one map for days to complete it since many players are helping to build a network. Th<br /> <br /> guru3 started to host the first dedicated server. The early maps were 256x256 only since OTTD did not support bigmaps back then.<br /> <br /> ==The Restructuring==<br /> <br /> After a period of little activity during the spring/summer period of 2005, most members of #openttdcoop got together again in September 2005. In the meantime, OpenTTD had seen heavy development, which allowed for the creation of many new strategies and styles.<br /> <br /> The community also decided to change and expand its own structure:<br /> * There would be a Wiki instead of a webpage in order to improve information flow.<br /> * There would be a definition of 'Membership' and a clear regulation on how to become a member<br /> * There would be a unified appearence of #openttdcoop (signature for [http://tt-forums.net tt-forums], logo, etc.)<br /> <br /> Thanks to valhallasw, who hosts the wiki, guru3, who hosts our signature and most members and close-to-membership players, the goals above were completed.<br /> <br /> ==The 'Finally-at-Home'-Period==<br /> <br /> One day Brianetta joined our community and offered us the possibility to host a dedicated server for our games. We gratefully agreed to his offer and are proud to have two servers online now:<br /> * The mainserver which is restricted playground for members and trusted players<br /> * The Sandbox Server which is the playground for our upcoming players, learning platform and funpark at once.<br /> <br /> After setting up the dedicated servers many aspirants joined our community. ''#''openttdcoop is now well-structured and became a known part of the OpenTTD-Universe.</div>

Brianetta