#openttdcoop wiki - User contributions [en]

Category:Gametypes

2010-07-19T19:50:07Z

Bodo Thiesen: someone forgot this one

===Why different gametypes?===
As a matter of fact, a human needs some variety in life. Our community started with the ambition to build huge cargo-related networks that start with transporting all coal on a map and move onward through all cargo types available. Since we did so many games (and yes, every game was different and great fun to play), we came to some more ideas in the area of passenger transportation etc.

=<center>Major gametypes at #openttdcoop</center>=

<center>
{| class="wikitable" style="border: 1px solid black;"
! Concept
! Freight
! Trainlength
! Connections
! Network Focus
|-
|[[Gametype:Cargo_Concept|The Cargo Concept]] ||Cargo||3-10||Multipoint to Point||Flow
|-
|[[Gametype:TGV_Concept|The TGV Concept]] || Passenger/Mail||8-12||Multipoint to Multipoint||Speed
|-
|[[Gametype:TGV_NG|The Next-Generation TGV]] ||Passenger/Mail||8-12||Multipoint to Multipoint||Speed
|-
|[[Gametype:Back_to_Basics|Back to the Basics]] ||All||4-5||Multipoint to Multipoint||Flow
|-
|[[Gametype:ICE_SBahn|ICE/S-Bahn]] ||Passenger||8-12 / 3-4||Multipoint to Multipoint||Speed
|-
|[[Gametype:Death_Feeder|The Death Feeder Concept]] ||Cargo||4-7 / 20||Multipoint to Point to Point ||Flow
|-
|[[Gametype:Progman_B2B|The Progman Back to Basic Concept]] ||Cargo||~5||Multipoint to Point||Flow
|-
|[[Gametype:Chaos_Theory|The Chaos Theory Concept]] ||Random||Random||Multipoint to MultiPoint||Random
|-
|[[Gametype:Eye _Candy|The Eye Candy Concept]] ||Random||Random||Multipoint to MultiPoint||Good looking
|-
|[[Gametype:Subsidiaries|The Holding & Subsidiaries Concept]] ||depends||depends||Multipoint to MultiPoint||Flow
|
|[[Gametype:Boost]] || ??? || ??? || ??? || ???
|}
</center>

Gametype:Subsidiaries

2010-07-19T19:49:13Z

Bodo Thiesen: +Category:Gametypes

The idea of this concept is to have different people (or groups thereof) manage different parts of the map with focus on different goods. These parts are connected via a transfer terminal with the ML where they exchange goods and are brought to their final destination.
It requires some kind of role-playing, some general manager to plan the ML layout and co-ordinate. Very well playable also with a track sharing patch.

This is untested yet but goes in the direction of wwottdgd.

[[Category:Gametypes]]

Cooperation

2010-07-19T19:15:51Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides|^^ Back to Guides-Index]]
----
This page will give you some basic ideas of the problems arising out of a game where many players are playing simultanously or delayed. This is a list that shows the aproach of #openttdcoop to optimize our corporation.

* Communication is the key point. Always say what your intention is. Check the console what has been said if you haven't been active some time (toggle the console with the key left to the "1", its the "^" on my keyboard or the "~" on the english one). If you connected a industry just tell your collegues so they can check it and advise you in case of a construction error. Here we are at the main advantage of cooperative gameplay: many eyes see more than just two and therefore errors in the network are less likely.

* Do not build on a construction site where another player is working on. This is a very nasty thing. You can imagine why.

* When you are building complicated stuff like hub or big station and you need time for thinking over it place a sign there. If you don't, someone can start building at the same place only because they wouldn't know you are building there.

* You can never be sure how many players are playing before or after your game session. Therefore, you have to transport your ideas with signs used to comment out certain spots or stations. This is compareable to comments on programming. Take care you do not overact this; too many signs won't get read. Furthermore, delete signs that became unimportant.

* The naming convention is very important to find the certain spots in a game. In our games we use to name every Mainline-Hub and Sideline-Hub in order they are built. Be sure to use '''exactly''' the notation used on the other Hubs (so it is ensured they are correctly sorted in the signlist).

* Writing your name to Hubs make it easy to contact a person and give advices how improve his buildings. Also, do not fear to be blamed for a mistake you made - ''errare humanum est!'' No one will ever be angry with you. Thats a key point of cooperation. Do not accuse other people but correct them. Do not try to cover your mistakes but make them public so all can learn from them.

----
[[Guides|^^ Back to Guides-Index]]
[[Category:Guides]]

Category:Guides

2010-07-19T19:15:21Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides|^^ Back to Guides-Index]]
----
All the building guides can be found here.

Planning

2010-07-19T19:14:15Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides|^^ Back to Guides-Index]]
----

Coordination is very important for cooperative gameplay since the goals and implementation tactics are meant to be shared among all participants. The planning stage of game is the time to lay a good foundation for prolonged and interesting gameplay, where the final result is achieved by combined activity of all players. Planning does take some skill and experience, and should be taken a serious task and with responsibility for future development. It should provide detailed description of what and how is to be achieved.

==Studying the map==
There is no basic "best strategy" for all situations. All games are very circumstantial, environment-dependent, and have different focuses. Even for targeted games, when a particular scenario or game preconditions are used, it still remains very open-ended and a successful result can be achieved by many ways. Thus, it is very important to explore the map and foresee future development and implementation, ensuring that it is possible to achieve the goals that are set. Some layouts are only applicable to certain cases and various types of networks deal with landscape in different fashions. It is very important to keep in mind that it is not that landscape is to be altered to fit the idea of the plan, but vice versa—the plan must adhere to circumstances.

==Defining main elements==
All plans have certain main elements which predefine the plan's foundation.

These are:
; Game type : Global [[:Category:Gametypes]] (i.e.: ''raw cargo'', ''TGV global pax game'', ''ICE/S-Bahn'', etc.)
; Goals/focus : Narrowing down the type to a particular point (i.e.: ''flow'/capacity', ''speed'', ''second tier saturation'', ''connecting something'', etc.)
; Network type : Basic rules, describing type of lines used (perhaps: ''plain'', ''segregated'', ''distributed'', ''shifting'' ) and track width, along with details (such as: ''prioritised 2nd tier', ''none blocking mergers only'', ''expandable to ...'' etc.)
; Network layout : That controls shape of lines and defined by major stations' requirements. Should be done in some illustrated form or shape, providing enough details to show key points of particular layout.
; Perks : anything what is out of ordinary and not generally applicable to described conditions (i.e.: ''steam only'', ''no terraforming'', ''avoid coal'', ''save all trees'')

==Sharing ideas==
It is possible that there are already plans being discussed or that some are made, in which case it would make sense to comprehend them and understand key elements and differences. Presenting many plans with differences only in directions of tracks or train length used is quite pointless. It would be better to discuss with the author possible changes and make corrections to the existing plan if they are considered as useful after coming to consensus. Plans as well as the game itself can be result of collaboration and shaping the ideas based on experience of different players. However, please make sure to suggest changes rather than insist upon them.

==Planning==
Usually, there is a remote spot on the map somewhere with sign " !!NETWORK PLANS" next to it. This is designated for laying out proposed plans. If there is no area marked in this way, feel free to create one. Bear in mind that plans are meant to last the whole game and selecting densely populated areas makes very little sense; typically remote areas such as corners and edges of map, with even or gently rolling terrain are the best spots.

When creating a plan, allocate yourself enough space and try not to interfere with other people's work. Make sure to state as many details as possible to make the plan clear for others (separation between primary/secondary, type of network and width, train lengths etc.). Major elements design can also be noted in case if it is not clear from visual layout. Make sure the plan is comprehensive and covers all/most game aspects. Don't forget to title and sign it, as well as to add it to voting board if one is there already.

After the core of your plan is done, listen for critique and constructive comments, be patient for more plans to appear, and wait until voting is finished. It is quite common for the planning phase to take a long time simply because of different people's schedules and other limitations.

==Understanding complexity==
As an author of a plan you are responsible for covering many aspects in design and location of key elements (be it a hub station or the location of a drop). A good plan should present an opportunity for many players to have their input useful for achieving the goal. It should not be overly complex or simply impossible but have various challenges for a variety of skill levels. It should also withstand the test of time. In many cases planned expandability saves the day by turning tedious upgrades into a set of doable tasks with little to no interference to the existing network.

==Implementation==
In case if you plan is chosen (and that is bound to happen sometime), as author, you are encouraged to provide as much help as possible to execute the plan. The creator of the selected plan takes a guiding role of chief engineer, answering questions and being a source of wisdom when unforeseen challenges arise.

It greatly helps for proper implementation to have predefined locations for major nodes of the network as well as other important elements. Selecting placement for these, by putting signs in desired places, essentially charts the map to meet the plan's requirements. Being the author does not mean that it is totally up to you to create the whole network, but playing a key role in creation process is expected. At the same time let others help you to "get there:" it will be faster and more entertaining as the joint effort of many—that's what #openttdcoop is about, after all!

==Modification and corrections==
As time goes, it is quite possible that a need for reform or alteration is required due to change in environment, implementation limitations or unforeseen roadblocks. In the event that such drawbacks are observed, it is imperative to quickly react and modify the plan to satisfy new needs. Along with being ''proactive'' and trying to ensure the future of the game, authors should also try to be ''reactive'' to ongoing development. Other players can provide valuable input which can ease extreme challenges and help avoid known pitfalls. Sometimes there are several approaches that can be taken and it is up to author to consider alternatives and make wise choices and introduce corrections to the plan.

==Examples==
{|
|| [[Image:plan4.png|thumb|center|320px|]] || [[Image:plan1.png|thumb|center|320px|]]
|-
|| [[Image:plan2.png|thumb|center|320px|]] || [[Image:plan3.png|thumb|center|320px|]]
|-
|| [[Image:plan0.png|thumb|center|320px|]] || [[Image:plan5.png|thumb|center|320px|]]
|-
|| [[Image:plan6.png|thumb|center|320px|]] || [[Image:plan7.png|thumb|center|320px|]]
|-
|| [[Image:plan8.png|thumb|center|320px|]] || [[Image:plan9.png|thumb|center|320px|]]
|}

----
[[Guides|^^ Back to Guides-Index]]
[[Category:Guides]]

Game Start with Trains

2010-07-19T19:10:19Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Game_Start|^^ Back to Game Start Guide-Index]] | [[Game_Start_with_Airplanes|Game Start using Airplanes >>]]
----

