https://wiki.openttdcoop.org/api.php?action=feedcontributions&user=Thraxian&feedformat=atom#openttdcoop wiki - User contributions [en]2024-03-28T10:25:05ZUser contributionsMediaWiki 1.25.2https://wiki.openttdcoop.org/index.php?title=Help:Range_blocks&diff=11898Help:Range blocks2010-11-15T15:15:47Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Osai</p>
<hr />
<div>{{PD Help Page}}<br />
'''Range blocks''' are technical restrictions applied through [[Special:Blockip]] to a group of [http://en.wikipedia.org/wiki/IP_addresses IP addresses] that prevent them from editing, creating new accounts, sending email through the wiki interface, et cetera. Registered accounts editing from these IP addresses will also be blocked, unless you check the box to only block anonymous editors.<br />
<br />
Range blocking is enabled on all [http://en.wikipedia.org/wiki/Wikimedia_Foundation Wikimedia] wikis; to enable it on other wikis, add "<code>{{mediawiki|Manual:$wgSysopRangeBans|$wgSysopRangeBans}} = true;</code>" in <tt>{{mediawiki|Manual:LocalSettings.php|LocalSettings.php}}</tt>.<br />
<br />
To block an IP range from [[Special:Blockip]], enter the first IP address in the range followed by a forward slash and a [http://en.wikipedia.org/wiki/Classless_inter-domain_routing Classless inter-domain routing] (CIDR) suffix. '''You should avoid performing range blocks unless you understand what you are doing, or you may end up blocking tens of thousands of people who are not the problem!'''<br />
<br />
==Technical explanation==<br />
CIDR notation is written as the IP address, a slash, and the CIDR affix (for example, the IPv4 "<code>10.2.3.41/24</code>" or IPv6 "<code>a3:b:c1:d:e:f:1:21/24</code>"). The CIDR affix is the number of starting digits every IP address in the range have in common when written in binary. <br />
<br />
For example: "<code>10.10.1.32</code>" is binary "<code>00001010.00001010.00000001.00100000</code>", so <code>10.10.1.32/27</code> will match the first 27 digits ("<code><u>00001010</u>.<u>00001010</u>.<u>00000001</u>.<u>001</u>00000</code>"). The IP addresses <code>10.10.1.32</code>–<code>10.10.1.63</code>, when converted to binary, all have the same 27 first digits and will be blocked if <code>10.10.1.32/27</code> is blocked.<br />
<br />
As the CIDR affix increases, the block affects less IP addresses (see [[#Table|table of example ranges]]). CIDR affixes are not the same for IPv4 addresses as they are for IPv6 addresses.<br />
<br />
==Calculating the CIDR affix==<br />
You can use the [[#Table|table of sample ranges]] below to guess the range, use a computer script, or manually calculate the range.<br />
<br />
===Conversion to binary===<br />
The first step in manually calculating a range is to convert the first and last IP address to binary representation. (This assumes you're not using a computer script, which can probably calculate the range for you anyway.) An IP address is composed of four groups of eight ones and zeros. Each group represents a number from 0 to 255. To convert a number to binary, you can use a [http://www.ccci.com/tools/subcalc/binary.html reference table] or know the value of each binary digit:<br />
{| class="prettytable" style="text-align:center;"<br />
|-<br />
| 1<br />
| 1<br />
| 1<br />
| 1<br />
| 1<br />
| 1<br />
| 1<br />
| 1<br />
|-<br />
| 128<br />
| 64<br />
| 32<br />
| 16<br />
| 8<br />
| 4<br />
| 2<br />
| 1<br />
|}<br />
<br />
Proceeding from left to right, fill in '1' if the number is at least that value, and subtract that value (if it's not, fill in '0' and don't subtract). For example, to calculate 240:<br />
# 240 is at least 128, so place 1 and subtract 128.<br />
# 112 (240-128) is at least 64, so place 1 and subtract 64.<br />
# 48 (112-64) is at least 32, so place 1 and subtract 48.<br />
# 16 (48-32) is at least 16, so place 1 and subtract 16.<br />
# Since the remaining value is zero, all the remaining places are '0'.<br />
Thus, 240 is 1111 0000 because it can be represented as 128+64+32+16+0+0+0+0.<br />
<br />
===Calculate range===<br />
# Place both IP addresses one atop the other, and count how many starting digits are exactly alike. This is the CIDR affix.<br />
# Double-check! Being off by one digit could extend your block by thousands of addresses.<br />
<br />
The example below calculates the CIDR range between 69.208.0.0 and 69.208.0.255. Note that this is a simple example; some groups of IP addresses do not so neatly fit CIDR affixes, and need multiple different-sized blocks to block the exact range.<br />
IP addresses:<br />
69.208.0.0<br />
69.208.0.255<br />
&nbsp;<br />
Convert to binary:<br />
0100 0101.1101 0000.0000 0000.0000 0000<br />
0100 0101.1101 0000.0000 0000.1111 1111<br />
&nbsp;<br />
Count identical first numbers:<br />
'''0100 0101.1101 0000.0000 0000'''.0000 0000<br />
'''0100 0101.1101 0000.0000 0000'''.1111 1111<br />
|____________________________|<br />
24 digits<br />
&nbsp;<br />
CIDR range:<br />
69.208.0.0/24<br />
</pre><br />
<br />
===<span id="Table">Table of sample ranges</span>===<br />
The table below shows the IP blocks each CIDR suffix affects. Note that MediaWiki only supports blocking CIDR suffixes 16&ndash;32.<br />
<br />
{| class="prettytable"<br />
! CIDR<br />
! Start Range<br />
! End Range<br />
! Total addresses<br />
! Bits selected in IP address<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/0'''<br />
| 0.0.0.0<br />
| 255.255.255.255<br />
| 4,294,967,296<br />
| ********.********.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/1'''<br />
| 0.0.0.0<br />
| 127.255.255.255<br />
| 2,147,483,648<br />
| 0*******.********.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/4'''<br />
| 65.0.0.0<br />
| 79.255.255.255<br />
| 268,435,456<br />
| 0100****.********.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/8'''<br />
| 69.0.0.0<br />
| 69.255.255.255<br />
| 67,108,864<br />
| 01000101.********.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/11'''<br />
| 69.208.0.0<br />
| 69.238.255.255<br />
| 2,197,152<br />
| 01000101.110*****.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/12'''<br />
| 69.208.0.0<br />
| 69.223.255.255<br />
| 1,048,576<br />
| 01000101.1101****.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/13'''<br />
| 69.208.0.0<br />
| 69.215.255.255<br />
| 524,288<br />
| 01000101.11010***.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/14'''<br />
| 69.208.0.0<br />
| 69.211.255.255<br />
| 262,144<br />
| 01000101.110100**.********.********<br />
|- style="color:gray;"<br />
| 69.208.0.0'''/15'''<br />
| 69.208.0.0<br />
| 69.209.255.255<br />
| 131,072<br />
| 01000101.1101000*.********.********<br />
|-<br />
| 69.208.0.0'''/16'''<br />
| 69.208.0.0<br />
| 69.208.255.255<br />
| 65,536<br />
| 01000101.11010000.********.********<br />
|-<br />
| 69.208.0.0'''/17'''<br />
| 69.208.0.0<br />
| 69.208.127.255<br />
| 32,768<br />
| 01000101.11010000.0*******.********<br />
|-<br />
| 69.208.0.0'''/18'''<br />
| 69.208.0.0<br />
| 69.208.63.255<br />
| 16,384<br />
| 01000101.11010000.00******.********<br />
|-<br />
| 69.208.0.0'''/19'''<br />
| 69.208.0.0<br />
| 69.208.31.255<br />
| 8,192<br />
| 01000101.11010000.000*****.********<br />
|-<br />
| 69.208.0.0'''/20'''<br />
| 69.208.0.0<br />
| 69.208.15.255<br />
| 4,096<br />
| 01000101.11010000.0000****.********<br />
|-<br />
| 69.208.0.0'''/21'''<br />
| 69.208.0.0<br />
| 69.208.7.255<br />
| 2,048<br />
| 01000101.11010000.00000***.********<br />
|-<br />
| 69.208.0.0'''/22'''<br />
| 69.208.0.0<br />
| 69.208.3.255<br />
| 1,024<br />
| 01000101.11010000.000000**.********<br />
|-<br />
| 69.208.0.0'''/23'''<br />
| 69.208.0.0<br />
| 69.208.1.255<br />
| 512<br />
| 01000101.11010000.0000000*.********<br />
|-<br />
| 69.208.0.0'''/24'''<br />
| 69.208.0.0<br />
| 69.208.0.255<br />
| 256<br />
| 01000101.11010000.00000000.********<br />
|-<br />
| 69.208.0.0'''/25'''<br />
| 69.208.0.0<br />
| 69.208.0.127<br />
| 128<br />
| 01000101.11010000.00000000.0*******<br />
|-<br />
| 69.208.0.0'''/26'''<br />
| 69.208.0.0<br />
| 69.208.0.63<br />
| 64<br />
| 01000101.11010000.00000000.00******<br />
|-<br />
| 69.208.0.0'''/27'''<br />
| 69.208.0.0<br />
| 69.208.0.31<br />
| 32<br />
| 01000101.11010000.00000000.000*****<br />
|-<br />
| 69.208.0.0'''/28'''<br />
| 69.208.0.0<br />
| 69.208.0.15<br />
| 16<br />
| 01000101.11010000.00000000.0000****<br />
|-<br />
| 69.208.0.0'''/29'''<br />
| 69.208.0.0<br />
| 69.208.0.7<br />
| 8<br />
| 01000101.11010000.00000000.00000***<br />
|-<br />
| 69.208.0.0'''/30'''<br />
| 69.208.0.0<br />
| 69.208.0.3<br />
| 4<br />
| 01000101.11010000.00000000.000000**<br />
|-<br />
| 69.208.0.0'''/31'''<br />
| 69.208.0.0<br />
| 69.208.0.1<br />
| 2<br />
| 01000101.11010000.00000000.0000000*<br />
|-<br />
| 69.208.0.0'''/32'''<br />
| 69.208.0.0<br />
| 69.208.0.0<br />
| 1<br />
| 01000101.11010000.00000000.00000000<br />
|}<br />
<br />
==References==<br />
* {{wikipedia|Classless Inter-Domain Routing}}<br />
* [http://www.ccci.com/tools/subcalc/binary.html Converting IP addresses to binary]<br />
<br />
==External links==<br />
* [http://apps.csc.fi/laskin2.html Netmask calculator] which helps in making the correct decision for range blocks.<br />
* [http://tools.wikimedia.de/~chm/blockcalc.php Rangeblock-Calculator] gives you the range you should use when blocking.<br />
<br />
{{Languages|Help:Range blocks}}<br />
<br />
[[Category:Help|Range blocks]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Help:Namespaces&diff=11897Help:Namespaces2010-11-15T15:14:56Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Osai</p>
<hr />
<div>{{PD Help Page}}<br />
Pages without a ':' in their name are in the main namespace. This namespace is for content pages; documents that aren't directly related to this may go in other namespaces. When pages are in another namespace, they are specified as ''namespace'':''page''; i.e. this page is ''{{NAMESPACE}}'':''{{PAGENAME}}''.<br />
<br />
;Help: Documentation about working with the wiki software. This could be mirrored from outside sites, or locally written.<br />
;Image: For descriptions of uploaded files or media files. You shouldn't create these directly; they are created when you click the [[special:upload|Upload file]] link in the toolbox.<br />
;Media: Use this namespace to link to uploaded files directly, rather than through the description pages.<br />
;MediaWiki: Use this namespace to change the default system messages, [http://meta.wikimedia.org/wiki/Help:System_message See Help:System message on meta].<br />
;Project: Information about this wiki; i.e. policies that apply here. This namespace also has an alias, which is the name of the wiki installation.<br />
;Talk: Each page has a corresponding ''discussion'' page. This can be used for feedback/comments about that page, or other local notes that another group may want to associate with the page, without modifying the document directly, or for any other additional information to associate with the document.<br />
;Template: This is used for meta-information that is to be transcluded into multiple documents, such as tags to mark the status of a document.<br />
;User: For personal notes. Each User has a corresponding user page for their own information. Users can also create subpages, by using a / after their name.<br />
;User_talk: The discussion page on a user's page can be used for leaving messages. If this page is edited, the next time that user logs in they will see a box notifying them that they have new messages<br />
<br />
==External links==<br />
<br />
{{meta|Help:Namespace}}<br />
<br />
{{Languages}}<br />
[[Category:Help|Namespaces]]<br />
[[Category:Namespace]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Help:Interwiki_linking&diff=11896Help:Interwiki linking2010-11-15T15:14:50Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Osai</p>
<hr />
<div>{{PD Help Page}}<br />
'''Interwiki links''' are links to pages of other projects, using a prefixed internal link style.<br />
<br />
Interwiki links make it possible, to link to pages of (e.g.) Wikipedia, Wikibooks, Wikinews etc. or to your wiki-project in different languages (see [[Manual:Wiki family]]). <br />
<br />
A link like <code><nowiki>[[Wikipedia:Main Page]]</nowiki></code> will appear like this: [[Wikipedia:Main Page]] and redirect you to Wikipedia's Main Page. <br />
<br />
==Interwiki links to other projects==<br />
===Default===<br />
Several Wikimedia-Projects (and others) are ready for interwiki linking by default, so you can use them without editing your database. Note that wikipedia was only added as one of the interwiki defaults since v1.10<br />
<br />
The following are some examples of interwiki prefixes which are available by default:<br />
{| {{prettytable}}<br />
|{{Hl3}} align="center"|'''prefix'''<br />
|{{Hl3}} align="center"|'''destination URL'''<br />
|{{Hl3}} align="center"|'''usage example'''<br />
|-<br />
|commons<br />
|<nowiki>http://commons.wikimedia.org/wiki/</nowiki><br />
|<code><nowiki>[[commons:MediaWiki]]</nowiki></code><br />
|-<br />
|mediazilla<br />
|<nowiki>http://bugzilla.wikimedia.org/</nowiki><br />
|<code><nowiki>[[mediazilla:1209]]</nowiki></code><br />
|-<br />
|meta<br />
|<nowiki>http://meta.wikimedia.org/wiki/</nowiki><br />
|<code><nowiki>[[meta:Main Page]]</nowiki></code><br />
|-<br />
|mw<br />
|<nowiki>http://www.mediawiki.org/wiki/</nowiki><br />
|<code><nowiki>[[mw:Help:Contents]]</nowiki></code><br />
|-<br />
|wikibooks<br />
|<nowiki>http://en.wikibooks.org/wiki/</nowiki><br />
|<code><nowiki>[[wikibooks:Main Page]]</nowiki></code><br />
|-<br />
|wikimedia<br />
|<nowiki>http://wikimediafoundation.org/wiki/</nowiki><br />
|<code><nowiki>[[wikimedia:Main Page]]</nowiki></code><br />
|-<br />
|wikinews<br />
|<nowiki>http://en.wikinews.org/wiki/</nowiki><br />
|<code><nowiki>[[wikinews:Main Page]]</nowiki></code><br />
|-<br />
|wikiquote<br />
|<nowiki>http://en.wikiquote.org/wiki/</nowiki><br />
|<code><nowiki>[[wikiquote:Main Page]]</nowiki></code><br />
|-<br />
|wikisource<br />
|<nowiki>http://en.wikisource.org/wiki/</nowiki><br />
|<code><nowiki>[[wikisource:Main Page]]</nowiki></code><br />
|-<br />
|wikispecies<br />
|<nowiki>http://species.wikimedia.org/wiki/</nowiki><br />
|<code><nowiki>[[wikispecies:Main Page]]</nowiki></code><br />
|-<br />
|wiktionary<br />
|<nowiki>http://en.wiktionary.org/wiki/</nowiki><br />
|<code> <nowiki>[[wiktionary:Main Page]]</nowiki></code><br />
|-<br />
|}<br />
<br />
Note: In some installations none of these is pre-installed. Try <code><nowiki>[[metawikipedia:Main Page]]</nowiki></code> in this case.<br />
<br />
===Adding a new website for interwiki linking===<br />
For setting up interwiki links, you might need to edit the database. Alternatively you might prefer to install an [[:Category:Interwiki extensions|Interwiki extension]].<br />
<br />
(note: advanced mySQL users may prefer to use just a single command line:<nowiki> INSERT INTO interwiki SET iw_prefix='(the wiki name)', iw_url='http://(the adequate URL)/$1', iw_local=1, iw_trans=0 ;</nowiki> - instead of exporting and re-importing the whole table interwiki content... )<br />
<br />
(Advanced users of PostgreSQL use <code>INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('w', 'http://en.wikipedia.org/wiki/$1', 1, 0);</code>)<br />
* Export the database table 'interwiki' then add to the end of the table the following kayakwiki example...<br /><br />
* <nowiki>('kayakwiki', 'http://en.kayakwiki.org/index.php/$1', 1, 0);</nowiki><br /><br />
* Note: in the above code, the semicolon ';' as seen, MUST be at the end of the table. At the end of any other line within that table Only has ','.<br /><br />
* Import the database table 'interwiki'<br /><br />
* To test it: Go to your site, create an article, with the following content.<br /><br />
* <nowiki>[[kayakwiki:Places|]]</nowiki> will display a link to the 'Places' page on KayakWiki.org (the url <nowiki>http://en.kayakwiki.org/index.php/Places</nowiki>)<br />
<br />
As the Wikipedia isn't set up by default in version 1.9 and before, you might want to add it (and other projects of your need).<br />
<br />
The fields of the <code>interwiki</code> database table are as follows:<br />
*'''<code>iw_prefix</code>''': choose a prefix, which is used for interwiki linking, e.g. "wikipedia" for linking to Wikipedia<br />
*'''<code>iw_url</code>''': enter the project's URL, e.g. <code><nowiki>http://en.wikipedia.org/wiki/$1</nowiki></code> for Wikipedia. Don't forget the <code>$1</code> as it is replaced with the article's name you are linking to (<code><nowiki>[[Wikipedia:Main Page]]</nowiki></code> links to <code><nowiki>http://en.wikipedia.org/wiki/</nowiki>'''Main_Page'''</code>).<br />
Note: If iw_url is a binary BLOB field (SVN version, but also occurs in version 1.11.0, bug?) this won't work directly. You have to enter it as binary. There are two possible solutions: 1. You save the url in a plain text file, then import it through phpmyadmin. 2. You can directly enter an SQL query. <br />
<br />
*'''<code>iw_local</code>''': if 1, your wiki will redirect even external links of the form iw_prefix:title, not only those from its own pages. you need this if you want to use the redirect functionality from outside your wiki or other wikis use your transwiki functions for nested transwiki links (like http://en.wikipedia.org/wiki/fr:Accueil)<br />
*'''<code>iw_trans</code>''': "transwiki transclusion" - set to 1 if you want to use pages from the other wiki as templates. You will also need to set [[Manual:$wgEnableScaryTranscluding|$wgEnableScaryTranscluding = true]] in your ''LocalSettings.php''<br />
<br />
{{admin tip|tip=<br />
Several help pages link to MediaWiki.org's ''Manual'' namespace. To make these links work on your local wiki, add an interwiki link with ''iw_prefix=manual'' and ''iw_url=<nowiki>http:</nowiki>//www.mediawiki.org/wiki/Manual:$1''<br />
}}<br />
<br />
==Interwiki links to other languages==<br />
[[Image:M-en-interwiki lang.png|thumb|Interwiki links to other languages]]<br />
If you have installed a [[Manual:Wiki family|Wiki family]], you can link from an article in English to an article in German (if you have a German project, too). You can set up MediaWiki, to show those links in the sidebar, just below the toolbox.<br />
<br />
In your filesystem, there is a subfolder of your MediaWiki installation, called "languages". Go there and have a look at "<code>Names.php</code>" as it contains a list of known languages and their prefixes. E.g. you want to add your German project, search "<code>Names.php</code>" for "Deutsch" and note the prefix "de".<br />
<br />
If you know the "right" prefix, edit your database by adding a new line to table <code>interwiki</code>:<br />
*'''<code>iw_prefix</code>''': language-prefix (e.g. "de" for German), which is listed in "<code>Names.php</code>"<br />
*'''<code>iw_url</code>''': URL to your wiki-project (e.g. <code><nowiki>http://de.your-wiki.org/index.php/$1</nowiki></code>)<br />
*'''<code>iw_local</code>''': ''same as above "Adding More"''<br />
*'''<code>iw_trans</code>''': ''same as above "Adding More"''<br />
<br />
<br />
Now, you can link an article to the same in other languages. Adding <code><nowiki>[[de:Hauptseite]]</nowiki></code> on your english Main_Page will create a link "Deutsch" below the toolbox, which leads to the Main_Page of the German wiki (Hauptseite).<br />
<br />
Note, that this link is shown in Sidebar's section, '''only''', and not inside of the article. If you want to create a link inside of the text, you have to add a colon previous to the prefix: <code><nowiki>[[:de:Hauptseite]]</nowiki></code>.<br />
<br />
==See also==<br />
* [[Extension:SpecialInterwiki]]<br />
<br />
==External links==<br />
{{meta|Help:Interwiki linking}}<br />
<br />
{{Languages|Help:Interwiki linking}}<br />
<br />
[[Category:Help|Interwiki linking]]<br />
[[Category:Interwiki]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Sideline&diff=11895Sideline2010-11-15T15:14:46Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by KenjiE20</p>
<hr />
<div>{{expand}}<br />
Sidelines, as the name suggests, are lines to the side of something else. In this case, they are the rail link between industries and the [[Guides:Glossary:Mainline|mainline]] via special [[Guides:Glossary:Sideline Hub|Sideline Hubs]]. They are in the form of LR and usually service 1-5 industries before another sideline further down the [[Guides:Glossary:Mainline|mainline]] takes over.<br />
<br />
[[Category:Guides]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Yield_Line&diff=11894Yield Line2010-11-15T15:14:40Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Scobos</p>
<hr />
<div>''by [[User:scobos|scobos]]<br />
<br />
== Overview ==<br />
Yield Lines are temporary extra tracks than run parallel to a ML or SL. The idea is force slow(er) trains to move to the side and allow fast(er) trains to pass.<br />
<br />
<br />
== Development ==<br />
Any help is welcome on the idea or the write-up. There is a sample save game of both Fail Safe and non-Fail Safe varieties: [[File:Yield_FS.sav]] or [[File:Yield non-FS.sav]]<br />
<br />
== The Concept ==<br />
<br />
[[Image:YieldLineConcept.png|thumb|right|200px|Yield Line Concept]]<br />
Often a ML or SL can become slightly jammed by the presence of slower trains. This can happen when trains are out of date and haven't replaced yet, or simply when they are carrying full loads back to a drop on the same line as empty trains. Ideally, we would be able to separate trains to different tracks based on speed. Since currently this is not possible, a theoretical work-around is to separate trains based on Gap Distance.<br />
<br />
As a slower train continue down a ML or SL, traffic builds up behind them, but a Gap opens in front of them (as faster trains move ahead). Therefore, we can assume that if there is a large Gap in front of a train, and no Gap behind it, it is probably a slow train. Now the only question is how to sort it.<br />
<br />
<br />
== The Logic ==<br />
[[Image:YieldLineLogic.png|thumb|right|200px|Yield Line Logic]]<br />
Q is the Entry Combo Signal that determines whether a train can continue on the ML or must go to the Yield Line (YL). Note the penalty on the YL.<br />
<br />
Using Osai's definition of 0 for Green and 1 for Red:<br />
{| align="center" border="1" cellspacing="20"<br />
! !! 1 !! 0<br />
|-<br />
! Q || Will Yield || Will Not Yield<br />
|-<br />
! X || Train Following || No Train Following<br />
|-<br />
! B || Train on ML Ahead || No Train on ML Ahead<br />
|-<br />
! C || Train on YL || No Train on YL<br />
|}<br />
<br />
<br />
'''Why These Inputs Matter'''<br />
<br />
X: If there is a train behind us, we might be slow and should consider yielding.<br />
If there is no train behind us, we probably aren't slow and can continue.<br />
<br />
B: If there is a train right in front of us (who didn't yield), we probably aren't slow.<br />
If there is no train right in front of us, we might be slow and should consider yielding.<br />
<br />
C: If there is a train on the YL, he might be slow and we should try to pass! (Continue on ML)<br />
If there is no train on the YL... well, this by itself doesn't really tell us much!<br />
Also note that if we don't check for trains on the YL, as soon as the first train Yields, the ML becomes clear... which could result in every train taking the YL.<br />
<br />
So the logic, first in words, then formula, is that we want:<br />
(Train Will Yield) if (Train is Behind) and (No Train on ML) and (No Train on YL)<br />
Q = X NAND B NAND C<br />
<br />
which is the same as saying:<br />
(Train Will Yield) if (Train is Behind) and [No Train on ML or YL]<br />
Q = X AND (B NOR C)<br />
<br />
Truth Table:<br />
A = (No Train on ML or YL) = B NOR C<br />
{| align="center" border="1" cellspacing="20"<br />
! X !! A !! Q<br />
|-<br />
| 0 || 0 || 0<br />
|-<br />
| 0 || 1 || 0<br />
|-<br />
| 1 || 0 || 0<br />
|-<br />
| 1 || 1 || 1<br />
|}<br />
<br />
<br />
== The Construct ==<br />
[[Image:YieldLineConstruct.png|thumb|right|200px|Yield Line in Action]]<br />
Using the Logic Train newGRF and Osai's NOT and OR Gates, I was able to construct a sample Yield Line. <br />
<br />
X should be placed more then 1 TL and less than 2 TL from Q. B and C can test as far down as you'd like (I used 2 TL). Don't forget a Penalty on the YL.<br />
<br />
Currently, there are two main flaws, and two areas I haven't started work on. First flaw: the lead train in a group of all fast trains will yield to the other fast trains, and if using a simple prio to rejoin, will get passed by every train in the line. Unfortunately, this is a core design flaw. Second flaw: like most logic gates, this needs a Fail Safe, but it is fairly in-elegant to place it so close to "X," as I was forced to do to get the prototype working. Someone with a better idea for a FS (or a better way to check for X) might fix this. The area I haven't worked on yet is the re-join down the line. In the save-game, I put in a simple prio, but this is in-elegant. There should be a precise gap in the prio to allow for the situation (Flaw 1) of a fast train needing the re-join the head of the line and not yield priority. Second new area - it should be possible to queue slow trains in the Yield Line by using a more elegant check for C and having a better re-entry system. Even further, you could use this as a sorter to segregate fast and slow trains on different lines, if a method was developed to allow the fast trains in Flaw 1 back onto the correct track.<br />
<br />
'''Pros:'''<br />
<br />
Catches slow trains that are jamming the ML<br />
<br />
Allows overtaking<br />
<br />
'''Cons:'''<br />
<br />
Low/Medium Traffic: Lead trains always yield<br />
<br />
== Progress on Yield Line==<br />
{{R&D_header|R&D Overview}}<br />
{{R&D_content|Yield Line|[[User:scobos|scobos]]|wip|Currently Editing|unclaimed||unclaimed|| | }}<br />
{{R&D_footer}}<br />
[[Category:Research]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Help:Moving_a_page&diff=11893Help:Moving a page2010-11-15T15:14:35Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Osai</p>
<hr />
<div>{{PD Help Page}}<br />
<br />
'''Moving (renaming) a page''' means giving it another name. This is done by using "{{int:move}}" tab at the top. Then simply enter the new name and click 'Move Page'. Normally you would want to leave "Move associated talk page" option ticked. <br />
<br />
If you move page "A" to a new title "B", this operation will do the following:<br />
* Creates the new page "B", with contents from page "A"<br />
* Replaces the contents of page "A" with redirect to "B"<br />
* Moves all the editing history from page "A" so that it appears under "B"'s history tab.<br />
<!--I think the above describes just the opposite to what actually happens in the database, I'm going to replace it with correct description: page is not actually moved in [[Page table]], it's simply given a new title--><br />
<br />
The third point is important. By using the 'Move' feature, you also '''move the editing history''', which is desireable in most situations. The editing history allows people to see how the contents of the page were built up, and who contributed what. If you move contents around by copying and pasting (not using the move feature), you do not achieve this.<br />
<br />
Because the move operation '''leaves behind a redirect''', it should not result in any broken links, however you might want to hunt down the pages which link in to the redirect, and change their text to link directly to the new title. The 'What links here' toolbox feature (bottom left) is useful when doing this.<br />
<br />
== Proposing a move ==<br />
Deciding on a page title can be a difficult aspect of wiki organization, and one which can often provoke debates. If the move you have in mind is one which might cause upset or could be considered controversial, you should propose the move first. Do this by leaving a note to give your reasons on the [[Help:Talk pages|talk page]]. You might also establish a system for labelling the page itself, with a move proposal template, to make everybody aware of your intentions.<br />
<br />
== Undo a move ==<br />
As with all wiki editing, a move operation can be reversed (by any user). To reverse a move operation, simply move the page back, e.g. move page "B" back to "A".<br />
<br />
The page title "B" will still be left behind, as a redirect from "B" to "A". Any user can remove the redirect and propose that the page be deleted. However the final deletion will require sysop priviledges (see [[Help:Deleting a page]]).<br />
<br />
==External links==<br />
{{meta|Help:Moving a page}}<br />
<br />
{{Languages|Help:Moving a page}}<br />
<br />
[[Category:Help|Moving a page]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Template:Languages&diff=11892Template:Languages2010-11-15T15:14:24Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Osai</p>
<hr />
<div>== Template ==<br />
<br />
<onlyinclude><div class="LanguageLinks"><br />
<table width="100%"><br />
<tr valign="top" style="background: #EEF3E2"><br />
<td style="width: 25px; padding-left: 0.5em;">[[Image:Geographylogo.png|25px|Languages]]</td><br />
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #aaaaaa;">'''[[Project:Language policy|Languages]]:'''&nbsp;</td><td style="padding: 1px 1em 0; background: #F6F9ED;"><br />
'''[[{{{1|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}|English]]'''<br />
{{Languages/Lang|af|{{{1|}}}}}<br />
{{Languages/Lang|ar|{{{1|}}}}}<br />
{{Languages/Lang|br|{{{1|}}}}}<br />
{{Languages/Lang|ca|{{{1|}}}}}<br />
{{Languages/Lang|cs|{{{1|}}}}}<br />
{{Languages/Lang|de|{{{1|}}}}}<br />
{{Languages/Lang|el|{{{1|}}}}}<br />
{{Languages/Lang|es|{{{1|}}}}}<br />
{{Languages/Lang|fa|{{{1|}}}}}<br />
{{Languages/Lang|fi|{{{1|}}}}}<br />
{{Languages/Lang|fr|{{{1|}}}}}<br />
{{Languages/Lang|gu|{{{1|}}}}}<br />
{{Languages/Lang|he|{{{1|}}}}}<br />
{{Languages/Lang|hu|{{{1|}}}}}<br />
{{Languages/Lang|id|{{{1|}}}}}<br />
{{Languages/Lang|it|{{{1|}}}}}<br />
{{Languages/Lang|ja|{{{1|}}}}}<br />
{{Languages/Lang|ko|{{{1|}}}}}<br />
{{Languages/Lang|mr|{{{1|}}}}}<br />
{{Languages/Lang|ms|{{{1|}}}}}<br />
{{Languages/Lang|nl|{{{1|}}}}}<br />
{{Languages/Lang|no|{{{1|}}}}}<br />
{{Languages/Lang|oc|{{{1|}}}}}<br />
{{Languages/Lang|pl|{{{1|}}}}}<br />
{{Languages/Lang|pt|{{{1|}}}}}<br />
{{Languages/Lang|ro|{{{1|}}}}}<br />
{{Languages/Lang|ru|{{{1|}}}}}<br />
{{Languages/Lang|si|{{{1|}}}}}<br />
{{Languages/Lang|sq|{{{1|}}}}}<br />
{{Languages/Lang|sr|{{{1|}}}}}<br />
{{Languages/Lang|sv|{{{1|}}}}}<br />
{{Languages/Lang|th|{{{1|}}}}}<br />
{{Languages/Lang|tr|{{{1|}}}}}<br />
{{Languages/Lang|vi|{{{1|}}}}}<br />
{{Languages/Lang|yue|{{{1|}}}}}<br />
{{Languages/Lang|zh|{{{1|}}}}}<br />
{{Languages/Lang|zh-hans|{{{1|}}}}}<br />
{{Languages/Lang|zh-hant|{{{1|}}}}}<br />
</td></tr></table></div></onlyinclude><br />
<br />
== Syntax ==<br />
<nowiki>{{Languages|PageName}}</nowiki><br />
<br />
* '''PageName''' (optional) - the name of the page to display language links for. If omitted then the English version of the current page is used. This parameter can normally be omitted, as it is only required if you want to link to a page other than the one you place the template on, which is very uncommon. If this parameter is used on a sub-page make sure you supply the root name, not the full page name (e.g. on [[MediaWiki/fr]] you would need to use <code><nowiki>{{Languages|MediaWiki}}</nowiki></code> and not <code><nowiki>{{Languages|MediaWiki/fr}}</nowiki></code>).<br />
<br />
== Usage ==<br />
<br />
The template should only be placed on pages that exist in more than one language, and it should be placed in the same location on each translation of the page.<br />
<br />
The English version of a page is always the main version, with all other languages as sub-pages, named using the appropriate language code (see below). <br />
<br />
For example, on the Main Page you would include the text <code><nowiki>{{Languages}}</nowiki></code>, both on [[Main Page]] itself, and on each of its language sub-pages. The template automatically creates links to any language sub-pages that exist, e.g. <tt>Main Page/ja<tt>, <tt>Main Page/fr</tt>, and ignores non-existant languages.<br />
<br />
See [[Project:Language policy]] for further details about translating pages.<br />
<br />
== Supported languages ==<br />
This shows you the name of each language's sub-page (using ''Main Page'' as an example). Other languages may be added easily as necessary. Please use the appropriate [[meta:List of Wikipedias|prefix, as used on Wikipedia]] when adding a new language. Please do ''not'' add languages for which no pages exist yet, as this will increase the time needed to include the template without adding any benefit (languages are only displayed to the user when the relevant page exists).<br />
<br />
The link on the language names goes to the Wikipedia in that language. '''If no Wikipedia in your language exists, do not add pages in that language to MediaWiki.org!''' This wiki is not the place for language advocacy - please go through the correct channels, and once your language has a Wikipedia then please return to add content here.<br />
<br />
{| border="1" cellpadding="5"<br />
! Page Name || Language <br />
|-<br />
| Main Page || [[:en:|English]]<br />
|-<br />
| Main Page'''/af''' || [[:af:|Afrikaans]]<br />
|-<br />
| Main Page'''/ar''' || [[:ar:|Arabic]]<br />
|-<br />
| Main Page'''/br''' || [[:br:|Breton]]<br />
|-<br />
| Main Page'''/ca''' || [[:ca:|Catalan]]<br />
|-<br />
| Main Page'''/cs''' || [[:cs:|Czech]]<br />
|-<br />
| Main Page'''/de''' || [[:de:|German]]<br />
|-<br />
| Main Page'''/el''' || [[:el:|Greek]]<br />
|-<br />
| Main Page'''/es''' || [[:es:|Spanish]]<br />
|-<br />
| Main Page'''/fa''' || [[:fa:|Persian]]<br />
|-<br />
| Main Page'''/fi''' || [[:fi:|Finnish]]<br />
|-<br />
| Main Page'''/fr''' || [[:fr:|French]]<br />
|-<br />
| Main Page'''/gu''' || [[:gu:|Gujarati]]<br />
|-<br />
| Main Page'''/he''' || [[:he:|Hebrew]]<br />
|-<br />
| Main Page'''/hu''' || [[:hu:|Hungarian]]<br />
|-<br />
| Main Page'''/id''' || [[:id:|Indonesian]]<br />
|-<br />
| Main Page'''/it''' || [[:it:|Italian]]<br />
|-<br />
| Main Page'''/ja''' || [[:ja:|Japanese]]<br />
|-<br />
| Main Page'''/ko''' || [[:ko:|Korean]]<br />
|-<br />
| Main Page'''/mr''' || [[:mr:|Marathi]]<br />
|-<br />
| Main Page'''/ms''' || [[:ms:|Malay]]<br />
|-<br />
| Main Page'''/nl''' || [[:nl:|Nederlands]]<br />
|-<br />
| Main Page'''/no''' || [[:no:|Norwegian]]<br />
|-<br />
| Main Page'''/oc''' || [[:oc:|Occitan]]<br />
|-<br />
| Main Page'''/pl''' || [[:pl:|Polish]]<br />
|-<br />
| Main Page'''/pt''' || [[:pt:|Portugese]]<br />
|-<br />
| Main Page'''/ro''' || [[:ro:|Romanian]]<br />
|-<br />
| Main Page'''/ru''' || [[:ru:|Russian]]<br />
|-<br />
| Main Page'''/si''' || [[:si:|Sinhalese]]<br />
|-<br />
| Main Page'''/sq''' || [[:sq:|Albanian]]<br />
|-<br />
| Main Page'''/sr''' || [[:sr:|Serbian]]<br />
|-<br />
| Main Page'''/sv''' || [[:sv:|Swedish]]<br />
|-<br />
| Main Page'''/th''' || [[:th:|Thai]]<br />
|-<br />
| Main Page'''/tr''' || [[:tr:|Turkish]]<br />
|-<br />
| Main Page'''/vi''' || [[:vi:|Vietnamese]]<br />
|-<br />
| Main Page'''/yue''' || [[:zh-yue:|Cantonese]]<br />
|-<br />
| Main Page'''/zh''' || [[:zh:|Chinese]]<br />
|-<br />
| Main Page'''/zh-hans''' || Chinese (Simplified)<br />
|-<br />
| Main Page'''/zh-hant''' || Chinese (Traditional)<br />
|}<br />
<br />
== Example ==<br />
Here is how the language bar looks on the [[MediaWiki]] page:<br />
{{Languages|MediaWiki}}<br />
[[Category:Language templates]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Srnw&diff=11891Srnw2010-11-15T15:14:18Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Mark</p>
<hr />
<div>==Introduction==<br />
<br />
SRNW stands for selfregulating network. The idea behind this building style is to have an intelligent network that sends trains to where they are needed most, instead of ordering trains trains to go to every individual station to pick up waiting cargo.<br />
<br />
In a typical SRNW trains have only one order: a drop order at a main station.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Help:Formatting&diff=11890Help:Formatting2010-11-15T15:14:04Z<p>Thraxian: Reverted edits by Ojatonakyq (Talk) to last revision by Osai</p>
<hr />
<div>{{PD Help Page}}<br />
You can format your text using wiki markup. This consists of normal characters like asterisks, single quotes or equation marks which have a special function in the wiki, sometimes depending on their position. For example, to format a word in ''italic'', you include it in two single quotes like <tt><nowiki>''this''</nowiki></tt><br />
<br />
== Text formatting markup ==<br />
<br />
{| align="center" {{Prettytable}}<br />
|-<br />
|{{Hl2}} |'''Description'''<br />
|{{Hl2}} |'''You type''' <br />
|{{Hl2}} |'''You get'''<br />
|-<br />
| colspan="3" align="center" | ''applies anywhere''<br />
|-<br />
|Italic text<br />
|<tt><nowiki>''italic''</nowiki></tt><br />
|''italic''<br />
|-<br />
| Bold text<br />
|<tt><nowiki>'''bold'''</nowiki></tt><br />
|'''bold'''<br />
|-<br />
| Bold and italic<br />
|<tt><nowiki>'''''bold & italic'''''</nowiki></tt><br />
|'''''bold & italic'''''<br />
|-<br />
|Escape wiki markup<br />
|<tt><nowiki><nowiki>no ''markup''</nowiki></nowiki></tt><br />
|<nowiki>no ''markup''</nowiki><br />
|-<br />
| colspan="3" align="center" | ''only at the beginning of the line''<br />
|-<br />
| Indent text<br />
|<tt><nowiki>:Indent text</nowiki></tt><br />
|&nbsp;&nbsp;&nbsp;&nbsp;Indent text<br />
|-<br />
|Headings of<br /><br />
different levels <ref>Use of a heading created by single equal signs is discouraged as it appears with the same formatting and size as the page title, which can be confusing.</ref><ref>An article with four or more headings will automatically create a [http://en.wikipedia.org/wiki/Wikipedia:Section#Table_of_contents_.28TOC.29 table of contents].</ref><br />
|<br />
<tt><nowiki>==level 1==</nowiki></tt><br /><br />
<tt><nowiki>===level 2===</nowiki></tt><br /><br />
<tt><nowiki>====level 3====</nowiki></tt><br /><br />
<tt><nowiki>=====level 4=====</nowiki></tt><br />
|<br />
<br />
==Level 1==<br />
===Level 2===<br />
====Level 3====<br />
=====Level 4=====<br />
|-<br />
|Horizontal rule<br />
|<br />
<tt><nowiki>----</nowiki></tt><br />
|<br />
----<br />
|-<br />
|Bullet list<br />
|<br />
&#42; one<br><br />
&#42; two<br><br />
&#42; three<br><br />
&#42;&#42; three and one-third<br><br />
&#42;&#42; three and two-thirds<br><br />
|<br />
* one<br />
* two<br />
* three<br />
** three and one-third<br />
** three and two-thirds<br />
|-<br />
|Numbered list<br />
|<br />
&#35; one<br /><br />
&#35; two<nowiki><br></nowiki>spanning several lines<nowiki><br></nowiki>without breaking the numbering<br /><br />
&#35; three<br /><br />
&#35;&#35; three point one<br /><br />
&#35;&#35; three point two<br /><br />
|<br />
# one<br />
# two<br>spanning several lines<br>without breaking the numbering<br />
# three<br />
## three point one<br />
## three point two<br />
|-<br />
| Mixture of bulleted<br /> and numbered lists<br />
|<br />
&#35; one<br /><br />
&#35; two<br /><br />
&#35;&#42; two point one<br /><br />
&#35;&#42; two point two<br /><br />
|<br />
# one<br />
# two<br />
#* two point one<br />
#* two point two<br />
|-<br />
|Definition list<br />
|<br />
&#59;Definition<br /><br />
&#58;item 1<br /><br />
&#58;item 2<br /><br />
|<br />
;Definition<br />
:item 1<br />
:item 2<br />
|-<br />
|Preformatted text<br />
|<br />
&nbsp;&nbsp;preformatted text is done with<br /><br />
&nbsp;&nbsp;a space at the<br /><br />
&nbsp;&nbsp;beginning of the line<br /><br />
|<br />
preformatted text is done with<br />
a space at the <br />
beginning of the line<br />
|}<br />
<br />
Notes: <references/><br />
<br />
== Paragraphs ==<br />
<br />
MediaWiki ignores normal line breaks. To start a new paragraph, leave an empty line. You can also start a new line with the HTML tags <tt><nowiki><br> or <br/></nowiki></tt>.<br />
<br />
== HTML ==<br />
<br />
Some [[w:HTML|HTML]] tags are allowed in MediaWiki, for example <tt><nowiki><code></nowiki></tt>, <tt><nowiki><div></nowiki></tt>, <tt><nowiki><span></nowiki></tt> and <tt><nowiki><font></nowiki></tt>.<br />
<br />
{{Admin tip|tip=If you trust your users you can allow full HTML by setting <code>[[Manual:$wgRawHtml|$wgRawHtml]] = true;</code> in [[Manual:LocalSettings.php|LocalSettings.php]].}}<br />
<br />
<br />
== Other formatting ==<br />
Beyond the text formatting markup shown above, here are some other formatting references:<br />
*[[Help:Links|Links]]<br />
*[[Help:Images|Images]]<br />
*[[Help:Tables|Tables]]<br />
[http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_Page_Help/Do-It-Yourself/Formatting_Text#Underlining More Formatting from Wikipedia]<br />
<br />
== External Links ==<br />
{{meta|Help:Editing}}<br />
<br />
{{Languages|Help:Formatting}}<br />
<br />
[[Category:Help|Formatting]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Signal_gap&diff=11265Signal gap2010-02-16T14:57:27Z<p>Thraxian: Added screenshots, removed Reqscreenshot tag</p>
<hr />
<div>== Definition ==<br />
[[Image:Signal gap settings.png | thumb | 400px | right | Configuring auto-signalling]]<br />
A signal gap, or gap for short, is the amount of unsignalled space in a single signal block. Understanding signal gaps is important for maximizing train density on a rail line and ensuring that trains continue to move at the maximum allowable speed. In coop games, we adhere to a maximum signal gap of 1 tile.<br />
<br />
In general, use of the term "gap" indicates that a signal gap of length greater than 1 has been detected, and as a result, the efficiency of the network is at risk. Steps should be taken to fix any gaps marked in this manner.<br />
<br />
Do not confuse a "signal gap" with a "train gap". A train gap is the minimum space between two trains. Because our signals are 2 spaced tiles apart (also known as [http://wiki.openttd.org/Railway_Designs Signal Density]), there is a minimum gap of 3 (the Signal Density +1). <br />
<br />
<br clear=all><br />
== Why is understanding gaps important? ==<br />
<br />
A rail line is only as fast as its weakest link. If there is any point on the line where traffic must slow down or stop, the disruption will have a domino effect on any following trains, resulting in an inefficient network. As the goal is often to build a highly-efficient, and highly-dense network, these types of disruptions must be avoided at all costs!<br />
<br />
<br clear=all><br />
== What if I need to create a signal gap larger than 1? ==<br />
[[Image:Signal gap sync.png | thumb | 400px | right | Make sure alternate routes are in sync]]<br />
To create a signal gap larger than 1, you must provide following trains an alternate route until the gap is restored to 1. Larger gaps are created at station platforms, bridges, and tunnels, since none of these items can be signalled.<br />
<br />
To create an alternate route, simply make a new line parallel to the first line. This line should continue until the signal gap can be restored to 1, making sure to keep the trains [[Line sync|synchronize]]d.<br />
<br />
<br clear=all><br />
== How to count the length of a gap ==<br />
When using normal block signals, a gap's length is defined as the number of unsignalled spaces between two signals. Normal coop [[mainline]]s use a signal gap of 1, meaning there is only 1 unsignalled tiles between two signalled tiles.<br />
<br />
When using pre-signals, the gap is counted from the tile after the first pre-signalled (or combo-signalled) tile through (but not including) the next normal block signal (exit signals are still counted as part of the gap). If multiple routes exist, the largest value is the gap.<br />
<br />
Placing a pre- (or combo-) signal and an exit signal (in that order) on a mainline will create a gap larger than 1, so this type of construction should not be done without creating an alternate route.<br />
<br />
When using PBS signals, the gap is counted just like normal block signals: from the tile after the PBS signal through (but not including) the next signalled tile. If multiple routes exist, the largest value is the gap.<br />
[[Image:Signal gap counting.png | 400px | thumb | left | Counting signal gaps]] [[Image:Signal gap signals.png | 400px | thumb | left | Other signals]]<br />
<br />
<br clear=all><br />
== How many alternate routes do I need to create? ==<br />
[[Image:Signal gap bridges.png | thumb | 400px | right | Two bridges for this gap is enough for any train length]]<br />
The number of alternate routes is dependent on the length of the gap and the minimum train length that might encounter the gap.<br />
<br />
The typical formula used to calculate the maximum gap length for a certain number of lines (LineCount) is <br />
<br />
'''SignalGapLength = (TrainLength + 2) * LineCount - (TrainLength - 2)'''<br />
<br />
Where TrainLength is the minimum train length to encounter the gap, and LineCount is the sum of the alternate routes provided + 1 (the original route).<br /><br />
(This can be quickly calculated with [[User:KenjiE20/Webster|Webster's]] @gap)<br />
<br />
Conversely:<br />
<br />
'''LineCount = (SignalGapLength + TrainLength -2) / (TrainLength+2)'''<br />
<br />
Always round any fractions up to the next whole number.<br /><br />
(This can be quickly calculated with the [[IRC Commands|PublicServer bot's]] !gap)<br />
<br />
Refer to the section above for information about how to count a gap properly.<br />
<br />
<br clear=all><br />
== The Evil X ==<br />
[[Image:Signal gap evilx.png | thumb | 400px | right | The Evil X]]<br />
When two lines cross each other in an oblique (non-perpendicular) way, it creates an "evil X". The main problem with the evil X is that it inherently creates a signal gap of 2. <br />
<br />
A simple merge does not create a large gap, as long as the tiles before (on both lines) and after (on the single output line) are signalled.<br />
<br />
However, note that when the tracks cross obliquely, it is not possible to signal the output line, creating the gap.<br />
<br />
In practically all cases, evil X's should be avoided.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Signal_gap_sync.png&diff=11264File:Signal gap sync.png2010-02-16T14:53:38Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Signal_gap_settings.png&diff=11262File:Signal gap settings.png2010-02-16T14:40:07Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Signal_gap_signals.png&diff=11263File:Signal gap signals.png2010-02-16T14:40:07Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Signal_gap_bridges.png&diff=11259File:Signal gap bridges.png2010-02-16T14:40:06Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Signal_gap_counting.png&diff=11260File:Signal gap counting.png2010-02-16T14:40:06Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Signal_gap_evilx.png&diff=11261File:Signal gap evilx.png2010-02-16T14:40:06Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:PSG174.png&diff=11202File:PSG174.png2010-02-03T14:28:35Z<p>Thraxian: PSG174 archive screenshot. Lake Area.</p>
<hr />
<div>PSG174 archive screenshot. Lake Area.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Line_sync&diff=11143Line sync2010-01-20T18:22:43Z<p>Thraxian: Initial Draft</p>
<hr />
<div>{{reqscreenshot}}<br />
== Definition ==<br />
Line sync, or '''sync''' for short, is a term used in coop games when splitting a line (in most cases, a [[mainline]]). The split lines are "in sync" if they are the same length, and "out of sync" if one is shorter than the other.<br />
<br />
Sync is especially important on dense networks (lots of trains on the same line) to ensure that the line continues to flow at maximum speed without interruption.<br />
<br />
Lines that are in sync will typically shift one or more tiles (N-1, where N is the number of routes from before the shift to the end of the shift).<br />
<br />
== Seeing the Difference ==<br />
<br />
Below are two screenshots. One contains lines that are "in sync", and the other contains lines that are "out of sync".<br />
<br />
[[Image:Tunnel_Flow.png|250px|frame|left|In Sync]]<br />
[[Image:image_needed.png|250px|frame|right|(REPLACE)Out of Sync]]<br clear=all><br />
<br />
== Checking Line Sync ==<br />
The easiest way to check line sync is to use OpenTTD's measuring tool. Starting at the split, count the number of straight tracks on each route until the lines merge again. Also count the number of diagonal tracks. If all routes have the same number of straight tracks and the same number of diagonal tracks, the lines are in sync. Due to the difference in length between a straight and diagonal track, it is not always safe to assume that two diagonal tracks count as one straight track (especially on very dense networks).<br />
<br />
[[Image:image_needed.png|250px|frame|left|Measuring Line Sync]]<br clear=all><br />
<br />
== Multi-line Sync ==<br />
In cases where more than 2 tracks must be sync'd, it is often helpful to remember that trains should enter and leave the set of tracks from alternate corners of the bounding rectangle. If they enter from the southwest, they should all leave via the northeast corner.<br />
<br />
[[Image:image_needed.png|250px|frame|left|Multi-line Sync]]<br clear=all><br />
<br />
== Station Sync ==<br />
Line sync also applies to stations. If station platforms are out of sync, the resulting slowdown could impact station throughput.<br />
<br />
[[Image:image_needed.png|250px|frame|left|Station Sync]]<br clear=all><br />
<br />
== Synchronized corners ==<br />
When synchronizing tracks that go around corners, take special care to count the diagonal tracks. In some cases, it may be impossible to create an accurate sync. <br />
<br />
[[Image:image_needed.png|250px|frame|left|Sync around corners]]<br clear=all><br />
<br />
== X-Sync ==<br />
Below is a special sync case. It uses an X crossing between two split tracks to maintain line sync. Note that while this [[Signal gap|evil-X]] is typically frowned upon, this case is ok because both tracks *should* not be in use at the same time (because trains came from the same original track).<br />
<br />
[[Image:X-Sync.png|250px|frame|left|X-sync]]<br clear=all></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Signal_gap&diff=11136Signal gap2010-01-19T23:01:52Z<p>Thraxian: Initial Draft - needs images</p>
<hr />
<div>== Definition ==<br />
A signal gap, or gap for short, is the amount of unsignalled space in a single signal block. Understanding signal gaps is important for maximizing train density on a rail line and ensuring that trains continue to move at the maximum allowable speed. In coop games, we adhere to a maximum signal gap of 1 tile.<br />
<br />
In general, use of the term "gap" indicates that a signal gap of length greater than 1 has been detected, and as a result, the efficiency of the network is at risk. Steps should be taken to fix any gaps marked in this manner.<br />
<br />
Do not confuse a "signal gap" with a "train gap". A train gap is the minimum space between two trains. Because our signals are 2 spaced tiles apart (also known as [http://wiki.openttd.org/Railway_Designs Signal Density]), there is a minimum gap of 3 (the Signal Density +1). <br />
<br />
== Why is understanding gaps important? ==<br />
<br />
A rail line is only as fast as its weakest link. If there is any point on the line where traffic must slow down or stop, the disruption will have a domino effect on any following trains, resulting in an inefficient network. As the goal is often to build a highly-efficient, and highly-dense network, these types of disruptions must be avoided at all costs!<br />
<br />
== What if I need to create a signal gap larger than 1? ==<br />
<br />
To create a signal gap larger than 1, you must provide following trains an alternate route until the gap is restored to 1. Larger gaps are created at station platforms, bridges, and tunnels, since none of these items can be signalled.<br />
<br />
To create an alternate route, simply make a new line parallel to the first line. This line should continue until the signal gap can be restored to 1, making sure to keep the trains [[synchronize]]d.<br />
<br />
== How to count the length of a gap ==<br />
When using normal block signals, a gap's length is defined as the number of unsignalled spaces between two signals. Normal coop [[mainline]]s use a signal gap of 1, meaning there is only 1 unsignalled tiles between two signallled tiles.<br />
<br />
When using pre-signals, the gap is counted from the tile after the first pre-signalled (or combo-signalled) tile through (but not including) the next normal block signal (exit signals are still counted as part of the gap). If multiple routes exist, the largest value is the gap.<br />
<br />
Placing a pre- (or combo-) signal and an exit signal (in that order) on a mainline will create a gap larger than 1, so this type of construction should not be done without creating an alternate route.<br />
<br />
When using PBS signals, the gap is counted just like normal block signals: from the tile after the PBS signal through (but not including) the next signalled tile. If multiple routes exist, the largest value is the gap.<br />
<br />
== How many alternate routes do I need to create? ==<br />
<br />
The number of alternate routes is dependent on the length of the gap and the minimum train length that might encounter the gap.<br />
<br />
The typical formula used to calculate the maximum gap length for a certain number of lines (LineCount) is <br />
<br />
'''SignalGapLength = (TrainLength + 2) * LineCount - (TrainLength - 2)'''<br />
<br />
Where TrainLength is the minimum train length to encounter the gap, and LineCount is the sum of the alternate routes provided + 1 (the original route).<br />
<br />
Conversely:<br />
<br />
'''LineCount = (SignalGapLength + TrainLength -2) / (TrainLength+2)'''<br />
<br />
Always round any fractions up to the next whole number.<br />
<br />
Refer to the section above for information about how to count a gap properly.<br />
<br />
== The Evil X ==<br />
<br />
When two lines cross each other in an oblique (non-perpendicular) way, it creates an "evil X". The main problem with the evil X is that it inherently creates a signal gap of 2. <br />
<br />
A simple merge does not create a large gap, as long as the tiles before (on both lines) and after (on the single output line) are signalled.<br />
<br />
However, note that when the tracks cross obliquely, it is not possible to signal the output line, creating the gap.<br />
<br />
In practically all cases, evil X's should be avoided.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Shift_Mainline&diff=11133Shift Mainline2010-01-18T19:04:47Z<p>Thraxian: Initial Draft</p>
<hr />
<div>== Definition ==<br />
A Shift Mainline, or SML, is a special type of [[Mainline]] used in coop games. SML behaves almost identically to a normal mainline. They are [[signalling|signaled]] the same, require the same bridge and tunnel constructions, and inherit all the other characteristics of a normal ML. What distinguishes an SML from a normal mainline is how junctions are performed.<br />
<br />
When a [[sideline]] merges to a normal Mainline (a [[SLH]] junction), the sideline should be able to choose to merge with any of the ML lanes. These merges are [[priority|prioritized]] to ensure ML traffic is not slowed or stopped due to a merging train.<br />
<br />
When a sideline merges to a Shift Mainline, the sideline is only allowed to merge to one (or possibly more) of the ML lanes. Again, these merges are prioritized. However, on an SML, trains on the ML will attempt to move, or shift, to other lanes on the ML to free up the merging lane(s) for incoming trains.<br />
<br />
''This behavior mimics real-world traffic patterns. When travelling on a high-capacity roadway, motorists will often choose to travel on the innermost lanes, which are generally reserved for through-traffic. These lanes do not suffer from slowdowns due to merging traffic on the outer lanes. Motorists "shift" to the inside lanes to make way for new motorists entering the roadway. This same logic is applied to SML construction.''<br />
<br />
== How it works ==<br />
The shifting on an SML occurs by placing [[penalties|penalty]] on the lanes that oncoming traffic will merge into. These penalties may be built as stations (trains should use non-stop orders if stations are used), reverse PBS signals, or any other construction that would force a train on that lane to search for an alternate route, in this case, another lane on the mainline. <br />
<br />
These shifts on the SML must behave like any other mainline by granting priority to any traffic currently on the lane the train wishes to merge into. A priority lane must be defined, and if the train seeking an alternate route (the "shifting train") can safely move to another lane without slowing or stopping traffic, it does so. If not, it continues on its current path, through the penalty. <br />
<br />
SMLs with more than two lanes moving in one direction will typically contain multiple opportunities for trains to shift. Consider a 3-lane SML, where A is the innermost lane, B is the middle lane, and C is the outermost lane. Merging trains will attempt to enter lane C, so trains must shift from lane C to lane B to make room for these merging trains. However, it makes sense to first shift trains from lane B to lane A, making more room on lane B for the trains shifting from lane C.<br />
<br />
== How to detect SML ==<br />
SMLs are easily detected by looking for these shifting opportunities. These typically occur just before a SLH, and are easily recognizable due to the way the mainlines are connected (which rarely happens otherwise) and the priorities involved. <br />
<br />
SML is also frequently noted on the network plan during the design phase of the game. When in doubt, ask if SML is being used.<br />
<br />
== Additional Notes ==<br />
* Due to the nature of SML, the lanes in the mainline will inherently become imbalanced, with more traffic on the innermost lanes, and less traffic on the outermost (or merging) lanes. This imbalance should be taken into consideration during [[BBH]] and [[Main station|Mainline Station]] construction.<br />
<br />
* Ensure that the shifts always occur in the '''same direction'''. Check the plan for the direction of the shift (left or right, relative to the flow of traffic). If not mentioned on the plan, look for a nearby SML construction on the mainline (in the same direction) and use the same logic. If opposite directions are used, merging will become impossible due to the traffic density that occurs on the merging lane.<br />
<br />
* Trains should have shifting opportunities prior to every SLH. When the SML has more than two lanes, trains should generally receive the opportunity to shift all the way across the ML to ensure the best chance for full-speed merges from the sideline. Optionally, shifts may also occur after an SLH, especially in cases where space would make shifting difficult before the next SLH.<br />
<br />
== SML Implementations ==<br />
Several SML designs have been created. More information can be found on the [[Shift_Mainlines_(Research)|Research]] page.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User_talk:Ammler&diff=11119User talk:Ammler2010-01-15T13:30:27Z<p>Thraxian: /* Drum Corps Exhibition */ new section</p>
<hr />
<div>who said you were too old to play TTD, i'm only 2 years younger than you! :P [[User:Spectre100|Spectre100]] 10:29, 17 August 2007 (UTC)<br />
:So, you see, I'm older ;) --[[User:Ammler|Ammler]] 15:04, 17 August 2007 (UTC)<br />
::Still doesn't mean you're too old, one of my guild wars guildies plays, he's 43[[User:Spectre100|Spectre100]] 17:30, 19 August 2007 (UTC)<br />
<br />
== Drum Corps Exhibition ==<br />
<br />
Thought you might like [http://www.drummerworld.com/watchlistdrummers/Top_Secret_Drum_Corps.html| this video] - you've gotta have national pride after seeing something like this! My dad sent it to me, and after seeing the flags, I immediately thought of you. The last 30 seconds are particularly impressive, if you don't have time for the whole 6 minutes. -- [[User:Thraxian|Thraxian]] 13:30, 15 January 2010 (UTC)<br />
:Please note that while I am posting an external link, like so many of late, mine is actually appropriate for the page it is being placed on, and I am a well-established member of the community. Don't <strike>tase</strike> ban me, dude! -- also [[User:Thraxian|Thraxian]] 13:30, 15 January 2010 (UTC)</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_161_-_170&diff=10685PublicServer:Archive - Games 161 - 1702009-10-21T13:56:59Z<p>Thraxian: Updates to PSG 161</p>
<hr />
<div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br />
<br />
{{Archive_PublicServer|Public Server Game 162|11.10.09-20.10.09| {{User|Chris Booth}}, {{User|Thraxian}}, {{User|ZarenorDarkstalker}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 1024 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| It all started with a two-way SML ML loop with main stations on the corners and a single BBH on each edge. Over 1650 trains later, most of the farms had closed - wood, coal, and oil became the chief exports. Later in the game, balancing the loads on the sidelines became the challenge, as some sidelines were sparse while others were over capacity. Shifting some stations from one mainline to another helped alleviate a lot of the congestion.|162|File:PSG162.png| One of several high-output wood stations}}<br />
<br />
{{Archive_PublicServer|Public Server Game 161|03.10.09-11.10.09| {{User|Chris Booth}}, {{User|DCritic}}, {{User|AlexanderB}}, {{User|Petert}}, {{User|Tussengas}}, {{User|tneo}}, {{User|^Spike^}}, {{User|Stoffe}} | [[Gametype:Cargo_Concept|Cargo]] & RV | TL7 | 128 x 2048 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| Originally intended to be an RV-only game, the 2048 dimension made several players rethink that strategy. Instead, local RV networks were connected by a backbone rail line. 2000 cars and 600 trains carried cargo as fast as they could - which wasn't very fast (iron trucks carried 19 tons each at 80km/h). |161|File:PSG161.png| Don't drink and drive - you might get lost!}}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:PSG161.png&diff=10684File:PSG161.png2009-10-21T13:50:15Z<p>Thraxian: Don't drink and drive - you might get lost!</p>
<hr />
<div>Don't drink and drive - you might get lost!</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_161_-_170&diff=10683PublicServer:Archive - Games 161 - 1702009-10-21T13:44:30Z<p>Thraxian: Updates to 162</p>
<hr />
<div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br />
<br />
{{Archive_PublicServer|Public Server Game 162|11.10.09-20.10.09| {{User|Chris Booth}}, {{User|Thraxian}}, {{User|ZarenorDarkstalker}} | [[Gametype:Cargo_Concept|Cargo]] | TL3 | 512 x 1024 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| It all started with a two-way SML ML loop with main stations on the corners and a single BBH on each edge. Over 1650 trains later, most of the farms had closed - wood, coal, and oil became the chief exports. Later in the game, balancing the loads on the sidelines became the challenge, as some sidelines were sparse while others were over capacity. Shifting some stations from one mainline to another helped alleviate a lot of the congestion.|162|File:PSG162.png| One of several high-output wood stations}}<br />
<br />
{{Archive_PublicServer|Public Server Game 161|03.10.09-11.10.09| {{User|Chris Booth}}, {{User|DCritic}}, {{User|AlexanderB}}, {{User|Petert}} | [[Gametype:Cargo_Concept|Cargo]] & RV | TL7 | 128 x 2048 Temperate| r17687 [[GRF|#openttdcoop-GRF-Pack 7.3]]| Game summary |161|File:PSG161.png| Image Caption}}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:PSG162.png&diff=10682File:PSG162.png2009-10-21T13:29:02Z<p>Thraxian: uploaded a new version of "File:PSG162.png":&#32;resized to make a shorter thumbnail for archive</p>
<hr />
<div>One of several high-output wood stations</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:PSG162.png&diff=10681File:PSG162.png2009-10-21T13:24:37Z<p>Thraxian: One of several high-output wood stations</p>
<hr />
<div>One of several high-output wood stations</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/NewUsers&diff=10678User:Thraxian/NewUsers2009-10-20T14:16:43Z<p>Thraxian: attempting to remove section edit links</p>
<hr />
<div>__NOEDITSECTION__<br />
{|<br />
|- <br />
| width=250 valign=top |<br />
{|<br />
|-<br />
| width=250 valign=top |<br />
==Active Members ({{PAGESINCATEGORY:Active Members}})==<br />
<DPL><br />
category=Active Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|-<br />
| width=250 valign=top |<br />
==Honorary Members ({{PAGESINCATEGORY:Honorary Members}})==<br />
<DPL><br />
category= Honorary Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}<br />
| width=100 valign=top |<br />
{|<br />
|-<br />
| &nbsp;<br />
|}<br />
| width=750 valign=top |<br />
{|<br />
|-<br />
| width=750 valign=top |<br />
==Usual Suspects ({{PAGESINCATEGORY:Usual Suspects}})==<br />
<DPL><br />
category=Usual Suspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}<br />
|- <br />
| width=250 valign=top |<br />
==Inactive Members ({{PAGESINCATEGORY: Inactive Members}})==<br />
<DPL><br />
category= Inactive Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=100 valign=top | &nbsp;<br />
| width=750 valign=top |<br />
==Ex-suspects ({{PAGESINCATEGORY:Exsuspects}})==<br />
<DPL><br />
category=Exsuspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/NewUsers&diff=10677User:Thraxian/NewUsers2009-10-20T14:14:15Z<p>Thraxian: Added honoraries</p>
<hr />
<div>{|<br />
|- <br />
| width=250 valign=top |<br />
{|<br />
|-<br />
| width=250 valign=top |<br />
==Active Members ({{PAGESINCATEGORY:Active Members}})==<br />
<DPL><br />
category=Active Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|-<br />
| width=250 valign=top |<br />
==Honorary Members ({{PAGESINCATEGORY:Honorary Members}})==<br />
<DPL><br />
category= Honorary Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}<br />
| width=100 valign=top |<br />
{|<br />
|-<br />
| &nbsp;<br />
|}<br />
| width=750 valign=top |<br />
{|<br />
|-<br />
| width=750 valign=top |<br />
==Usual Suspects ({{PAGESINCATEGORY:Usual Suspects}})==<br />
<DPL><br />
category=Usual Suspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}<br />
|- <br />
| width=250 valign=top |<br />
==Inactive Members ({{PAGESINCATEGORY: Inactive Members}})==<br />
<DPL><br />
category= Inactive Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=100 valign=top | &nbsp;<br />
| width=750 valign=top |<br />
==Ex-suspects ({{PAGESINCATEGORY:Exsuspects}})==<br />
<DPL><br />
category=Exsuspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/NewUsers&diff=10676User:Thraxian/NewUsers2009-10-20T14:03:40Z<p>Thraxian: Added inactive players</p>
<hr />
<div>{|<br />
|- <br />
| width=250 valign=top |<br />
==Active Members ({{PAGESINCATEGORY:Active Members}})==<br />
<DPL><br />
category=Active Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=100 valign=top | &nbsp;<br />
| width=750 valign=top |<br />
==Usual Suspects ({{PAGESINCATEGORY:Usual Suspects}})==<br />
<DPL><br />
category=Usual Suspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}<br />
<br />
{|<br />
|- <br />
| width=250 valign=top |<br />
==Inactive Members ({{PAGESINCATEGORY: Inactive Members}})==<br />
<DPL><br />
category= Inactive Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=100 valign=top | &nbsp;<br />
| width=750 valign=top |<br />
==Ex-suspects ({{PAGESINCATEGORY:Exsuspects}})==<br />
<DPL><br />
category=Exsuspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Phazorx&diff=10675User:Phazorx2009-10-20T13:58:29Z<p>Thraxian: removed canadian flag for proper inclusion in NewUsers list</p>
<hr />
<div>'''Born:''' 22.05.77<br />
<br />
'''Home:''' St.-Petersburg, Russia {{Flag|ru}}<br />
<br />
'''Residence:''' Toronto, Canada<br />
<br />
'''Email:''' pavelkolla[at]gmx[dot]net<br />
<br />
'''Homepage:''' /me waves hand; "This is not the homepage you are looking for..."<br />
<br />
'''Started playing TTD:''' Actually it was TTO, back in 94 as i recall<br />
<br />
'''Joined #openttdcoop:''' April 2007<br />
<br />
'''Specialist on:''' balanced mergers, shuttle/transfer subnetworks, streamline ML traffic<br />
<br />
'''Prefers:''' games that are based on single efficient network or multiple performing networks.<br />
<br />
'''Dislikes:''' missing signals at ML, jams at SLHs (especially mine), loud 13 yearolds<br />
[[Category:Active Members]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Test&diff=10674User:Test2009-10-20T13:57:51Z<p>Thraxian: moved to usual suspects category</p>
<hr />
<div>Test user with no flag.<br />
<br />
[[Category:Usual Suspects]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:%5ESpike%5E&diff=10673User:^Spike^2009-10-20T13:56:41Z<p>Thraxian: moved to active members category</p>
<hr />
<div>The bored tumtidum Dutch guy.<br />
<br />
Student Computer Science<br />
<br />
All-round gamer (CSS, OTTD, AA3, The other i forgot)<br />
<br />
Oh and did i mention I was {{flag|nl}}?<br />
<br />
Hanging around several games from 139 till well now :)<br />
[[Category:Active Members]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Phazorx&diff=10672User:Phazorx2009-10-20T13:55:24Z<p>Thraxian: moved to active members category</p>
<hr />
<div>'''Born:''' 22.05.77<br />
<br />
'''Home:''' St.-Petersburg, Russia {{Flag|ru}}<br />
<br />
'''Residence:''' Toronto, Canada {{Flag|ca}}<br />
<br />
'''Email:''' pavelkolla[at]gmx[dot]net<br />
<br />
'''Homepage:''' /me waves hand; "This is not the homepage you are looking for..."<br />
<br />
'''Started playing TTD:''' Actually it was TTO, back in 94 as i recall<br />
<br />
'''Joined #openttdcoop:''' April 2007<br />
<br />
'''Specialist on:''' balanced mergers, shuttle/transfer subnetworks, streamline ML traffic<br />
<br />
'''Prefers:''' games that are based on single efficient network or multiple performing networks.<br />
<br />
'''Dislikes:''' missing signals at ML, jams at SLHs (especially mine), loud 13 yearolds<br />
[[Category:Active Members]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Nickman&diff=10671User:Nickman2009-10-20T13:53:15Z<p>Thraxian: moved to usual suspects category</p>
<hr />
<div>'''Born:''' 24th of June 1987 [[Category:Usual Suspects]]<br />
<br />
'''Home:''' Edegem/Antwerp, Belgium {{Flag|be}}<br />
<br />
'''Homepage:''' [http://www.bwf.be BWF-LAN]<br />
<br />
'''Started with TT:''' Discovered OTTD and got addicted to train building! Started coop at Game 08 but had a big stop in between :).<br />
<br />
'''Likes:''' Chaos, eyecandy, optimizations, crashing trains...<br />
<br />
'''Dislikes:''' Ugly landscaping, un-symmetric stuff<br />
<br />
'''Specialist on:''' Optimizing other peoples junctions/stations/...<br />
<br />
'''Weaknesses:''' Taking initiative to build something new</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Kommer&diff=10670User:Kommer2009-10-20T13:52:45Z<p>Thraxian: moved to inactive member category</p>
<hr />
<div>'''Born:''' 1979 [[Category:Inactive Members]]<br />
<br />
'''Home:''' The Netherlands<br />
<br />
'''Email:''' -<br />
<br />
'''Homepage:''' -<br />
<br />
'''Started playing TTD:''' When TTD was first in store.<br />
<br />
'''Prefers:''' Searching networks for errors, improving stuff<br />
<br />
'''Dislikes:''' terraforming (a lot),<br />
<br />
'''#openttdcoop:''' Player since august 2007. Member since october 2007.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/NewUsers&diff=10669User:Thraxian/NewUsers2009-10-20T13:44:35Z<p>Thraxian: Changed to only show active players - suspects in 3 columns</p>
<hr />
<div>{|<br />
|- <br />
| width=250 valign=top |<br />
==Active Members ({{PAGESINCATEGORY:Active Members}})==<br />
<DPL><br />
category=Active Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=100 valign=top | &nbsp;<br />
| width=750 valign=top |<br />
==Usual Suspects ({{PAGESINCATEGORY:Usual Suspects}})==<br />
<DPL><br />
category=Usual Suspects<br />
mode=userformat<br />
columns=3<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=Template:User&diff=10668Template:User2009-10-20T13:39:46Z<p>Thraxian: removed whitespace</p>
<hr />
<div>[[User:{{{1}}}|{{{1}}}]]{{ #if: {{{2|}}}| {{Flag|{{{2}}}}}}}<noinclude><br />
<!-- Put it in the template Category !--><br />
[[Category:Templates|{{PAGENAME}}]]<br />
</noinclude></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/NewUsers&diff=10665User:Thraxian/NewUsers2009-10-20T13:36:08Z<p>Thraxian: Playing with 3 column display</p>
<hr />
<div>{|<br />
|- <br />
| width=250 valign=top |<br />
==Active Members ({{PAGESINCATEGORY:Active Members}})==<br />
<DPL><br />
category=Active Members<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=250 valign=top |<br />
==Usual Suspects ({{PAGESINCATEGORY:Usual Suspects}})==<br />
<DPL><br />
category=Usual Suspects<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
| width=250 valign=top |<br />
==Retired Players ({{PAGESINCATEGORY:Retired Players}})==<br />
<DPL><br />
category=Retired Players<br />
mode=userformat<br />
include={flag}:1, [[%PAGE%]]<br />
listseparators={|\n!style="width:100px;align:left;"|\n!style="width:50px;align:left;"|,\n|-\n|[[%PAGE%|%TITLE%]]\n|,,\n|}<br />
secseparators=style="align: center;"|{{flag|,}}<br />
</DPL><br />
|}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User_talk:V453000&diff=10649User talk:V4530002009-10-13T17:38:00Z<p>Thraxian: </p>
<hr />
<div>Hello world testing<br />
<br />
== Preview? ==<br />
Any chance you could try using the "Show Preview" button when making edits? The [[Special:RecentChanges]] page got hit REALLY hard from all your edits...<br />
<br />
I'm not trying to discourage you from wiki editing - far from it! Just wanted to be sure you were aware of the preview button, and how it impacts the wiki if you choose not to use it.<br />
<br />
Thanks! -- [[User:Thraxian|Thraxian]] 17:38, 13 October 2009 (UTC)</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian&diff=10243User:Thraxian2009-06-16T17:43:37Z<p>Thraxian: </p>
<hr />
<div>== About Me ==<br />
{|<br />
|-<br />
| width=200 | <br />
| width=300 |<br />
|-<br />
| '''Born:''' || 1977<br />
|-<br />
|'''Home:''' || North Carolina, USA {{flag|us}}<br />
|-<br />
|'''Email:''' || thraxian[at]nc[dot]rr[dot]com<br />
|-<br />
|'''Occupation:''' || Software design, development, testing, and support<br />
|-<br />
| colspan=2 | &nbsp;<br />
|-<br />
|'''Started playing TTD:''' || Don't remember, but possibly mid-late 90's.<br />
|-<br />
|'''Discovered #openttdcoop:''' || August 2007<br />
|-<br />
|'''Promoted to "Usual Suspect":''' || September 13, 2007<br />
|-<br />
|'''Promoted to "Member":''' || November 19, 2007<br />
|-<br />
| colspan=2 | &nbsp;<br />
|-<br />
|'''Strengths:''' || Debugging problematic lines, building and managing SL networks, avoiding terraforming<br />
|-<br />
|'''Weaknesses:''' || Complex hubs, very advanced techniques (SML, for example)<br />
|-<br />
|'''Prefers:''' || Teamwork, strict adherence to plan, working efficiently with the terrain<br />
|-<br />
|'''Dislikes:''' || Deviations from plan, careless terraforming, large and expensive eye-candy spending, band-aid solutions<br />
|-<br />
| colspan=2 | &nbsp;<br />
|-<br />
|'''Other Gaming Interests:''' || Battlefield 2, Guild Wars, Titan Quest, Sacred, Diablo II, Unreal Tournament<br />
|}<br />
<br />
<br />
== Subpages ==<br />
=== Concepts ===<br />
* [[User:Thraxian/ML_Bypass| ML Bypass]] (aka XML) - Express lane for ML to connect BBHs or drop stations without SL interference<br />
* [[User:Thraxian/Station Separation| Station Separation]] - How to effectively separate a single station into pickup/drop stations<br />
* [[User:Thraxian/Diverging Diamond| Diverging Diamond Interchange]] - A new interchange design<br />
* [[User:Thraxian/RV City Service| RV City Service]] - How to effectively service an entire city with minimal station walk.<br />
=== Proposals ===<br />
* [[User:Thraxian/Frontpage| Frontpage Proposal]] - Proposed rework of the wiki frontpage<br />
* [[User:Thraxian/Voting | Voting Proposals]] - Proposed changes to the voting process for public server games<br />
* [[User:Thraxian/GamePlanOnWiki | Wiki Planning]] - Proposal for wiki planning of Public Server games<br />
<br />
=== Miscellaneous ===<br />
* [[User:Thraxian/Junctions | Junctionary Candidates]] - Screenshots awaiting critique and approval before formal entry to Junctionary<br />
=== Games ===<br />
* [[http://www.openttdcoop.org/files/pm/expert2.sav Savegame]] from an experts server which we conquered as #openttdcoop<br />
<br />
[[Category:Active Members]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/RV_City_Service&diff=10242User:Thraxian/RV City Service2009-06-16T17:42:56Z<p>Thraxian: New page: == Overview == 800px == Description == The goal is to provide an efficient way to provide passenger service to an entire city without major station walking. ...</p>
<hr />
<div>== Overview ==<br />
[[Image:RV City Service.png|800px]]<br />
<br />
== Description ==<br />
The goal is to provide an efficient way to provide passenger service to an entire city without major station walking. One major problem to address is that RV queues can block through traffic on roads. <br />
<br />
== How it Works ==<br />
The use of Road Vehicles is preferred here. Trains and stations require too much real-estate, reducing the amount of space for cities to build. Road stations are built on existing roads, providing the maximum amount of space for cities to grow.<br />
<br />
The use of one-way streets allows for queues to form without blocking traffic. Each station has two blocks (6 tiles) of queue space, which should sufficiently handle any queue that forms for that station. If the queue becomes too long, then there are likely too many buses servicing that station.<br />
<br />
A bus stop placed in an intersection will cover the 4 3x3 city blocks adjacent to that intersection. Since stations cannot be placed on an intersection, we place bus stops on two opposite sides (using a 3rd station temporarily to walk across the intersection). One such station is created at every other intersection to ensure total coverage of the city.<br />
<br />
Every other line into the city is considered a major artery. These arteries should never block and provide buses access to and from their respective stations. Upon reaching the intersection prior to the cross-street that contains their stop, the bus will turn off, and then make another turn to approach their station's intersection. Buses can go either direction at the intersection to reach a station platform. The bus will leave the station to immediately join a major artery, which will take them to the transfer station for the local ICE/SBahn terminal.<br />
<br />
Each station has a separate list of buses which will perform a full-load pickup, and then do a transfer no-load drop at the ICE/SBahn terminal. Separate buses ensure that each station can be serviced independently and no station will backup due to insufficient cargo at another station causing buses to backup (due to full-load orders).<br />
<br />
In larger cities, it may be best to create several SBahn stations for bus transfers, and have them all connect to an ICE terminal located outside of town. Building these SBahn stations can be done to enhance the coverage and symmetry of the network.<br />
<br />
== Disadvantages ==<br />
Lots of RVs are required for large cities. Limiting the number of cities with this type of infrastructure will help with the server load caused by so many vehicles.<br />
<br />
Some stations may create more passengers than two bus stops can keep up with. In these cases, the station can be expanded into 2+2 stations by simply adding another loading area adjacent to the existing one. <br />
<br />
Stations deeper into the city will require additional buses due to the driving distance/time involved in reaching the ICE/SBahn terminal. As the ICE/SBahn terminal is likely on the outskirts of the city, these deeper stations will likely be closer to the city center, which will generate more passengers anyways.<br />
<br />
Monitoring of each station will be required to ensure that they are all being serviced adequately. Using a common naming convention for each station (based on coordinates relative to the city center) may facilitate this monitoring.<br />
<br />
Generally flat land is required to create such a network, as the road depots cannot be built on slopes. Expanding the station (as mentioned above) should be considered when terraforming the city to meet this requirement.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:RV_City_Service.png&diff=10241File:RV City Service.png2009-06-16T17:27:00Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian&diff=10240User:Thraxian2009-06-16T17:24:14Z<p>Thraxian: </p>
<hr />
<div>== About Me ==<br />
{|<br />
|-<br />
| width=200 | <br />
| width=300 |<br />
|-<br />
| '''Born:''' || 1977<br />
|-<br />
|'''Home:''' || North Carolina, USA {{flag|us}}<br />
|-<br />
|'''Email:''' || thraxian[at]nc[dot]rr[dot]com<br />
|-<br />
|'''Occupation:''' || Software design, development, testing, and support<br />
|-<br />
| colspan=2 | &nbsp;<br />
|-<br />
|'''Started playing TTD:''' || Don't remember, but possibly mid-late 90's.<br />
|-<br />
|'''Discovered #openttdcoop:''' || August 2007<br />
|-<br />
|'''Promoted to "Usual Suspect":''' || September 13, 2007<br />
|-<br />
|'''Promoted to "Member":''' || November 19, 2007<br />
|-<br />
| colspan=2 | &nbsp;<br />
|-<br />
|'''Strengths:''' || Debugging problematic lines, building and managing SL networks, avoiding terraforming<br />
|-<br />
|'''Weaknesses:''' || Complex hubs, very advanced techniques (SML, for example)<br />
|-<br />
|'''Prefers:''' || Teamwork, strict adherence to plan, working efficiently with the terrain<br />
|-<br />
|'''Dislikes:''' || Deviations from plan, careless terraforming, large and expensive eye-candy spending, band-aid solutions<br />
|-<br />
| colspan=2 | &nbsp;<br />
|-<br />
|'''Other Gaming Interests:''' || Battlefield 2, Guild Wars, Titan Quest, Sacred, Diablo II, Unreal Tournament<br />
|}<br />
<br />
<br />
== Subpages ==<br />
=== Concepts ===<br />
* [[User:Thraxian/ML_Bypass| ML Bypass]] (aka XML) - Express lane for ML to connect BBHs or drop stations without SL interference<br />
* [[User:Thraxian/Station Separation| Station Separation]] - How to effectively separate a single station into pickup/drop stations<br />
* [[User:Thraxian/Diverging Diamond| Diverging Diamond Interchange]] - A new interchange design<br />
=== Proposals ===<br />
* [[User:Thraxian/Frontpage| Frontpage Proposal]] - Proposed rework of the wiki frontpage<br />
* [[User:Thraxian/Voting | Voting Proposals]] - Proposed changes to the voting process for public server games<br />
* [[User:Thraxian/GamePlanOnWiki | Wiki Planning]] - Proposal for wiki planning of Public Server games<br />
<br />
=== Miscellaneous ===<br />
* [[User:Thraxian/Junctions | Junctionary Candidates]] - Screenshots awaiting critique and approval before formal entry to Junctionary<br />
=== Games ===<br />
* [[http://www.openttdcoop.org/files/pm/expert2.sav Savegame]] from an experts server which we conquered as #openttdcoop<br />
<br />
[[Category:Active Members]]</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=User:Thraxian/Diverging_Diamond&diff=10239User:Thraxian/Diverging Diamond2009-06-16T17:23:39Z<p>Thraxian: New page: == Overview == 800px == Description == The primary purpose is to design a hub that eliminates or reduces the need for bridges/tunnels in 4-way interchanges...</p>
<hr />
<div>== Overview ==<br />
[[Image:Diverging Diamond.png|800px]]<br />
<br />
== Description ==<br />
The primary purpose is to design a hub that eliminates or reduces the need for bridges/tunnels in 4-way interchanges. This design comes from a similarly named road interchange design (see http://en.wikipedia.org/wiki/Diverging_diamond_interchange).<br />
<br />
== How it Works ==<br />
The most prominent feature of this type of interchange is the reversal of lane direction under the primary line. In this diagram, the north/south line begins as LL_RR, but changes to RR_LL under the mainline (east/west) bridges, and then reverts back to LL_RR.<br />
<br />
This reversal allows for entrances and exits to be made without having to cross over traffic (as those crossing are done in advance of the interchange).<br />
<br />
== Drawbacks ==<br />
The main drawback for this type of interchange is the merge before split that occurs under the bridge. This could likely be resolved by adding additional levels underneath the interchange, or possibly splitting the left turns prior to the merge.</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:Diverging_Diamond.png&diff=10237File:Diverging Diamond.png2009-06-16T17:18:06Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_141_-_150&diff=10236PublicServer:Archive - Games 141 - 1502009-06-16T16:12:01Z<p>Thraxian: Added users to 145 based on BBH/MSH sign list</p>
<hr />
<div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br />
<br />
{{Archive_PublicServer|Public Server Game 145|05.06.09-16.06.09| {{User|Thraxian}}, {{User|Mark}}, {{User|Strix}}, {{User|ODM}}, {{User|mensi}}, {{User|uliko}}, {{User|Combuster}}, {{User|theholyduck}}, {{User|hafai}} | [[Gametype:Cargo_Concept|Cargo]] & PAX | TL 4 & 6 | 512 x 512 Temperate | 16520 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
After selecting a plan, construction began. Then construction continued. And some more construction. Practically everything in the game was reworked at least once, so it took time before trains starting moving. Several new players joined the server, so the late-game included lots of instruction and guidance. In the end, the network ran fairly smoothly, and most industries were connected. |145|Image:PSG145.png| BBHs and MSHs were packed in tightly on this map}}<br />
<br />
{{Archive_PublicServer|Public Server Game 144|01.06.09-05.06.09| {{User|Thraxian}}, | [[Gametype:Cargo_Concept|Cargo]] | TL 5 | 512 x 512 Toyland | r16381 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
Intended to be a proof of the Davil-style hub (a recent blog article), this plan never really got off the ground. The loop was made too large, and later shrunk to a more manageable size. The Mainlines radiating from the loop were developed, but no industries (and consequently no trains) ever touched the network. In the end, the graphics proved to be too hard on the eyes and the game was scrapped in favor of a new climate. |144|Image:PSG144.png| Part of the 3-way Town Drop station}}<br />
<br />
{{Archive_PublicServer|Public Server Game 143|23.05.09-01.06.09| {{User|tneo}}, | [[Gametype:Cargo_Concept|Cargo]] & Pax | TL 8 & 12 | 512 x 512 Temperate | r16381 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
The original plan involving many twoway loops and lots of massive BBHs, combined with different trainspeeds and trainlengths proved to be too hard. We decided to get rid of the inner loop and seperate the pax and cargo network, in the end the map came out pretty well. |143|Image:PSG143.png| Showing an openttdcoop first: a full 5-way BBH.}}<br />
<br />
{{Archive_PublicServer|Public Server Game 142|15.05.09-23.05.09| {{User|tneo}}, {{User|Chris_booth}},| [[Gametype:Cargo_Concept|Cargo]] |TL 5 | 512 x 512 Temperate | r16341 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
The goal of the plan chosen was to have a high capacity network that worked with the map. We ended up with an LLLL_RRRR babcbone loop to which the other MLs were connected. |142|Image:PSG142.png| BBH02 is one of the 6 big BBHs in this game.}}<br />
<br />
{{Archive_PublicServer|Public Server Game 141|08.05.09-15.05.09| {{User|tneo}}, {{User|planetmaker}}, {{User|gleeb}}, {{User|uliko}}, {{User|ODM}}, {{User|Chris_booth}}, {{User|Combuster}}, | [[Gametype:Cargo_Concept|Cargo]] |TL 5 | 512 x 256 Sub-Tropical | r16277 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
This game featured a central hub station with an LL_RR leg to either side, trains picked up at both ends of the legs. After delivering their cargo trains were heading for the nearest depot to be refitted. This way train amount required was less then usual and trains mostly didn't travel empty.|141|Image:PSG141.png| An oil pickup station initally used for the MM.}}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_141_-_150&diff=10235PublicServer:Archive - Games 141 - 1502009-06-16T16:08:03Z<p>Thraxian: Added PSG145</p>
<hr />
<div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br />
<br />
{{Archive_PublicServer|Public Server Game 145|05.06.09-16.06.09| {{User|Thraxian}}, | [[Gametype:Cargo_Concept|Cargo]] & PAX | TL 4 & 6 | 512 x 512 Temperate | 16520 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
After selecting a plan, construction began. Then construction continued. And some more construction. Practically everything in the game was reworked at least once, so it took time before trains starting moving. Several new players joined the server, so the late-game included lots of instruction and guidance. In the end, the network ran fairly smoothly, and most industries were connected. |145|Image:PSG145.png| BBHs and MSHs were packed in tightly on this map}}<br />
<br />
{{Archive_PublicServer|Public Server Game 144|01.06.09-05.06.09| {{User|Thraxian}}, | [[Gametype:Cargo_Concept|Cargo]] | TL 5 | 512 x 512 Toyland | r16381 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
Intended to be a proof of the Davil-style hub (a recent blog article), this plan never really got off the ground. The loop was made too large, and later shrunk to a more manageable size. The Mainlines radiating from the loop were developed, but no industries (and consequently no trains) ever touched the network. In the end, the graphics proved to be too hard on the eyes and the game was scrapped in favor of a new climate. |144|Image:PSG144.png| Part of the 3-way Town Drop station}}<br />
<br />
{{Archive_PublicServer|Public Server Game 143|23.05.09-01.06.09| {{User|tneo}}, | [[Gametype:Cargo_Concept|Cargo]] & Pax | TL 8 & 12 | 512 x 512 Temperate | r16381 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
The original plan involving many twoway loops and lots of massive BBHs, combined with different trainspeeds and trainlengths proved to be too hard. We decided to get rid of the inner loop and seperate the pax and cargo network, in the end the map came out pretty well. |143|Image:PSG143.png| Showing an openttdcoop first: a full 5-way BBH.}}<br />
<br />
{{Archive_PublicServer|Public Server Game 142|15.05.09-23.05.09| {{User|tneo}}, {{User|Chris_booth}},| [[Gametype:Cargo_Concept|Cargo]] |TL 5 | 512 x 512 Temperate | r16341 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
The goal of the plan chosen was to have a high capacity network that worked with the map. We ended up with an LLLL_RRRR babcbone loop to which the other MLs were connected. |142|Image:PSG142.png| BBH02 is one of the 6 big BBHs in this game.}}<br />
<br />
{{Archive_PublicServer|Public Server Game 141|08.05.09-15.05.09| {{User|tneo}}, {{User|planetmaker}}, {{User|gleeb}}, {{User|uliko}}, {{User|ODM}}, {{User|Chris_booth}}, {{User|Combuster}}, | [[Gametype:Cargo_Concept|Cargo]] |TL 5 | 512 x 256 Sub-Tropical | r16277 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
This game featured a central hub station with an LL_RR leg to either side, trains picked up at both ends of the legs. After delivering their cargo trains were heading for the nearest depot to be refitted. This way train amount required was less then usual and trains mostly didn't travel empty.|141|Image:PSG141.png| An oil pickup station initally used for the MM.}}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=PublicServer:Archive_-_Games_141_-_150&diff=10234PublicServer:Archive - Games 141 - 1502009-06-16T16:03:04Z<p>Thraxian: Added PSG144</p>
<hr />
<div><noinclude>{{PublicServerArchiveMenu}}</noinclude><br />
<br />
{{Archive_PublicServer|Public Server Game 144|01.06.09-05.06.09| {{User|Thraxian}}, | [[Gametype:Cargo_Concept|Cargo]] | TL 5 | 512 x 512 Toyland | r16381 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
Intended to be a proof of the Davil-style hub (a recent blog article), this plan never really got off the ground. The loop was made too large, and later shrunk to a more manageable size. The Mainlines radiating from the loop were developed, but no industries (and consequently no trains) ever touched the network. In the end, the graphics proved to be too hard on the eyes and the game was scrapped in favor of a new climate. |144|Image:PSG144.png| Part of the 3-way Town Drop station}}<br />
<br />
{{Archive_PublicServer|Public Server Game 143|23.05.09-01.06.09| {{User|tneo}}, | [[Gametype:Cargo_Concept|Cargo]] & Pax | TL 8 & 12 | 512 x 512 Temperate | r16381 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
The original plan involving many twoway loops and lots of massive BBHs, combined with different trainspeeds and trainlengths proved to be too hard. We decided to get rid of the inner loop and seperate the pax and cargo network, in the end the map came out pretty well. |143|Image:PSG143.png| Showing an openttdcoop first: a full 5-way BBH.}}<br />
<br />
{{Archive_PublicServer|Public Server Game 142|15.05.09-23.05.09| {{User|tneo}}, {{User|Chris_booth}},| [[Gametype:Cargo_Concept|Cargo]] |TL 5 | 512 x 512 Temperate | r16341 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
The goal of the plan chosen was to have a high capacity network that worked with the map. We ended up with an LLLL_RRRR babcbone loop to which the other MLs were connected. |142|Image:PSG142.png| BBH02 is one of the 6 big BBHs in this game.}}<br />
<br />
{{Archive_PublicServer|Public Server Game 141|08.05.09-15.05.09| {{User|tneo}}, {{User|planetmaker}}, {{User|gleeb}}, {{User|uliko}}, {{User|ODM}}, {{User|Chris_booth}}, {{User|Combuster}}, | [[Gametype:Cargo_Concept|Cargo]] |TL 5 | 512 x 256 Sub-Tropical | r16277 [[GRF|#openttdcoop-GRF-Pack 7.3]]|<br />
This game featured a central hub station with an LL_RR leg to either side, trains picked up at both ends of the legs. After delivering their cargo trains were heading for the nearest depot to be refitted. This way train amount required was less then usual and trains mostly didn't travel empty.|141|Image:PSG141.png| An oil pickup station initally used for the MM.}}</div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:PSG144.png&diff=10233File:PSG144.png2009-06-16T15:55:55Z<p>Thraxian: </p>
<hr />
<div></div>Thraxianhttps://wiki.openttdcoop.org/index.php?title=File:PSG145.png&diff=10230File:PSG145.png2009-06-16T15:23:37Z<p>Thraxian: </p>
<hr />
<div></div>Thraxian