{{obsolete||Game Start with Airplanes}}

== Game Start ==
When first beginning a new game, on a fresh map, there are a few VERY important things to remember.

* Cargo
* Distance
* Signals
* Terraforming
* Trains

Alternatively [[Game_Start_with_Airplanes|starting with airplanes]] instead of trains can be done.

== Cargo ==
The first type of cargo that should be transported in a new game is coal. It has the best distance/earnings ratio of any cargo. That means, the farther you take it, the more you earn!

[[Image:Payment.png|thumb|564px|center|Example]]

== Distance ==
Find a power station near a corner of the map with preferably 2-4 mines within decent reach. Build a simple Ro-Ro station, 3 or 4 tracks is all that will be needed; connect this station to a coal mine about 100 tiles away (The normal COOP map is 256x1024, so about half the shorter length) with smart track laying you should be able to build the stations and track for around 150,000e. It also helps to use a single track line with passing areas for very distant connections, as seen here:

[[Image:SingleLine.png|thumb|610px|center|Example]]

== Signals ==
Our network rules state that there should be a signal every other tile. During a game start this is lunacy and a HUGE waste of money, most of the track you are building will be destroyed later in the game, and will have very few trains running on it to boot. A signal every 20 tiles is sufficient.

== Terraforming ==
If at all possible, go around anything in your way, rather than moving it. 2x45 degree turns are not as bad in the game start as they are in our final network. Most trains in early game will not even slow down around a 2x45 degree curve! Bridges are cheap and tend to be faster than just laying tracks down a valley, if possible use a bridge!

== Trains ==
You can go with either electric rail, or regular, but since the costs for erail are the same, you have to stick to electrified rail by default. The steam engines will have similar top speed, half the HP (only bad point) but cost about a third of an electric engine.

[[Image:SteamvsElec.png|thumb|500px|center|Example]]

----
[[Game_Start|^^ Back to Game Start Guide-Index]] | [[Game_Start_with_Airplanes|Game Start using Airplanes >>]]
[[Category:Guides]]

Game Start with Airplanes

2010-07-19T19:10:16Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Game_Start_with_Trains|<< Game Start using Trains]] | [[Game_Start|^^ Back to Game Start Guide-Index]]
----

{{reqscreenshot|Ideal placements}}
== Game Start with Airplanes ==

An alternative to transporting coal with trains as the moneymaker at game start is to use airplanes to transport passengers and mail. There are several advantages to using airplanes instead of trains:
*No track to construct
*Constructing airports great distances apart costs no more than constructing them nearby
*Airplanes can transport their cargo faster than trains can
*Avoids having production at coal mines swell before the final network is constructed

== Choosing Towns for the Airports ==

Care must be taken when choosing towns to build moneymaker airports in. Under ideal conditions, the best candidates are larger towns in opposite corners of the map. The larger the town, the more passengers that will be supplied. The farther the distance, the greater the earnings per trip. Other factors such as available space should be considered as well. A large town on a small island or in mountainous terrain is a poor choice for a moneymaker airport as teraforming will be required to create a large enough piece of land to build the airport on. Also since farmland has a greater cost to build on top of, it may be wise to build away from farms. Always remember to communicate with your fellow coop players about where to build moneymaker airports. Without communication we could end up with two players building two airports in the same city, an unnecessary expense at the only time in the game when money is tight. Start with two airports, often times this will be expanded to four as income becomes steady.

== Building the Airports ==
Once towns have been chosen, build the airports as close to the town as possible. Avoid demolishing town buildings and avoid teraforming as much as possible. Use drive through road stops to walk the station to the town center to increase catchment area. This practice in generally discouraged in most final networks, but works well for moneymakers. Even small airports works well as it doesn't take large numbers of airplanes to generate the required income. Always remember to communicate with your fellow coop players about where to build moneymaker airports. Without communication we could end up with two players building two airports in the same city, an unnecessary expense at the only time in the game when money is tight. Rename the airports to "MM01, MM02, etc".

== Buying the Airplanes ==
When choosing airplanes for the moneymaker, a balance needs to be struck between cargo capacity, running costs, and speed. As we commonly use different planesets each game, this is a decision to be made as a community. It is also important not to buy too many planes to begin with. If we spend all our money before the first plane reaches it's destination, we could end up going bankrupt. Building additional planes should be handled by a single player to avoid confusion. As always keep one unit of loan on reserve, ready to be taken if money goes into the red at any time. In these circumstances when the full loan is taken, the top priority is ALWAYS to repay at least one loan unit. This is more important than purchasing new airplanes or airports.

== Town Growth ==
A side effect of airplane moneymakers is that it can cause towns to grow. This should be avoided as larger towns could get in the way of the final network. There are two ways to prevent town growth. The first is to set town growth in the advanced settings / economy tab to "none". This can only be done by members, so ask if you notice that town growth is on. The second involves buying land adjacent to the city to block growth, or in some cases restrict growth to a certain size by buying land a few tiles away from the city to allow for growth to increase moneymaker profits through more passengers. That decision should be made by the community, and made known via signs for players who are not online at that moment. Purchasing of town land should be done after income has stabilized to avoid bankruptcy.

== Completion of the Moneymaker ==
Once income has stabilized and the loan has been repaid, the moneymaker stage of the game is finished, and the planning stage begins. The moneymaker will continue to earn money until the final network is planned, chosen, built, and begins making money itself. At this point the moneymaker is generally dismantled as it it no longer needed.

== Communication is Vital ==
At game start there are generally a lot of players connected waiting to create a plan for the final network. You are welcome to help build the moneymaker, but please remember to use the in-game chat to communicate with the other players. Without communication, several players could end up trying to do the same thing, and this can lead to confusion and wasting money at the only time when we need to be worried about cash levels. Please be patient about creating your plan.

----
[[Game_Start_with_Trains|<< Game Start using Trains]] | [[Game_Start|^^ Back to Game Start Guide-Index]]
[[Category:Guides]]

Game Start

2010-07-19T19:07:15Z

Bodo Thiesen:

[[Tutorial_Savegame|<< Tutorial Savegame]] | [[Guides|^^ Back to Guides-Index]] | [[Planning|Planning-Index >>]]
----

== Game Start ==

=== Game Start with Trains ===

In previous games, we booted games using Trains. It remains here as documentation for games, whose starting year doesn't allow building arplanes and hence make the new approach impossible.

[[Game_Start_with_Trains]]

=== Game Start withAirplanes ===

The new and current approach to boot games in #openttdcoop is to use Airplanes. It's the recommended way to boot a game.

[[Game Start with Airplanes]]

----
[[Tutorial_Savegame|<< Tutorial Savegame]] | [[Guides|^^ Back to Guides-Index]] | [[Planning|Planning-Index >>]]
[[Category:Guides]]

Game Start

2010-07-19T19:05:47Z

Bodo Thiesen: Moved content of Game Start to Game Start with Trains

== Game Start ==

=== Game Start with Trains ===

In previous games, we booted games using Trains. It remains here as documentation for games, whose starting year doesn't allow building arplanes and hence make the new approach impossible.

[[Game_Start_with_Trains]]

=== Game Start withAirplanes ===

The new and current approach to boot games in #openttdcoop is to use Airplanes. It's the recommended way to boot a game.

[[Game Start with Airplanes]]

Game Start with Trains

2010-07-19T19:01:03Z

Bodo Thiesen: Moved content of Game Start to Game Start with Trains

{{obsolete||Game Start with Airplanes}}

== Game Start ==
When first beginning a new game, on a fresh map, there are a few VERY important things to remember.

* Cargo
* Distance
* Signals
* Terraforming
* Trains

Alternatively [[Game_Start_with_Airplanes|starting with airplanes]] instead of trains can be done.

== Cargo ==
The first type of cargo that should be transported in a new game is coal. It has the best distance/earnings ratio of any cargo. That means, the farther you take it, the more you earn!

[[Image:Payment.png|thumb|564px|center|Example]]

== Distance ==
Find a power station near a corner of the map with preferably 2-4 mines within decent reach. Build a simple Ro-Ro station, 3 or 4 tracks is all that will be needed; connect this station to a coal mine about 100 tiles away (The normal COOP map is 256x1024, so about half the shorter length) with smart track laying you should be able to build the stations and track for around 150,000e. It also helps to use a single track line with passing areas for very distant connections, as seen here:

[[Image:SingleLine.png|thumb|610px|center|Example]]

== Signals ==
Our network rules state that there should be a signal every other tile. During a game start this is lunacy and a HUGE waste of money, most of the track you are building will be destroyed later in the game, and will have very few trains running on it to boot. A signal every 20 tiles is sufficient.

== Terraforming ==
If at all possible, go around anything in your way, rather than moving it. 2x45 degree turns are not as bad in the game start as they are in our final network. Most trains in early game will not even slow down around a 2x45 degree curve! Bridges are cheap and tend to be faster than just laying tracks down a valley, if possible use a bridge!

== Trains ==
You can go with either electric rail, or regular, but since the costs for erail are the same, you have to stick to electrified rail by default. The steam engines will have similar top speed, half the HP (only bad point) but cost about a third of an electric engine.

[[Image:SteamvsElec.png|thumb|500px|center|Example]]
[[Category:Guides]]

Tutorial Savegame

2010-07-19T16:43:54Z

Bodo Thiesen: interwiki linkfix

{{TutorialSavegameMenu|Guides|<< Back to Guides|Tutorial Savegame Mainline|1.x Mainline >>|Tutorial Savegame}}
__NOTOC__
=<center>The #openttdcoop Tutorial Savegame</center>=

After some 2+ years of #openttdcoop we felt like we had to do a compilation of key points from our games. Some of our well-known guides are a nice peek into the world of #openttdcoop but by any means not enough to tell our readers WHY we build weird structures such as [[Balancing|Load Balancers]] or [[Sideline Hub|Sideline Hubs]]. Most important in order to understand these constructs is seeing them in action. As a result of our considerations we hereby supply a '''tutorial savegame''' to every interested reader.

Please retrieve the [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav '''tutorial savegame'''] ([[:Image:Tutorial.sav|page]])

''Technical Note: the savegame should work on OpenTTD 0.6.3 or the latest nightly builds. Get the latest nightly build or OpenTTD 0.6.3 (or newer) to load the savegame.''

==How to use this savegame==
[[Image:Signlist.png|355px|thumb|right|Open your signlist]]
Open the signlist. The signlist is probably the most important feature of OpenTTD to our community since we are using signs a lot to guide people around and mark points of interest. Cooperative play is very much about communication, and the signlist allows us to more easily communicate spatially. If you click on a sign in the list, the client directs you straight to this point. We classified the topics within the tutorial in five headers:

# [[Tutorial Savegame Mainline]]
# [[Tutorial Savegame Sideline]]
# [[Tutorial Savegame Stations]]
# [[Tutorial Savegame Feeder]]
# [[Tutorial Savegame Towns]]

With reference to these signs in the game, we dedicate the next pages to explain our ideas with the relevant constructs and concepts. We try to give you an idea of our thinking: in the end you'll be through a crash course straight into the core principles of network building in #openttdcoop.

If you feel impressed by a lot of signaling and lots of traffic, don't hesitate joining our [[Public Server]]. It's not that difficult as one could expect. You can just watch for a while if you wish. As you gain confidence and experience, you will learn to build parts of the cooperative network of increasing complexity. Other players can help you with what you build and tell you what you've done correctly and incorrectly. This '''tutorial savegame''' is just a good point to start at—we'll teach you the basics so you know what's going on.

'''A last suggestion to our readers: in case of questions or comments please use the discussion pages!'''

{{TutorialSavegameMenu|Guides|<< Back to Guides|Tutorial Savegame Mainline|1.x Mainline >>|Tutorial Savegame}}

[[Category:Guides]]

Dodging unremovables

2010-07-19T16:33:17Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Removing_a_city|<< Removing a city]] | [[Guides:Altering|^^ Back to Altering Guides Index]]
----

When building Line's it's unavoidable that you will encounter at some point an Un-Removable object such as an Antenna. There are multiple ways to avoid these and some are more effective than others. Here are a few examples:

== Going Around ==

Going around is a simple and efficient way as long as the line is not too wide and the turns aren't too short. The curve around must be wide enough that trains do not slow down from encountering a tight turn, we call this curve length, or CL for short. The curve must also not force trains to change direction more than two times in the tile length, or TL for short, of the trains. Here is an example of a track curving around a transmitter antenna:

[[Image:dodge-around.png]]

== Going under ==

Going under is just as simple. Dig 2 hole's and place tunnels. Of course tunnels can't be signaled so for busy line's Multiple tunnels for every track could be required. Here is an example of a track using double tunnels to go under a power station, notice the track is offset on either side so the path through either tunnel is the same length, 7 straight tiles and two diagonal:

[[Image:dodge-under.png]]

----
[[Removing_a_city|<< Removing a city]] | [[Guides:Altering|^^ Back to Altering Guides Index]]
[[Category:Guides]]

Removing a city

2010-07-19T16:32:45Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides:Altering|^^ Back to Altering Guides Index]] | [[Dodging_unremovables|Dodging unremovables >>]]
----

Sometimes when building the main line, side line or a station you come across some towns. Sometimes you have to remove them so there is more room for our networks. (Please note that this isn't cheap and only perform this when there enough money. Otherwise place a sign and wait until there is more money).

Removing is done in several steps:

==== Removing the first buildings ====
First check the rating of the authorities of the town. If it's '''Very Good''' or better start with removing some buildings like a football station, church or offices. These all need a rating of Very good or better. Removing a simple houses will be done later. Repeat the process until the rating drops to '''Appaling''', then move on to the next step.

If you don't know which kind of building everything is, use the "Land area information tool". It's the last button in the topside buttons bar (with pause, settings, save, map etc.). If you still don't know if a building can only be removed with Very good rating or higher start with the buildings that look the most expensive.

==== Planting trees ====
You've been removing quite a bit and your rating has dropped to Appaling and local authorities will not allow further demolition. It's time to raise the town rating.
Remove everything in between a range of about 10 to 20 tiles from the town center (mind any laid out tracks, stations or purchased land). When you've removed everything from these tiles plant trees on the bare tiles. Just one tree per tile is enough (only drag and drop once). Repeat this until you have reached a '''Good''' or higher town rating and continue with the next step. Do not use the bribe option, which is expensive and will lead to being discovered and an unwilling town.

==== Removing some (cheap) buildings ====
Now that your rating is increased to '''Good''' or better it is again time to remove buildings and roads. Start with removing houses at first and when that is not possible anymore try removing some roads. It appears that you can demolish up to 7/ 8 road pieces or 2 houses + 1 road tile at a time. When the town rating has dropped to '''Appaling''' again repeat the tree planting step. Do so until there are only buildings left that can't be removed (statues for instance).

==== Removing the last buildings ====
If it wasn't a very big town, the result you have now must be only a few buildings left. Now it's time for the expensive part: '''Bribing'''. To save money, make sure your rating now is '''Good''' and if it is not the case plant some trees. Bribe to get an excellent or outstanding rating and remove the final buildings. If your ratings has dropped again try to increase it first by planting trees otherwise attempt another bribe. Now the town is removed completely. If town growth is turned on purchase the tiles around the center to prevent future growth, a rectangle of 10 by 10 tiles will do.

----
[[Guides:Altering|^^ Back to Altering Guides Index]] | [[Dodging_unremovables|Dodging unremovables >>]]
[[Category:Guides]]

Guides:Altering

2010-07-19T16:28:57Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides:Presignals|<< Presignals-Index]] | [[Guides|^^ Back to Guides-Index]] | [[Tutorial_Savegame|Tutorial Savegame >>]]
----

=<center>Altering the world around you</center>=

==Part 1: Removing a city==
Sometimes cities get in the way of building a [[Mainline|mainline]] or something else. Here's how to get rid of it.

[[Removing a city]]

==Part 2: Dodging unremovables==
Often times antennaes on top of mountains, lighthouses on the shore, or just an industry in the wrong spot get in the way. The ways to get around this are explained here.

[[Dodging unremovables]]

----
[[Guides:Presignals|<< Presignals-Index]] | [[Guides|^^ Back to Guides-Index]] | [[Tutorial_Savegame|Tutorial Savegame >>]]
[[Category:Guides]]

Guides:Presignals

2010-07-19T16:25:53Z

Bodo Thiesen: /* Part 5: Complex Junctions */ fixed and/or improved inter guides linking

[[Guides:Building|<< Building-Index]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Altering|Altering-Index >>]]
----

=A Presignal Guide=
(under construction)
A guide for newbies, about presignals. However, this is not only for beginners as there are many complex things concerning presignals. If you know how the presignals work, you should skip the "basics" Part.

==Part 1: Basics==
The Presignal Basics is explained here: how they work, how they behave, and how does a terminal station work, and what's the use of the combo presignal.

[[Presignal Basics]]

==Part 2: Oneway or twoway Presignals==
Signals have two sides. In the basics part, the other side wasn`t important, since trains can`t turn back, etc. However, in more complex situations, a badly placed two way Combo Presignal can cause errors in your network.

[[Oneway or Twoway Presignals]]

==Part 3: Priorities==
When you have to connect two tracks into one, the most used track should have more priority than the lesser-used track.
In this Part, junctions with priority are shown.

[[Priorities]]

==Part 4: Load Balancers==
How to make presignals on a Load Balancer.

[[Balancing|Load Balancers]]

==Part 5: Complex Junctions==

[[Complex Junctions]]


----
[[Guides:Building|<< Building-Index]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Altering|Altering-Index >>]]
[[Category:Guides]]

Balancing

2010-07-19T16:22:24Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Priority|<< Priority]] | [[Guides:Presignals|^^ Back to Presignals Guides Index]] | Complex Junctions
----

In our networks we often have lots of tracks that want to join to other lots of tracks. Often the load on the tracks is unequal, so you want to provide incoming tracks with the choice to pick any outgoing line, otherwise you might end up having pretty much empty lines joining to other pretty much empty lines and full lines trying to join to other full lines. The first is obviously fine but you can see the latter might be problematic. Enter: balancing.

Let us clear out some misunderstandings first.

:''"The goal you want to achieve by balancing is to have equal loads on every track."''

This is not true. Mainlines are built for 100% capacity so it's not a problem when you have a two-track mainline with one track that is 40% loaded and one that is 90% loaded. The problem emerges when you try to join a 70% loaded track to an 80% loaded track.

:''"I don't have to balance this join, traffic is already balanced."''

The point I made before also shows this assumption is wrong; balancing is ''not'' about achieving equal loads. This is also why constructions such as the one below are completely pointless.
[[File:inline_balancing.PNG|400px|thumb|none|Inline balancing. Pointless and bound to cause problems once you get dense traffic running]]

==Balancing in text==
If you want to describe what kind of merge you're talking about, use this format:
:Amount of original tracks + Amount of incoming tracks -> Amount of outgoing tracks
So if you'd have a sideline joining a two-track mainline, you'd have 2+1->2.

So much for the theory, let's get building.

== Single-track to single-track: 1+1->1==
Of course this is not actual balancing; there is only one outgoing track so you can't provide choice. If you do want to have some control you could add a simple [[priority|priority]] line. Or if you're feeling really adventurous you could even throw in a [[compressor|compressor]]
Now let's move on to some more relevant stuff.

==Single-track to multi-track: 2+1->2==
This is a situation you'll often come across in our games; a sideline joining a mainline at a sideline hub. This is also pretty straight forward, you just want the sideline to be able to pick from every mainline. A potential issue when you start joining to multiple tracks is blocking.
Blocking happens when the block between the mainline and the joining line is not large enough to hold an entire train and a mainline train enters the priority section while a train is joining, which then gets stopped and also blocks other trains trying to join. Got that? The image below shows a blocked train.

[[File:Block.PNG|400px|thumb|none|A train that got blocked while joining]]

The solution to this is to eliminate the combo signal, meaning you want every block to be able to hold at least one train.

[[File:noblock.PNG|400px|thumb|none|Non-blocking 2+1->1 join.]]

It's pretty easy to repeat this process when you have more than 2 original tracks.

[[File:4_1_4.PNG|400px|thumb|none|A 4+1->4 balanced merge]]

==Multi-track to multi-track: 2+2->2==
This is where it gets interesting. These kinds of joins usually occur at backbone hubs and main station hubs. The easy way to balance these is to just repeat the single-track to multi-track merge for every incoming track, as seen below.

[[File:ugly.PNG|400px|thumb|none|A 2+2->2 join that actually consists of a dual 2+2->1 join]]

There is however an issue with this approach. The track that joins first has an advantage over the later joins, because the later joins also have to cope with the added load added by trains joining from the merges before. When you use this technique for larger joins the problem becomes bigger too:

[[File:even_uglier.PNG|400px|thumb|none|Showing ProZone Game 05's massive 8+8->8 join, joins like these magnify the problem described above]]

This can be solved by adding a cross allowing trains to switch the joining track, as you can see below:
n[[File:crossjoin.PNG|400px|thumb|none|A 2+2->2 join using a cross to allow trains to switch, non-blocking, of course]]

[[File:crossjoin_full.PNG|400px|thumb|none|The same join, with trains occupying the reserved blocks]]

This cross-joining style can be used for wider tracks relatively easily:

[[File:snowycross.PNG|400px|thumb|none|Showing a 3+2->3 merge in Public Server Game 146]]

==Priorities on BBHs==
It is often said that priorities are not needed an BBHs, because the loads have equal priority anyway. Priorities on backbone hubs, however, don't actually serve the purpose of giving priority; they are only there to disrupt ML traffic as little as possible. Often the priorities are nowhere near long enough to allow for full acceleration, unlike those at SLHs, and it's no problem to shorten them if the joining track seems to be jamming because of the long prios.

----
[[Priority|<< Priority]] | [[Guides:Presignals|^^ Back to Presignals Guides Index]] | Complex Junctions
[[Category:Guides]]
[[Category:Advanced Networking]]

Priority

2010-07-19T16:18:50Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Oneway_or_Twoway_Presignals|<< Oneway or Twoway Presignals]] | [[Guides:Presignals|^^ Back to Presignals Guides Index]] | [[Balancing|Balancing >>]]
----

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

----
[[Oneway_or_Twoway_Presignals|<< Oneway or Twoway Presignals]] | [[Guides:Presignals|^^ Back to Presignals Guides Index]] | [[Balancing|Balancing >>]]
[[Category:Guides]]

Oneway or Twoway Presignals

2010-07-19T16:17:24Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Presignal_Basics|<< Presignal Basics]] | [[Guides:Presignals|^^ Back to Presignals Guides Index]] | [[Priority|Priority >>]]
----

=<center>Oneway or Twoway Presignals?</center>=
Signals have two sides, in the basics part, the other side wasn`t important, since trains can`t turn back, etc. etc... But in more complex things, a badly placed twoway Combo Presignal can make errors in your network.

==Part 1: The Station entrance problem with two entries==
[[Image:Twoentry.PNG|thumb|center|370px|A RoRo station with two Entries]]
In this station the combo presignal can make errors, but can you notice why? If F-H presignals are green then Combo presignal C´s upper-right side is green too. Then if D and E exit Presignals, is red, then A Entry presignal remains green. The problem´s source is: Presignals calculates Signal Blocks, not the Possible chosable tracks: from A trough C and reach F-H platforms is impossible, but presignals CAN see this!
[[Image:Twoentry2.PNG|thumb|center|375px|The Error: Signal A remains green]]
How to fix this? Just change the Combo Presignal C to oneway or add an oneway Combo Presignal after it, like in the next picture:
[[Image:Twoentry3.PNG|thumb|center|373px|Now an Oneway Combo Presignal are added after it]]
With this Entry Presignal A cant look for Platforms F-H.

----
[[Presignal_Basics|<< Presignal Basics]] | [[Guides:Presignals|^^ Back to Presignals Guides Index]] | [[Priority|Priority >>]]
[[Category:Guides]]

Presignal Basics

2010-07-19T16:14:52Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides:Presignals|^^ Back to Presignals Guides Index]] | [[Oneway_or_Twoway_Presignals|Oneway or Twoway Presignals >>]]
----

=<center>Presignal Basics</center>=
The Presignal Basics is explained here: how they work, how they behave, and how does work a terminal station, and whats the use of the combo presignal.

==Part 1: Identify the signals==
There are six types of signals in OTTD. If you click on a normal signal with CTRL is held, these signals will appear:

'''Normal Signal''': It does not have any special alibity, it turns to red if the next signal block is blocked by any train.

'''Entry Presignal''': It works like a normal signal, plus it turns to red if all exit presignals, or combo presignals are red after it.

'''Exit Presignal''': It works same as normal signal, but it signs for the entry, or combo signals, if self is red.

'''Combo Presignal''': It has both Entry and Exit presignal alibities: It turns to red if all Exit/Combo are red after it, and it signs for the Entry/Combo Presignals, if the self is red.

'''PBS Signal ''': Not a Presignal, it enables more trains in one signal block, since PBS means Path Based Signaling. This type of signal is not explained here.

'''One-Way PBS Signal ''': It works like a PBS Signal, however, it prohibits passing through from the back side. This type of signal is not explained here.

[[Image:Signals_revised.png|thumb|center|388px|Different signal types]]

==Part 2: The Station Problem==
Stations without any presignals have a big problem: just have a look on the Image to the below. Signal A should be red...[[Image:Terminal1.png|270px|center|thumb|Problem at stations without Presignals]]
If you let one more train to enter into the station, it will block the exit, because A signal is green. This problem is solvable with presignals: Just turn A into Entry presignal, and turn B and C signals to exit signals. [[Image:Terminal2.png|276px|center|thumb|Station with Presignals]] How does it work? If Exit Presignals B, C are both red, then Entry Presignal A is red too. Then a third train cannot pass trough Signal A.

==Part 3: An Effective RoRo station==
Combo Presignals are mostly placed between Entry, and Exit presignals, because the Combo Presignals transmits the Exit presignal signs for the Entry Presignals. Combo presignals behave as an entry presignal and an exit presignal both.[[Image:RORO1.png|center|thumb|526px|RORO station]] In the Image above, signal A is Entry Presignal, signals B, C, D, E are Combo ones, and F-K are Exit Presignals.

If F and G Platforms are used, then Combo signal B uses its Entry Presignal alibity, and it will turn to red, because F, and G Exit Presignals are both red. But the Entry Presignal A is remains green. Exit presignals H-K are green, then Combo Presignals D, E is green, then Signal C is green too. With this Combo Presignal B is red and C is green, then the Entry Presignal A is remains green.[[Image:RORO2.png|center|thumb|526px|The Entry remains green]]

The Entry Presignal A will be red only, if all Platforms are used, Exit Presignals F-K are red. If F-K are red, then all Combo Presignals B-E are red too, then the Entry A will be red.[[Image:RORO3.png|center|thumb|520px|All Platforms red]]

----
[[Guides:Presignals|^^ Back to Presignals Guides Index]] | [[Oneway_or_Twoway_Presignals|Oneway or Twoway Presignals >>]]
[[Category:Guides]]

Guides:Presignals

2010-07-19T16:11:40Z

Bodo Thiesen: fixed and/or improved inter guides linking

[[Guides:Building|<< Building-Index]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Altering|Altering-Index >>]]
----

=A Presignal Guide=
(under construction)
A guide for newbies, about presignals. However, this is not only for beginners as there are many complex things concerning presignals. If you know how the presignals work, you should skip the "basics" Part.

==Part 1: Basics==
The Presignal Basics is explained here: how they work, how they behave, and how does a terminal station work, and what's the use of the combo presignal.

[[Presignal Basics]]

==Part 2: Oneway or twoway Presignals==
Signals have two sides. In the basics part, the other side wasn`t important, since trains can`t turn back, etc. However, in more complex situations, a badly placed two way Combo Presignal can cause errors in your network.

[[Oneway or Twoway Presignals]]

==Part 3: Priorities==
When you have to connect two tracks into one, the most used track should have more priority than the lesser-used track.
In this Part, junctions with priority are shown.

[[Priorities]]

==Part 4: Load Balancers==
How to make presignals on a Load Balancer.

[[Balancing|Load Balancers]]

==Part 5: Complex Junctions==

[[Complex Junctions]]

----
[[Guides:Building|<< Building-Index]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Altering|Altering-Index >>]]
[[Category:Guides]]

Guides:Glossary

2010-07-19T16:08:33Z

Bodo Thiesen: fixed and/or improved inter guides linking

Guides:Building

2010-07-19T16:06:59Z

Bodo Thiesen: fixed and improved inter guides linking

[[Guides:Glossary|<< Glossary]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Presignals|Presignals-Index >>]]
----

=<center>An illustrated guide to proper building</center>=
To help our new members and for reference, we have written a number of guides that will help you to understand how our games work. It is recommended that you read them in the order listed below.

==Part 1: Basic Stations==
First, we will start building a simple station. Before we start we want to make clear that our construction style is expandable in the future. Therefore, we construct huge mainlines and connect sidelines to this mainlines. Stations are ALWAYS connected to sidelines.

[[Sideline stations]]

==Part 2: Basic Junctions==
In this part we build the first junction (in #openttdcoop we always call it "hub"). Since we always build multi-track-junctions, a junction is a bit more complicated than it seems at first. Since we want to build efficient and fast railway networks, we need efficient and fast junctions as well. For the start we will analyse a so-called "Side Line Hub" (or "SLH" for short).

[[Basic Junctions]]

==Part 3: Mainline Junctions==
After building the first hubs in part 2, you will probably notice that our mainlines may sometimes cross each other. Since we always build a comprehensive network and always avoid dead-end lines, there is a point in the game where a so-called "Backbone Hub" is needed.

[[Mainline Junctions]]

==Part 4: Networking==
After being able to build all this nice little hubs we return to some basics. Actually we demand you to do something very important before you start to build: just think about what you are doing. In the ruleset you probably read about our intention to build a comprehensive network. In a typical 512*512 game we have developed a certain networking-style.

[[Networking]]

==Part 5: Trains==
Trains are a sensible part of OTTD. On this page, we just intend to make some short statements that help you building them for large networks like #openttdcoop's.

[[Trains]]

==Part 6: Orders==
After you built the first trains, you have to think about that. You'll find some guidelines on feeders here as well.

[[Orders]]

==Part 7: How not to build a network==
This guide is purely to show what happens when all the coop rules on building are blatantly ignored.

[[How not to build]]

----
[[Guides:Glossary|<< Glossary]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Presignals|Presignals-Index >>]]
[[Category:Guides]]

How not to build

2010-07-19T16:06:00Z

Bodo Thiesen: fixed and improved inter guides linking

[[Orders|<< Orders]] | [[Guides:Building|^^ Back to Building Guides Index]]
----

===How '''''not''''' to build...===

Ok, so by now you've been told how to build in our games. We haven't settled on that building method for no reason. In here I'm going to explain you why, using an old game I made together with a friend of mine (it's quite old and worked reasonably at the time, however now it doesn't).

Start out with loading [[Media:Magnetic_Corp.%2C_30th_Dec_2090_CLI.sav]].

''With newer revisions the game will not run, if you have any newgrf's enabled. Disable them if you want to see the game in action.'''

Now, I'll explain what's wrong with it:
* There is a jammed roundabout in there. It will keep jamming over, and over again.
* There are a multitude of 2x45 degree turns in there and even some 90 degree turns, the resulting congestion is disastrous to the efficiency of the network as most trains slow down to a crawl to get through the bends.
* No use of pre-signals, even where they should be used. Result: congestion and inefficient use of the stations which need it.
* Huge switches in front of stations. Most of those stations aren't even RoRo! Result: a ''lot'' of congestion.
* Huge stations which see lots of traffic... without proper load-balancing. The result: a huge queue of trains, which have to wait for a single train to enter the station.
* There are some junctions which are too tight. Result: waiting trains to go over it. This might cause a mild seizure to the network.

----
[[Orders|<< Orders]] | [[Guides:Building|^^ Back to Building Guides Index]]
[[Category:Guides]]

Orders

2010-07-19T16:04:29Z

Bodo Thiesen: improved inter guides linking

[[Trains|<< Trains]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[How not to build|How not to build >>]]
----

Orders make our networks work, they are what keeps our network alive, the cash flowing and prevent jams. Without proper order setup the trains won't go to the correct destination and won't be able to make money. This guide will lead you through the basics of giving orders and will also show you some more advanced orders.

==Basic orders==
You have build two stations and now you want to have a train running between them. The first thing you need to do is add the both the stations to the order list. We usually begin the orders with the pickup station:

[[Image:Start1.png]]

After this you add the drop station:

[[Image:Destination1.png]]

You now have given the train both the destinations, to let this route be effective however you need load orders.

== Load Orders ==

A load order is an order that tells the train to do a specific kind of loading. There are a few different kind of load orders:
* '''Load if available''' - The default load order. This order is not explicitly listed in the orders list so unless one of the other three load orders is present, this is the load order that the vehicle will use. When a vehicle stops at a station it will load all waiting cargo of any type that it can accept. The train will keep loading until it is either 100% full, or there is no cargo at the station to load.
* '''Full load all cargo''' - This load order tells the vehicle to stay at the station and load until it has reached 100% total cargo capacity. This load order will append "(Full load)" to the order.
* '''Full load any cargo''' - This load order tells the vehicle to stay at the station any load until any single cargo type that the vehicle accepts has reached 100%. An example would be an airplane that carries both passengers and mail, with full load any cargo the airplane will keep loading until either passengers or mail has reached 100% then continue to the next order. This keeps an airplane full of passengers from sitting on the tarmac waiting for more mail to fill up the airplane. This order can be useful anywhere that vehicles can carry multiple cargo types. This load order will append "(Full load any cargo)" to the order.
* '''No Loading''' - This load order tells the vehicle not to load at that station. When the vehicle has finished unloading cargo, it will continue to the next order in it's order list. In coop games, all drop stations should have this order unless it is desired for vehicles to pickup cargo at the drop station. Because drop stations are typically very large (thus have a very large catchment area), it is possible for a primary industry to open up within the drop stations catchment area at a later point in the game. When this happens, and yes it does happen often in public server games, then vehicles will drop their cargo and load more cargo before departing the drop station. Now when the vehicle returns to the primary industry station it is already partially (or completely) full. This decreases network efficiency. It also creates the annoyance of a drop station having a primary cargo rating. This load order will append "(No loading)" to the order.

== Unload Orders ==

An unload order tells a vehicle what to do with any cargo it may have.
*'''Unload if accepted'''- The default unload order. This order is not explicitly listed in the orders list so unless one of the other three unload orders is present, this is the unload order that the vehicle will use. When a vehicle stops at a station it will unload any cargo that it is carrying that is also accepted by the station.
*'''Unload all'''- This unload order tells the vehicle to unload all cargo, regardless of station acceptance. Any non accepted cargo will disappear. This unload order will append "(Unload and <load order>)" to the orders list, where <load> is the load order.
*'''Transfer'''- This unload order is explained later this page. This unload order appends "(Transfer and <load order>)" to the orders list, where <load> is the load order.
*'''No unloading'''- This unload order tells the vehicle that it is not to unload cargo at this station. This unload order appends "(Unload and <load order>)" to the orders list, where <load> is the load order.

==Go Orders==

Go orders are only available to trains and road vehicles(RV's). By default trains and RV's will stop at each station they pass through. Go orders can modify this behavior. The go order will immediately precede the station name in the orders list.
*'''Go to'''- This is the default go order. Vehicles will stop at the station on that line of the orders list AND STOP at any other station they travel through.
*'''Go non-stop to'''- Trains and RV's will stop at the station on that line of the orders list, but not stop at any other stations they travel through. There is an option in Advanced Settings/Vehicles to make: new orders are non-stop by default. This setting should be on for playing on the public server as single tile stations are frequently used on the public server for either penalties or occasionally used as waypoints. By making all orders "Go non-stop to", trains will not stop when they encounter theses stations.
*'''Go via'''- Trains and RV's will go to, and continue through the station in the order without stopping. They will however stop at any other stations they encounter. This order has the same functionality as waypoints. This order may have usefulness as a waypoint on a [[Self-regulating Network]], after the loading stations, otherwise the go non-stop via is preferred on the public server.
*'''Go non-stop via'''- With this order trains and RV's will go to without stoping at any station, and continue through the station in the order without stopping. This effectively turns stations into waypoints. The benefits of using stations as waypoints is that they can be built across several tracks, and thereby serve as a single waypoint across all (or only some if so desired) tracks of a ML. This preforms the same as waypoints with non-stop orders, and as station waypoints with the old TTDPatch non-stop compatible handling.

So for the train servicing the stations created above, the orders list will look like this:

[[Image:Orders1.png]]

The first order has the "Full load all cargo" load order, the second order has the "No loading" load order, and both orders have the "Go non-stop to" order. So the train will goto the station Sleningville Mines without stopping at any other station it may encounter on the way. It will unload any accepted cargo that it may have and stay at that station until all wagons, and the locomotive(s) if they have their own cargo capacity, are completely full. When fully loaded, the train will then go to the station Breadborune Cross Woods without stopping at any other stations it may encounter on the way. There the train will unload any accepted cargo that it may have, and leave without loading.

Since no unload order is indicated, both of this trains order have the default "Unload if accepted" order. Taking a view of the entire order list for this train tells us that the only place that it can get coal from is Sleningville Mines because there are only two stations the train is allowed to stop at, and it is only allowed to load at one of them. And even if a power station did open up within the catchment of Sleningville Mines the train would leave the station full of coal as unloading always happens before loading. The reason that the second order does not need the "Unload all" order is because on the public server a secondary industry drop station (as Breadborune Cross Woods is in this example) will always have the necessary industry within the catchment area, and therefore always accept the coal. It is also important to only have the default "Unload if accepted" order in games using newgrf industries that have a maximum stock of raw materials (such as Pikkas Basic Industries or ECS), then the unaccepted coal can continue to another possible drop station. In piratical use the "Unload all" order is just not necessary.

==Transfer orders==
When building multiple stations that are meant to be serviced by one train (or multiple trains sharing orders) you might need to use transfer orders. This kind of orders allow vehicles to keep cargo in the train and allow trains to unload all cargo at a station without loosing money. Transfer orders use virtual money this means that vehicles earn money so they don't show up as making a loss but the money won't be added to the bank balance. This is extremely usefull for making feeders.
There are four kinds of transfer orders:
* '''Transfer and take cargo''' - the combination of the "Transfer" unload order, with the "Load if available" load order. This order tells a vehicle to keep any cargo it has, and to load cargo until either the train is full or there is no more cargo waiting to load.
* '''Transfer and wait for full load''' - the combination of the "Transfer" unload order with the "Full load all cargo" load order. This order tells a vehicle to keep any cargo it has, and to load cargo until the train is full.
* '''Transfer and wait for any full load''' - the combination of the "Transfer" unload order with the "Full load any cargo" load order. This order tells a vehicle to keep any cargo it has, and to load cargo until any accepted cargo is full.
* '''Transfer and leave empty''' - the combination of the "Transfer" unload order with the "No Loading" load order. This order tells a vehicle to unload all cargo that it has to the station and collect it's "virtual money" for the distance(s) that the cargo has traveled. The cargo unloaded with this order will wait at the station to be loaded onto another vehicle, even if that cargo type is accepted at that station.

In the previous example of the coal train, let's assume that Breadbourne Cross Woods is just a transfer station where coal from several mines is gathered onto larger trains to travel to a central power station. In that case the orders would be:

[[Image:Orders2.png]]

[[Image:Transfer_overview.png|thumb|right|300px|A small SBahn ring]]

You have the following setup in a town which feeds a central station with passengers as in the picture to the right. Note that there are 4 station in this ring and the trains can drive both directions, the orders of the trains driving clock-wise will be explained in this section. SDH is the station where all ICE trains go to and that will be the station that will receive the passengers from the feeder trains.

Sonderhorst Woods is the first station after the unload station and won't need a transfer orders as there is no cargo in the train yet. The next station is Sonderhorst, this station needs a Transfer and take cargo order so we keep the current passengers loaded and take the passengers waiting at the station with us. Sonderhorst Heights needs the same orders as Sonderhorst. Last in line is SDH, this station will need a transfer and leave empty orders so the train will unload all the passengers loaded and also make some virtual money. The order list will end up looking like this:

[[Image:Transfer_orders.png]]

These kind of orders are very usefull when working with SBahn and must be used when working with SBahn rings with 3 stations or more.

----
[[Trains|<< Trains]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[How not to build|How not to build >>]]
[[Category:Guides]]

Trains

2010-07-19T16:03:39Z

Bodo Thiesen: improved inter guides linking

[[Networking|<< Networking]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Orders|Orders >>]]
----

Trains are a sensible part of OTTD. On this page, we just intend to make some short statements that help you building them for large networks like #openttdcoop's.

* '''Use SHARED ORDERS''' (CTRL+click on an existing train with the same order) for trains on the same route! This is probably the most important thing you have to care about. If you want to make a change for a route you just need to change the order and every train which shares this order will apply the change.
* '''Do not use waypoints anymore'''. Since the new pathfinding was implemented the trains behave quite smart and find the best way by themselves. A typical order list has only to consist of two orders "Goto Station XY + Full Load" and "Goto Station YZ" where it will unload (note: no need for an unload order!).
* Before we start the work on a map, we mostly agree to a unified, certain train length.
* In some games, '''train depots''' are used. These are small areas with all the train types to be used in the game already pre-created and sorted into the right train group. All you need to do is to copy one of those trains (''just copy'', no CTRL-click for shared orders, since the trains in the depot don't have orders!) and give them your orders. If you find such a depot in the game, ''do not create'' your own new trains.

----
[[Networking|<< Networking]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Orders|Orders >>]]
[[Category:Guides]]

Networking

2010-07-19T16:02:15Z

Bodo Thiesen: improved inter guides linking

[[Mainline_Junctions|<< Mainline Junctions]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Trains|Trains >>]]
----

After being able to build all these nice little hubs we return to some basics. Actually we demand you to do something very important before you start to build: just '''think about what you are doing!''' In the ruleset you probably read about our intention to build a comprehensive network. In a typical 512*512 game we have developed a certain networking-style. But do not misunderstand this: we do not want you to end up saying "Those guys are always just doing the same with all those strict rules...". We do not build networks one like the other! We always try to improve our building style and so the style changes.

The challenge is to invent new Network Concepts on the strategic level and new junctions/ stations etc. on the more detailed level of the game. Therefore, our games are not about doing the same things all the time but about keeping reliable network concepts and upgrade them with new ideas. But instead of writing so much about the theory we should get back and analyze a typical network of #openttdcoop.

[[Image:BasicNetwork.png|thumb|800px|center|Network overview]]

* On the map we see the 2x2 mainlines. On a 512*512 map we somtimes build some kind of "box" at the edges of the map. They provide some kind of a framework to our upcoming plans (note: on this screenshot only the southeastern part of the map is shown).
* Since mines/ factories/ plants/ farms located in the center of the map are far of this "framework" of mainlines, a mainline through the center is needed. It usually leads to a giant cloverleaf in the center of the map (note: we usually try to avoid cloverleafs due to their liability to jam). On our screenshot this "cross" of central mainlines is not yet completed but you already see the central west-east axis.
* Already shown in this screenshot: two Sideline Hubs at the "Eastern Axis". You probably notice the two sidelines originating at the two SLH's and the connected stations to the sidelines.
* If you ask yourself "Why the hell can't they build straight lines?!" there is an easy explaination for this: In OTTD, there are various landmark which can't be moved. Antennas (really evil things on hills), factories/ plants/ farms/ mines, churches (removable after some bribes -> expensive!) are other landmarks.
* This "crossed box" has proven to be a reliable concept on 512*512 maps but we are always searching for new ideas - and if we play on larger (or smaller) maps, we need a whole new concept.

==Depots==
The next picture is all about depots. Since we have a massive comprehensive network of railroad tracks we have trains going all along from one side of the map to the other side and back again. Despite break-downs are disabled in our standard configuration (if you ever operated more than 100 trains on a huge network in one game you know why) there is some train developement going on in the game. Therefore, we have to upgrade trains from time to time at a railroad depot. Since we have a massive comprehensive network of railroad tracks we have trains going all along from one side of the map to the other side and back again. We can't simply build depots somewhere on the map on sidelines or even next to a station because if we do so, a "goto depot"-order will cause trains going to the nearest depot - which means: most likely jamming sidelines or stations. You probably have to trust us this time: this is a serious issue!

Mucht developed a "Service Center" in order to build depots on the mainline.
[[Image:ServiceCenter.png|thumb|center|800px|Service Center]]

By making use of a [[PBS|Path Based Signal]] it is possible to have two trains at the same time enter the depots.
[[image:PBS_depot.png|thumb|center|800px|PBS depot]]

Notice:

* A train enters a depot quite slow. You have to implement some space so the train does not jam up the mainline because it enters the depot. If you look at the example picture you see some space for slowdown and even more space intended as acceleration area for the train.
* You always need a depot for every track at the mainline - if you try to save some money you risk trains moving straight forward to the next possibility to make a turn-around (which is, in a well-built network a station-area) and therefore jaming up the network instead of avoiding jams.
* Trains leaving the depot have to give priority to the mainline.
* Even name your service center. You know why.

----
[[Mainline_Junctions|<< Mainline Junctions]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Trains|Trains >>]]
[[Category:Guides]]

Basic Junctions

2010-07-19T16:00:45Z

Bodo Thiesen: improved inter guides linking

[[Sideline_stations|<< Sideline stations]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Mainline_Junctions|Mainline Junctions >>]]
----

In this part we build our first basic junction (in #openttdcoop we always call it "hub"). Since we always build multi-track-junctions, a junction is a bit more complicated than you may have done it before. We try to build ''efficient'' and ''fast'' railways and therefore we need ''efficient'' and ''fast'' junctions as well. For the start we will analyse a so-called [[Sideline_Hub|Sideline Hub]] - or '''SLH''' for short.

[[Image:BasicJuntions1.png|center|thumb|600px|A very basic [[Sideline_Hub|Sideline Hub]] - Note the lack of [[Balancing|load balancing]] ]]

We find several important things in the image above:
* A [[Basic_Networking|'''mainline''']] (also known as "Axis") goes from south to north (you can find it quite easy, mainlines have at least two tracks in each direction). The '''SLH''' has to connect a sideline to a mainline. This is the simplest case of a hub in our games. It is usually called '''"T-Hub"''' (just lean your head right and you will notice why).
* There are no [[Balancing|load balancers]] constructed for trains coming from the Sideline and entering the Mainline. The Loadbalancers will be explained later on.
* [[priorities|Priorities]] are missing on the mainline, so that trains entering the mainline slow down the trains on the mainline.
* Tunnels/ bridges are not doubled. Doubling is done based upon traffic load once a tunnel or bridge shows slowdowns for trains then it is needed to double. Unless it is a mainline or the tunnels/ bridges are longer then the distance between trains.

[[Image:BasicJuntions2.png|center|thumb|480px|An early [[Balancing|Loadbalancer]] - recent concepts are far better but this one already improves the balancing somewhat]]

On the image above, you see the idea of the balancing: if a Mainline-track is used (which means: a train is on the part the Sideline-Train wants to enter) the signal state is red - and the Sideline-Train chooses the other Mainline-track. A basic [[priorities|priority]] is used to accomplish this.

But for now, let us come back to our topic - basic junctions.I know what you are thinking: "Why are they doing these weird things?". The answer is: because it is the simplest thing in the end. Make a clean and intelligent building right from the start - it saves you and others later on.

Just imagine a game with 300+ trains and 100+ stations and every station has its own connection to a mainline with high traffic. All these entering/leaving trains will slow down other trains - it's some kind of chain reaction. [[Sideline_Hub|'''SLH's''']] are intended to be ''fast connection points'' from sidelines to mainlines. Traffic from stations are bundled to sidelines and via a SLH they are bundled to a massive mainline. This - in the end - ensures a fast and comprehensive network!

'''Name the HUB'''<br>
Every hub has a [[Naming_conventions|name]]! Not only because we are gifted writers but also because of finding all these hubs in the future. On a typical 512x512 map we end up with at least four "Backbone Hubs" (explained later on) and at least eight or even more Sideline Hubs.

[[Image:BasicJuntions3.png|center|thumb|357px|The signlist - click on a sign and you will get to the spot]]

Since #openttdcoop has something to deal with both communication and coordination it has proven that "Look at SLH 3" is easier to communicate rather than "Look at this hub east to the hub which is west of the eastern one". This ought to be obvious.

'''Things to keep in mind while constructing'''
* '''Close signaling!''' Always place signals as close as possible to a track split. This prevents unnecessary red-signal-times when a train passes a split.
[[Image:BasicJunction4.png|right|thumb|199px|The signals set as close as possible]]
* '''Think big!''' Our trains have a certain length (depending on the current game). If it is too long to enter a Sideline it therefore blocks not only the Sideline itself but also the Mainline. On a good junction the Sideline-entry is long enough for one whole train to wait.
* '''You can get from each direction to any other direction!''' Since we want to make our railline expandable, we don't want to rethink all the old hubs in the future. It is better to build a hub with as many features as possible right at the start rather than heaving a headache in the future.
* '''A clean building style!''' You are not at your own - and this is probably the best thing about #openttdcoop! Unfortunately, most of us can't read your mind and therefore it is best to make a clean building style everyone understands. To be more concrete: don't do unnecessary tracks, make comments (by using signs) of your ideas. Signs do not cost anything at all - except some pressed keys on your keyboard.
* '''Curve Radius'''. Depending on the game, we use a certain trainlength. Imaging a map with 3-tile-long-trains. This means: If you build curves with 3 tiles length each, the trains won't slow down! For monorail or maglev it's very important to remain at full speed. Just ask some experts around for the minimum radius for full [[Max_Curve_Speed|speed-curves]]. ''Note: for larger trainlengths, the radius is always smaller than the trainlength.''

[[Image:BasicJunction5.png|center|thumb|650px|Different trainlengths afford different curve radiuses for full speed]]

* Finally, one thing is left to say: '''the Mainline always has the highest priority!''' Keep this in your mind for the next chapters!

----
[[Sideline_stations|<< Sideline stations]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Mainline_Junctions|Mainline Junctions >>]]
[[Category:Guides]]

Mainline Junctions

2010-07-19T16:00:32Z

Bodo Thiesen: improved inter guides linking

[[Basic_Junctions|<< Basic Junctions ]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Networking| Networking >>]]
----

After building the first hubs in [[Basic_Junctions|Part 2]], you will probably notice that our mainlines may sometimes cross each other. Since we always build a comprehensive network and try to avoid dead-end lines, there is a point in the game where a so-called "Backbone Hub" is needed (remember to name the hub as described before). To see what we talk about, look at this:

[[Image:BBH.png|center|thumb|600px|Example of a [[Backbone_Hub|Backbone Hub]] ]]

Let us analyse this one:

* A mainline is built from east to west (if you read the previous pages carefully you should already know where east and west are). Be careful: this mainline has a temporary solution: the tunnels and bridges are all single for example purposes.
* Again, we have a T-Hub but this time it is slightly different: we do not connect a sideline (LR) to a mainline (LL___RR) but a mainline to a mainline.
* Mainlines enjoy the highest priority in the whole network. Mainlines are intended to be fast and hosting trains in order to go over long distances. Therefore, we try to avoid slowing down these trains on mainlines (remember: money has something to do with time and time is money!). In the end we come to the conclusion: Backbone Hubs have to be as fast as ever possible! As shown in our tutorial picture, there are no tight curves or major slopes. It is - as already shown - signaled as close as possible to avoid delays.
* Since a train typically has a route (notice: not order list!) like Station XY - Sideline Hub YZ - Backbone Hub ZA - Sideline Hub AB - Station BC, it has already the possibility to access both (i.g.: all) tracks of the mainline via the Sideline Hubs (remember: for SLH's we said: always connect every possibility!) we do not need to connect each track of one mainline to each track of the other mainline - which simplifies the whole thing a lot! You only need to connect the inner line of one mainline to the inner line of the other mainline and so one. Feel free to study our tutorial picture some minutes and you'll find out what we mean.
* The best start if you want to build a BBH is to move the tracks of one direction some spaces to have more space in between the tracks. You'll soon notice that this is a quite helpful trick.
* Always split before you join tracks, otherwise you might be creating a roundabout or (even worse) a cloverleaf junction. These junction types will jam once they see enough traffic from several directions.
* Don't mix that with join before split which has to be avoided by any means!
* In this example there is no load balancing, something you will see in our games.

----
[[Basic_Junctions|<< Basic Junctions ]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[Networking| Networking >>]]
[[Category:Guides]]

Sideline stations

2010-07-19T15:59:30Z

Bodo Thiesen: improved inter guides linking

[[Guides:Building|^^ Back to Building Guides Index]] | [[Basic_Junctions|Basic Junctions >>]]
----

First, we will start building a simple station. Before we start we want to make clear that our construction style is expandable in the future. Therefore, we construct huge mainlines (at least LL___RR or higher) and connect sidelines to this mainlines. Stations are ''always'' connected to sidelines. The number of platforms depends on the production rate of the farm/mine/forest. Take care about the pickup rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.

[[Image:BasicStation1.png|thumb|center|555px|A simple resource station connected to a [[Sideline|Sideline]]]]

You can clearly see a sideline going from south to north (lower right to upper left). As you notice, the signaling at the station is different to the simple signals on the track. This yellow signal is called "presignal" and the white signals are called "exit signals". They are more intelligent as the common signals and can be set by CTRL-click with the signal-building tool on an already built signal. If you are not used to this kind of signaling, please visit the our [[Presignals|presignaling Guide]] or the [http://wiki.openttd.org/ OTTD Wiki] for detailed information.

We usually build all stations as '''"RoRo"-Stations''' (roll-in, roll-out). This simply means no train exits a station in the same direction as it enters; as a result any departing trains won't block arriving trains. It's not necessarily needed for small stations, such as shown in our example, but let's stick to this building style wherever possible (sometimes RoRo's are simply not buildable due to space issues).

You may notice a drawback on the picture above: there may be too little space planned in for a train to wait. If all platforms of the station are occupied, you might have a train which wants to enter but has to wait in front of the station until another train departs. If there is too little space between the station and the corresponding sideline for waiting trains, the trains may jam up the sideline. Lets see if we can improve our stations a bit:

[[Image:BasicStation2.png|thumb|center|565px|Basic Stations connected to a [[Sideline|Sideline]] with extended waiting-space to avoid jams]]

You probably notice another important rule: '''never ever build a 90-degree-turn!''' Curves like that slow down trains quite a lot. You may ignore this rule close around a station (where trains are moving slow anyway).

'''''Since Version 0.5, on coop servers 90-deg-turn isn't possible anymore.'''''

[[Image:BasicStation3.png|thumb|center|265px|The difference between 90°-turns and 2*45°-turns]]

Despite this, we strongly suggest never to build 2*45-degree-turns due to speed issues. Also, try to build smooth curves in order to get trains fast off and fast on the sidelines.

For more information on various train stations such as those included in the newgrfs, please see [[illustrated newgrf station guide]]

----
[[Guides:Building|^^ Back to Building Guides Index]] | [[Basic_Junctions|Basic Junctions >>]]
[[Category:Guides]]

Guides:Building

2010-07-19T15:58:29Z

Bodo Thiesen: improved inter guides linking

[[Guides:Glossary|<< Glossary]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Presignals|Presignals >>]]
----

=<center>An illustrated guide to proper building</center>=
To help our new members and for reference, we have written a number of guides that will help you to understand how our games work. It is recommended that you read them in the order listed below.

==Part 1: Basic Stations==
First, we will start building a simple station. Before we start we want to make clear that our construction style is expandable in the future. Therefore, we construct huge mainlines and connect sidelines to this mainlines. Stations are ALWAYS connected to sidelines.

[[Sideline stations]]

==Part 2: Basic Junctions==
In this part we build the first junction (in #openttdcoop we always call it "hub"). Since we always build multi-track-junctions, a junction is a bit more complicated than it seems at first. Since we want to build efficient and fast railway networks, we need efficient and fast junctions as well. For the start we will analyse a so-called "Side Line Hub" (or "SLH" for short).

[[Basic Junctions]]

==Part 3: Mainline Junctions==
After building the first hubs in part 2, you will probably notice that our mainlines may sometimes cross each other. Since we always build a comprehensive network and always avoid dead-end lines, there is a point in the game where a so-called "Backbone Hub" is needed.

[[Mainline Junctions]]

==Part 4: Networking==
After being able to build all this nice little hubs we return to some basics. Actually we demand you to do something very important before you start to build: just think about what you are doing. In the ruleset you probably read about our intention to build a comprehensive network. In a typical 512*512 game we have developed a certain networking-style.

[[Networking]]

==Part 5: Trains==
Trains are a sensible part of OTTD. On this page, we just intend to make some short statements that help you building them for large networks like #openttdcoop's.

[[Trains]]

==Part 6: Orders==
After you built the first trains, you have to think about that. You'll find some guidelines on feeders here as well.

[[Orders]]

==Part 7: How not to build a network==
This guide is purely to show what happens when all the coop rules on building are blatantly ignored.

[[How not to build]]

----
[[Guides:Glossary|<< Glossary]] | [[Guides|^^ Back to Guides-Index]] | [[Guides:Presignals|Presignals >>]]
[[Category:Guides]]

Sideline stations

2010-07-19T15:44:28Z

Bodo Thiesen: copies link-menu to the bottom

[[Guides:Building|<< Back to Index]] | [[Basic_Junctions|Basic Junctions >>]]

First, we will start building a simple station. Before we start we want to make clear that our construction style is expandable in the future. Therefore, we construct huge mainlines (at least LL___RR or higher) and connect sidelines to this mainlines. Stations are ''always'' connected to sidelines. The number of platforms depends on the production rate of the farm/mine/forest. Take care about the pickup rating at primary industry stations. It should be between 65 and 75 per cent. Not more, since the production of the industry would fall down.

[[Image:BasicStation1.png|thumb|center|555px|A simple resource station connected to a [[Sideline|Sideline]]]]

You can clearly see a sideline going from south to north (lower right to upper left). As you notice, the signaling at the station is different to the simple signals on the track. This yellow signal is called "presignal" and the white signals are called "exit signals". They are more intelligent as the common signals and can be set by CTRL-click with the signal-building tool on an already built signal. If you are not used to this kind of signaling, please visit the our [[Presignals|presignaling Guide]] or the [http://wiki.openttd.org/ OTTD Wiki] for detailed information.

We usually build all stations as '''"RoRo"-Stations''' (roll-in, roll-out). This simply means no train exits a station in the same direction as it enters; as a result any departing trains won't block arriving trains. It's not necessarily needed for small stations, such as shown in our example, but let's stick to this building style wherever possible (sometimes RoRo's are simply not buildable due to space issues).

You may notice a drawback on the picture above: there may be too little space planned in for a train to wait. If all platforms of the station are occupied, you might have a train which wants to enter but has to wait in front of the station until another train departs. If there is too little space between the station and the corresponding sideline for waiting trains, the trains may jam up the sideline. Lets see if we can improve our stations a bit:

[[Image:BasicStation2.png|thumb|center|565px|Basic Stations connected to a [[Sideline|Sideline]] with extended waiting-space to avoid jams]]

You probably notice another important rule: '''never ever build a 90-degree-turn!''' Curves like that slow down trains quite a lot. You may ignore this rule close around a station (where trains are moving slow anyway).

'''''Since Version 0.5, on coop servers 90-deg-turn isn't possible anymore.'''''

[[Image:BasicStation3.png|thumb|center|265px|The difference between 90°-turns and 2*45°-turns]]

Despite this, we strongly suggest never to build 2*45-degree-turns due to speed issues. Also, try to build smooth curves in order to get trains fast off and fast on the sidelines.

For more information on various train stations such as those included in the newgrfs, please see [[illustrated newgrf station guide]]

[[Guides:Building|<< Back to Index]] | [[Basic_Junctions|Basic Junctions >>]]

Guides:Presignals

2010-07-19T15:42:14Z

Bodo Thiesen: /* Part 4: Load Balancers */ interwiki linkfix

=A Presignal Guide=
(under construction)
A guide for newbies, about presignals. However, this is not only for beginners as there are many complex things concerning presignals. If you know how the presignals work, you should skip the "basics" Part.

==Part 1: Basics==
The Presignal Basics is explained here: how they work, how they behave, and how does a terminal station work, and what's the use of the combo presignal.

[[Presignal Basics]]

==Part 2: Oneway or twoway Presignals==
Signals have two sides. In the basics part, the other side wasn`t important, since trains can`t turn back, etc. However, in more complex situations, a badly placed two way Combo Presignal can cause errors in your network.

[[Oneway or Twoway Presignals]]

==Part 3: Priorities==
When you have to connect two tracks into one, the most used track should have more priority than the lesser-used track.
In this Part, junctions with priority are shown.

[[Priorities]]

==Part 4: Load Balancers==
How to make presignals on a Load Balancer.

[[Balancing|Load Balancers]]

==Part 5: Complex Junctions==

[[Complex Junctions]]

Sideline stations

2010-07-19T15:41:08Z

Bodo Thiesen: completed Guides-Linking

Guides:Building

2010-07-19T15:36:25Z

Bodo Thiesen: interwiki

=<center>An illustrated guide to proper building</center>=
To help our new members and for reference, we have written a number of guides that will help you to understand how our games work. It is recommended that you read them in the order listed below.

==Part 1: Basic Stations==
First, we will start building a simple station. Before we start we want to make clear that our construction style is expandable in the future. Therefore, we construct huge mainlines and connect sidelines to this mainlines. Stations are ALWAYS connected to sidelines.

[[Sideline stations]]

==Part 2: Basic Junctions==
In this part we build the first junction (in #openttdcoop we always call it "hub"). Since we always build multi-track-junctions, a junction is a bit more complicated than it seems at first. Since we want to build efficient and fast railway networks, we need efficient and fast junctions as well. For the start we will analyse a so-called "Side Line Hub" (or "SLH" for short).

[[Basic Junctions]]

==Part 3: Mainline Junctions==
After building the first hubs in part 2, you will probably notice that our mainlines may sometimes cross each other. Since we always build a comprehensive network and always avoid dead-end lines, there is a point in the game where a so-called "Backbone Hub" is needed.

[[Mainline Junctions]]

==Part 4: Networking==
After being able to build all this nice little hubs we return to some basics. Actually we demand you to do something very important before you start to build: just think about what you are doing. In the ruleset you probably read about our intention to build a comprehensive network. In a typical 512*512 game we have developed a certain networking-style.

[[Networking]]

==Part 5: Trains==
Trains are a sensible part of OTTD. On this page, we just intend to make some short statements that help you building them for large networks like #openttdcoop's.

[[Trains]]

==Part 6: Orders==
After you built the first trains, you have to think about that. You'll find some guidelines on feeders here as well.

[[Orders]]

==Part 7: How not to build a network==
This guide is purely to show what happens when all the coop rules on building are blatantly ignored.

[[How not to build]]

----