#openttdcoop wiki - User contributions [en]

Guide: Creating a basic Ro-Ro Station

2024-01-22T04:55:30Z

OpenTTD Player9876556789: Created page with "After a while, production increases. Now, your trains are starting to block each other's paths at the Power Plant. What can you do? Well, if your tracks don't cross paths, you..."

After a while, production increases. Now, your trains are starting to block each other's paths at the Power Plant. What can you do? Well, if your tracks don't cross paths, your trains can't block each other's pathes. This isn't that important at the Coal Mine just yet, you could just spam trains to make up the money. But the more trains you have, the worse things get at the power plant. So, let's make a one way loop.

First, build a loop around the power plant or opposite it.

Next, link up the station's end that hasn't been connected to yet to the loop.

Add signals to the loop and the connection, making sure to either use PBS to link the station up or use Presignals correctly. Link the loop up to your tracks.

Disconnect any reduendent tracks.

And you're good to go.

Signals

2024-01-22T02:43:54Z

OpenTTD Player9876556789:

{{update}}
{{cleanup}}

See also: http://wiki.openttd.org/Signals

== Signal types ==
OpenTTD currently has 4 basic signal types (not counting presignals). These 4 are:
[[Image:Signals_basic_fixed.png|center]]

Each of these 4 signal types has different properties and should be used in different circumstances. An overview:
{| style="border:1px solid black;" border="1"
|-
! Signal
! Type
! Direction
! Comments
|-
! One-way block signal
| Block
| One-way
| The standard signal for one-way tracks, and therefore the most-used signal in coop games.
|-
! Two-way block signal
| Block
| Two-way
| Arguably the hardest signal to use properly. Standard double signals have an EOL property that means that if they are red, the pathfinder considers the signal the End Of a Line, thereby discarding its route. This property can lead to very unexpected and unwelcome behaviour. Use with caution.
|-
! PBS 1-Way
| Path-based
| One-way
| The path-based version of the standard single block signal. In general, use this instead of the PBS signal. However, whenever path-based signals are not strictly needed, use the standard single block signal instead.
|-
! PBS
| Path-based
| Two-way
| While this path-based signal can be driven two-ways, it does have a preference for one direction. This preferred driving direction is indicated by the single signal pole and is the same as with the PBS 1-Way. Driving a PBS signal the wrong way gives a fairly massive penalty in the pathfinder. This is the reason why we commonly use the reversed versions of these signals as penalties in our games.
|}

The two block signals themselves have specific versions, called pre-signals. More about those can be found in [[Presignal Basics]].
Path-based signals themselves have their own unique features, which are detailed [[Guides:Advanced_Signals|here]].

==Placing Signals==
[[Image:Standard signal dragging.png|left|thumb|200px|Basic Signalling]]
Before you start to use Automatic Signalling or Signal Dragging you should check the signal density. You can change it in the signal interface or edit the drag_signals_density value in your openttd.cfg. Make sure the value is set to two.

=== Basic Signalling ===
The first thing you should know is how use the basic signal dragging feature of OpenTTD: Build a signal (fastest Shortcut is A & S), left-click it and hold the button, drag it as far as you want to build signals. Release the button and the signals will be built. Very easy.

[[Image:Automatic signal completion.png|right|thumb|200px|Automatic Signal Completion]]
=== Automatic Signal Completion ===
Now we are ready to build signals and know how to use the basic feature of dragging. We can go a step further. Again Build a signal and drag it. While you are dragging it a little bit press the CTRL button and release it. The track will be filled up with signals until a breakpoint which are existing signals on the track, stations and junctions.

[[Image:Deleting signals.png|left|thumb|200px|Removing Signals]]
=== Removing Signals ===
It's also possible to remove Signals with the Automatic Completion feature. If you have build a track with signals, use the signal deletion function (Shortcut: A & S & R): click the signal, drag it while pressing the CTRL button and all the signals will be deleted. The breakpoints are stations and junctions.

=== Breakpoints ===
[[Image:Signalling breakpoints.png|right|thumb|200px|Breakpoints]]
Automatic Signal Completion won't stop at: '''Tunnels''' and '''Bridges'''
but stops at: Junctions (inculding merges), Stations, Waypoints, and Existing Signals

===Checking anyway===
After you have "signaled" a track, you should optimize signaling at junctions, they might need a signal right before or after the interruption to avoid signal gaps.

==Two-way signals==

Two-way signals are a common way to influence trains on coop servers. This is possible with the setting ''Two-way end of line''.

=== Two-way end of line ===
''Two-way end of line'' is a setting in OpenTTD that can be altered to create interesting train behaviour. By default it is off, but it is activated on every openttdcoop server.
A red two-way signal directs train to a different route if one is available.

Read more: http://wiki.openttdcoop.org/Two-way_end_of_line

== Presignals ==

Presignals are widely used in openttdcoop games for simple constructions as well as the most advanced ones.

Read more: http://wiki.openttdcoop.org/Guides:Presignals

== PBS ==
PBS stands for Path-Based Signaling

Details: http://wiki.openttdcoop.org/PBS

===Why not PBS everywhere?===

Though PBS dosn't lag computers (unless you've got thousands of trains constantly making requests), PBS checks for a clear route only every few ticks. Block signals can turn green the tick the block is clear becuase it only needs to know the block is clear, not the path. Therefore, it is slightly faster to use block signals vs. PBS when there can't be more than one train in the block with PBS. This logic is also true with a few Presignal blocks vs one PBS block, such as at station entrances.

== Signal Gaps ==
[[Image:Signal gap settings.png | thumb | 400px | right | Configuring auto-signalling]]
A signal gap, or gap for short, is the amount of unsignalled space in a single signal block. Understanding signal gaps is important for maximizing train density on a rail line and ensuring that trains continue to move at the maximum allowable speed. In coop games, we adhere to a maximum signal gap of 1 tile.

In general, use of the term "gap" indicates that a signal gap of length greater than 1 has been detected, and as a result, the efficiency of the network is at risk. Steps should be taken to fix any gaps marked in this manner.

Do not confuse a "signal gap" with a "train gap". A train gap is the minimum space between two trains. Because our signals are 2 spaced tiles apart (also known as [http://wiki.openttd.org/Railway_Designs Signal Density]), there is a minimum gap of 3 (the Signal Density +1).

<br clear=all>
=== Why is understanding gaps important? ===

A rail line is only as fast as its weakest link. If there is any point on the line where traffic must slow down or stop, the disruption will have a domino effect on any following trains, resulting in an inefficient network. As the goal is often to build a highly-efficient, and highly-dense network, these types of disruptions must be avoided at all costs!

<br clear=all>
=== What if I need to create a signal gap larger than 1? ===
[[Image:Signal gap sync.png | thumb | 400px | right | Make sure alternate routes are in sync]]
To create a signal gap larger than 1, you must provide following trains an alternate route until the gap is restored to 1. Larger gaps are created at station platforms, bridges, and tunnels, since none of these items can be signalled.

To create an alternate route, simply make a new line parallel to the first line. This line should continue until the signal gap can be restored to 1, making sure to keep the trains [[Line sync|synchronize]]d.

<br clear=all>
=== How to count the length of a gap ===
When using normal block signals, a gap's length is defined as the number of unsignalled spaces between two signals. Normal coop [[mainline]]s use a signal gap of 1, meaning there is only 1 unsignalled tiles between two signalled tiles.

When using pre-signals, the gap is counted from the tile after the first pre-signalled (or combo-signalled) tile through to (but not including) the next normal block signal (exit signals are still counted as part of the gap). If multiple routes exist, the largest value is the gap.

Placing a pre- (or combo-) signal and an exit signal (in that order) on a mainline will create a gap larger than 1, so this type of construction should not be done without creating an alternate route.

When using PBS signals, the gap is counted just like normal block signals: from the tile after the PBS signal through to (but not including) the next signalled tile. If multiple routes exist, the largest value is the gap.
[[Image:Signal gap counting.png | 400px | thumb | left | Counting signal gaps]] [[Image:Signal gap signals.png | 400px | thumb | left | Other signals]]

<br clear=all>

=== How many alternate routes do I need to create? ===
[[Image:Signal gap bridges.png | thumb | 400px | right | Two bridges for this gap is enough for any train length]]
The number of alternate routes is dependent on the length of the gap and the minimum train length that might encounter the gap.

The typical formula used to calculate the maximum gap length for a certain number of lines (LineCount) is

'''SignalGapLength = (TrainLength + 2) * LineCount - (TrainLength - 2)'''

Where TrainLength is the minimum train length to encounter the gap, and LineCount is the sum of the alternate routes provided + 1 (the original route).<br />
(This can be quickly calculated with [[User:KenjiE20/Webster|Webster's]] @gap)

Conversely:

'''LineCount = (SignalGapLength + TrainLength -2) / (TrainLength+2)'''

Always round any fractions up to the next whole number.<br />
(This can be quickly calculated with the [[IRC Commands|PublicServer bot's]] !gap)

Refer to the section above for information about how to count a gap properly.

<br clear=all>
==The Evil X ===
[[Image:Signal gap evilx.png | thumb | 400px | right | The Evil X]]
When two lines cross each other in an oblique (non-perpendicular) way, it creates an "evil X". The main problem with the evil X is that it inherently creates a signal gap of 2.

A simple merge does not create a large gap, as long as the tiles before (on both lines) and after (on the single output line) are signalled.

However, note that when the tracks cross obliquely, it is not possible to signal the output line, creating the gap.

In practically all cases, evil X's should be avoided.

[[Category:Guides]]
[[Category:Basic networking]]

PBS

2024-01-22T02:36:39Z

OpenTTD Player9876556789:

See also http://wiki.openttd.org/PBS

==Description==

PBS stands for Path Based Signaling, which is a signal type that allows multiple trains to enter one signal block. Although primarily intended in OpenTTD (and in the real world) to provide bi-directional track, without the deadlocks that will occur with regular signaling. Besides that it can also be used to increase performance in certain situations.

==How it works==
For an explanation on the basics of YAPP and some examples, please check [http://wiki.openttd.org/Yet_Another_PBS_Patch the YAPP page] on the OpenTTD site.

In short: PBS introduces a new type of signal, which comes in two flavors. The first type is a regular (or: two-way) PBS signal, the second a one-way PBS signal. When a train encounters a PBS signal it will attempt to reserve a path. This means that it will look ahead at the path it wants to go and determines whether there are any obstacles in the way, such as another train. It will only look as far as the next signal it encounters (any signal, no specific type). When a reservation can be made, the train will go past the signal along the reserved path, otherwise it'll wait until it can do so.

The advantage of PBS is that it allows multiple trains to enter a PBS guarded area, as long as their reserved paths do not cross each other. While a regular signal would stop the second train until the entire section of track is clear, using PBS signaling trains can overcome this limitation. An example can be shown below. Here, both trains will attempt to enter the crossing, both trains go straight ahead on their path. When the first train encounters PBS signal A, it will reserve a path up to signal C. Since there are no obstacles, the reservation is allowed and the train passes. Moments later, the second train encounters signal B and attempts to reserve a path to signal D. Since train 1 is not in the way, the reservation will be made as well and train 2 will continue as well. At that time, both trains are in the same PBS signaled section. If regular signals would be used in this case, one train would always have to wait.

[[Image:pbs_demo1_2trains.png]] [[Image:pbs_demo2_2trains.png]]

As said, there are two types of the PBS signal (regular and one-way). The regular signal is basically two way, but passing the signal from the back comes with a penalty in the pathfinder which will thus attempt to avoid it. This signal can be useful for situations where you want to allow trains to pass the signal from the back, but only when there's no other way. Applications include two way stations and two-way track, all of which can be found in the OpenTTD wiki. The one-way signal does not allow trains from the back is is used in situations where it's combined with regular one-way track, such as the examples below. It could be said that one should avoid regular PBS in one-way track, because trains that reverse might collide with the train behind them.

==Examples from #OpenTTDCoop games==

===Terminus station===
This is a normal [http://wiki.openttd.org/Railway_station#Terminus terminus station], except that PBS is used to allow more than one train to be in the signaling block in front of the station. The entry has a one-way PBS signal, each station track has a normal PBS signal facing the station. The exit has a regular one-way exit signal. The advantage of the station shown in the screenshot is that it allows a train to leave the station while another train enter it. This could improve throughput, depending on how large your station is. Please note that the exit signal has a gap, to avoid that a train waiting in front of that signal will block the track.

Below is and example of PBS signaling used at a terminus station. As you can see, one train leaves the station taking the left most track to the exit. At the same time a train is entering the station on the middle track. The is actually only 1 PBS signal, directly in front of the station one could place more PBS signals but these are not really needed. Also, in the example below there's a single tile track section in front of the station. Although not really needed, it provides trains with some breaking space so the train will spend less time on the switches. This may sometimes clear a path for the next train sooner, increasing performance.

[[Image:Pbs_terminus.jpg]]

===PBS bridges===
The bridges shown here have only one signal placed in front of them, with regular signals after them. As you can see from the screenshot, there is very little track in front of the bridge, because there are no signals needed in front of the bridge.

[[Image:Pbs_bridge.jpg]]

===PBS depot===
This depot setup slightly improves the amount of trains that can be serviced. It basically allows for two trains to be on the same tile, for example to have one train exit the depot while the other enters it.

[[Image:Pbs_depot.jpg|PBS depot. Notice that one train enters the depot while the other leaves, sharing the same tile.]]

===Hints for using PBS===
* Enable 'Show reserved tracks' in the OpenTTD patches to show ingame which tracks are being taken by trains entering sections. In the screenshots above you can see this, the track is a little darker.
* Build one-way PBS signals if possible. #OpenTTDCoop games will rarely need the use of two-way PBS, except for penalties

=== See also ===

* [[Signals]]
* [[Presignals]]

[[Category:Guides]]
[[Category:Basic networking]]

Signals

2024-01-22T02:35:04Z

OpenTTD Player9876556789:

{{update}}
{{cleanup}}

See also: http://wiki.openttd.org/Signals

== Signal types ==
OpenTTD currently has 4 basic signal types (not counting presignals). These 4 are:
[[Image:Signals_basic_fixed.png|center]]

Each of these 4 signal types has different properties and should be used in different circumstances. An overview:
{| style="border:1px solid black;" border="1"
|-
! Signal
! Type
! Direction
! Comments
|-
! One-way block signal
| Block
| One-way
| The standard signal for one-way tracks, and therefore the most-used signal in coop games.
|-
! Two-way block signal
| Block
| Two-way
| Arguably the hardest signal to use properly. Standard double signals have an EOL property that means that if they are red, the pathfinder considers the signal the End Of a Line, thereby discarding its route. This property can lead to very unexpected and unwelcome behaviour. Use with caution.
|-
! PBS 1-Way
| Path-based
| One-way
| The path-based version of the standard single block signal. In general, use this instead of the PBS signal. However, whenever path-based signals are not strictly needed, use the standard single block signal instead.
|-
! PBS
| Path-based
| Two-way
| While this path-based signal can be driven two-ways, it does have a preference for one direction. This preferred driving direction is indicated by the single signal pole and is the same as with the PBS 1-Way. Driving a PBS signal the wrong way gives a fairly massive penalty in the pathfinder. This is the reason why we commonly use the reversed versions of these signals as penalties in our games.
|}

The two block signals themselves have specific versions, called pre-signals. More about those can be found in [[Presignal Basics]].
Path-based signals themselves have their own unique features, which are detailed [[Guides:Advanced_Signals|here]].

==Placing Signals==
[[Image:Standard signal dragging.png|left|thumb|200px|Basic Signalling]]
Before you start to use Automatic Signalling or Signal Dragging you should check the signal density. You can change it in the signal interface or edit the drag_signals_density value in your openttd.cfg. Make sure the value is set to two.

=== Basic Signalling ===
The first thing you should know is how use the basic signal dragging feature of OpenTTD: Build a signal (fastest Shortcut is A & S), left-click it and hold the button, drag it as far as you want to build signals. Release the button and the signals will be built. Very easy.

[[Image:Automatic signal completion.png|right|thumb|200px|Automatic Signal Completion]]
=== Automatic Signal Completion ===
Now we are ready to build signals and know how to use the basic feature of dragging. We can go a step further. Again Build a signal and drag it. While you are dragging it a little bit press the CTRL button and release it. The track will be filled up with signals until a breakpoint which are existing signals on the track, stations and junctions.

[[Image:Deleting signals.png|left|thumb|200px|Removing Signals]]
=== Removing Signals ===
It's also possible to remove Signals with the Automatic Completion feature. If you have build a track with signals, use the signal deletion function (Shortcut: A & S & R): click the signal, drag it while pressing the CTRL button and all the signals will be deleted. The breakpoints are stations and junctions.

=== Breakpoints ===
[[Image:Signalling breakpoints.png|right|thumb|200px|Breakpoints]]
Automatic Signal Completion won't stop at: '''Tunnels''' and '''Bridges'''
but stops at: Junctions (inculding merges), Stations, Waypoints, and Existing Signals

===Checking anyway===
After you have "signaled" a track, you should optimize signaling at junctions, they might need a signal right before or after the interruption to avoid signal gaps.

==Two-way signals==

Two-way signals are a common way to influence trains on coop servers. This is possible with the setting ''Two-way end of line''.

=== Two-way end of line ===
''Two-way end of line'' is a setting in OpenTTD that can be altered to create interesting train behaviour. By default it is off, but it is activated on every openttdcoop server.
A red two-way signal directs train to a different route if one is available.

Read more: http://wiki.openttdcoop.org/Two-way_end_of_line

== Presignals ==

Presignals are widely used in openttdcoop games for simple constructions as well as the most advanced ones.

Read more: http://wiki.openttdcoop.org/Guides:Presignals

== PBS ==

Full article: http://wiki.openttdcoop.org/PBS

== Signal Gaps ==
[[Image:Signal gap settings.png | thumb | 400px | right | Configuring auto-signalling]]
A signal gap, or gap for short, is the amount of unsignalled space in a single signal block. Understanding signal gaps is important for maximizing train density on a rail line and ensuring that trains continue to move at the maximum allowable speed. In coop games, we adhere to a maximum signal gap of 1 tile.

In general, use of the term "gap" indicates that a signal gap of length greater than 1 has been detected, and as a result, the efficiency of the network is at risk. Steps should be taken to fix any gaps marked in this manner.

Do not confuse a "signal gap" with a "train gap". A train gap is the minimum space between two trains. Because our signals are 2 spaced tiles apart (also known as [http://wiki.openttd.org/Railway_Designs Signal Density]), there is a minimum gap of 3 (the Signal Density +1).

<br clear=all>
=== Why is understanding gaps important? ===

A rail line is only as fast as its weakest link. If there is any point on the line where traffic must slow down or stop, the disruption will have a domino effect on any following trains, resulting in an inefficient network. As the goal is often to build a highly-efficient, and highly-dense network, these types of disruptions must be avoided at all costs!

<br clear=all>
=== What if I need to create a signal gap larger than 1? ===
[[Image:Signal gap sync.png | thumb | 400px | right | Make sure alternate routes are in sync]]
To create a signal gap larger than 1, you must provide following trains an alternate route until the gap is restored to 1. Larger gaps are created at station platforms, bridges, and tunnels, since none of these items can be signalled.

To create an alternate route, simply make a new line parallel to the first line. This line should continue until the signal gap can be restored to 1, making sure to keep the trains [[Line sync|synchronize]]d.

<br clear=all>
=== How to count the length of a gap ===
When using normal block signals, a gap's length is defined as the number of unsignalled spaces between two signals. Normal coop [[mainline]]s use a signal gap of 1, meaning there is only 1 unsignalled tiles between two signalled tiles.

When using pre-signals, the gap is counted from the tile after the first pre-signalled (or combo-signalled) tile through to (but not including) the next normal block signal (exit signals are still counted as part of the gap). If multiple routes exist, the largest value is the gap.

Placing a pre- (or combo-) signal and an exit signal (in that order) on a mainline will create a gap larger than 1, so this type of construction should not be done without creating an alternate route.

When using PBS signals, the gap is counted just like normal block signals: from the tile after the PBS signal through to (but not including) the next signalled tile. If multiple routes exist, the largest value is the gap.
[[Image:Signal gap counting.png | 400px | thumb | left | Counting signal gaps]] [[Image:Signal gap signals.png | 400px | thumb | left | Other signals]]

<br clear=all>

=== How many alternate routes do I need to create? ===
[[Image:Signal gap bridges.png | thumb | 400px | right | Two bridges for this gap is enough for any train length]]
The number of alternate routes is dependent on the length of the gap and the minimum train length that might encounter the gap.

The typical formula used to calculate the maximum gap length for a certain number of lines (LineCount) is

'''SignalGapLength = (TrainLength + 2) * LineCount - (TrainLength - 2)'''

Where TrainLength is the minimum train length to encounter the gap, and LineCount is the sum of the alternate routes provided + 1 (the original route).<br />
(This can be quickly calculated with [[User:KenjiE20/Webster|Webster's]] @gap)

Conversely:

'''LineCount = (SignalGapLength + TrainLength -2) / (TrainLength+2)'''

Always round any fractions up to the next whole number.<br />
(This can be quickly calculated with the [[IRC Commands|PublicServer bot's]] !gap)

Refer to the section above for information about how to count a gap properly.

<br clear=all>
==The Evil X ===
[[Image:Signal gap evilx.png | thumb | 400px | right | The Evil X]]
When two lines cross each other in an oblique (non-perpendicular) way, it creates an "evil X". The main problem with the evil X is that it inherently creates a signal gap of 2.

A simple merge does not create a large gap, as long as the tiles before (on both lines) and after (on the single output line) are signalled.

However, note that when the tracks cross obliquely, it is not possible to signal the output line, creating the gap.

In practically all cases, evil X's should be avoided.

[[Category:Guides]]
[[Category:Basic networking]]

Signals

2024-01-22T02:32:22Z

OpenTTD Player9876556789: /* Signal types */

{{update}}
{{cleanup}}

See also: http://wiki.openttd.org/Signals

== Signal types ==
OpenTTD currently has 4 basic signal types (not counting presignals). These 4 are:
[[Image:Signals_basic_fixed.png|center]]

Each of these 4 signal types has different properties and should be used in different circumstances. An overview:
{| style="border:1px solid black;" border="1"
|-
! Signal
! Type
! Direction
! Comments
|-
! One-way block signal
| Block
| One-way
| The standard signal for one-way tracks, and therefore the most-used signal in coop games.
|-
! Two-way block signal
| Block
| Two-way
| Arguably the hardest signal to use properly. Standard double signals have an EOL property that means that if they are red, the pathfinder considers the signal the End Of a Line, thereby discarding its route. This property can lead to very unexpected and unwelcome behaviour. Use with caution.
|-
! PBS 1-Way
| Path-based
| One-way
| The path-based version of the standard single block signal. In general, use this instead of the PBS signal. However, whenever path-based signals are not strictly needed, use the standard single block signal instead.
|-
! PBS
| Path-based
| Two-way
| While this path-based signal can be driven two-ways, it does have a preference for one direction. This preferred driving direction is indicated by the single signal pole and is the same as with the PBS 1-Way. Driving a PBS signal the wrong way gives a fairly massive penalty in the pathfinder. This is the reason why we commonly use the reversed versions of these signals as penalties in our games.
|}

The two block signals themselves have specific versions, called pre-signals. More about those can be found in [[Presignal Basics]].
Path-based signals themselves have their own unique features, which are detailed [[Guides:Advanced_Signals|here]].

==Placing Signals==
[[Image:Standard signal dragging.png|left|thumb|200px|Basic Signalling]]
Before you start to use Automatic Signalling or Signal Dragging you should check the signal density. You can change it in the signal interface or edit the drag_signals_density value in your openttd.cfg. Make sure the value is set to two.

=== Basic Signalling ===
The first thing you should know is how use the basic signal dragging feature of OpenTTD: Build a signal (fastest Shortcut is A & S), left-click it and hold the button, drag it as far as you want to build signals. Release the button and the signals will be built. Very easy.

[[Image:Automatic signal completion.png|right|thumb|200px|Automatic Signal Completion]]
=== Automatic Signal Completion ===
Now we are ready to build signals and know how to use the basic feature of dragging. We can go a step further. Again Build a signal and drag it. While you are dragging it a little bit press the CTRL button and release it. The track will be filled up with signals until a breakpoint which are existing signals on the track, stations and junctions.

[[Image:Deleting signals.png|left|thumb|200px|Removing Signals]]
=== Removing Signals ===
It's also possible to remove Signals with the Automatic Completion feature. If you have build a track with signals, use the signal deletion function (Shortcut: A & S & R): click the signal, drag it while pressing the CTRL button and all the signals will be deleted. The breakpoints are stations and junctions.

=== Breakpoints ===
[[Image:Signalling breakpoints.png|right|thumb|200px|Breakpoints]]
Automatic Signal Completion won't stop at: '''Tunnels''' and '''Bridges'''
but stops at: Junctions, Stations and Existing Signals

===Checking anyway===
After you have "signaled" a track, you should optimize signaling at junctions, they might need a signal right before or after the interruption to avoid signal gaps.

==Two-way signals==

Two-way signals are a common way to influence trains on coop servers. This is possible with the setting ''Two-way end of line''.

=== Two-way end of line ===
''Two-way end of line'' is a setting in OpenTTD that can be altered to create interesting train behaviour. By default it is off, but it is activated on every openttdcoop server.
A red two-way signal directs train to a different route if one is available.

Read more: http://wiki.openttdcoop.org/Two-way_end_of_line

== Presignals ==

Presignals are widely used in openttdcoop games for simple constructions as well as the most advanced ones.

Read more: http://wiki.openttdcoop.org/Guides:Presignals

== PBS ==

Full article: http://wiki.openttdcoop.org/PBS

== Signal Gaps ==
[[Image:Signal gap settings.png | thumb | 400px | right | Configuring auto-signalling]]
A signal gap, or gap for short, is the amount of unsignalled space in a single signal block. Understanding signal gaps is important for maximizing train density on a rail line and ensuring that trains continue to move at the maximum allowable speed. In coop games, we adhere to a maximum signal gap of 1 tile.

In general, use of the term "gap" indicates that a signal gap of length greater than 1 has been detected, and as a result, the efficiency of the network is at risk. Steps should be taken to fix any gaps marked in this manner.

Do not confuse a "signal gap" with a "train gap". A train gap is the minimum space between two trains. Because our signals are 2 spaced tiles apart (also known as [http://wiki.openttd.org/Railway_Designs Signal Density]), there is a minimum gap of 3 (the Signal Density +1).

<br clear=all>
=== Why is understanding gaps important? ===

A rail line is only as fast as its weakest link. If there is any point on the line where traffic must slow down or stop, the disruption will have a domino effect on any following trains, resulting in an inefficient network. As the goal is often to build a highly-efficient, and highly-dense network, these types of disruptions must be avoided at all costs!

<br clear=all>
=== What if I need to create a signal gap larger than 1? ===
[[Image:Signal gap sync.png | thumb | 400px | right | Make sure alternate routes are in sync]]
To create a signal gap larger than 1, you must provide following trains an alternate route until the gap is restored to 1. Larger gaps are created at station platforms, bridges, and tunnels, since none of these items can be signalled.

To create an alternate route, simply make a new line parallel to the first line. This line should continue until the signal gap can be restored to 1, making sure to keep the trains [[Line sync|synchronize]]d.

<br clear=all>
=== How to count the length of a gap ===
When using normal block signals, a gap's length is defined as the number of unsignalled spaces between two signals. Normal coop [[mainline]]s use a signal gap of 1, meaning there is only 1 unsignalled tiles between two signalled tiles.

When using pre-signals, the gap is counted from the tile after the first pre-signalled (or combo-signalled) tile through to (but not including) the next normal block signal (exit signals are still counted as part of the gap). If multiple routes exist, the largest value is the gap.

Placing a pre- (or combo-) signal and an exit signal (in that order) on a mainline will create a gap larger than 1, so this type of construction should not be done without creating an alternate route.

When using PBS signals, the gap is counted just like normal block signals: from the tile after the PBS signal through to (but not including) the next signalled tile. If multiple routes exist, the largest value is the gap.
[[Image:Signal gap counting.png | 400px | thumb | left | Counting signal gaps]] [[Image:Signal gap signals.png | 400px | thumb | left | Other signals]]

<br clear=all>

=== How many alternate routes do I need to create? ===
[[Image:Signal gap bridges.png | thumb | 400px | right | Two bridges for this gap is enough for any train length]]
The number of alternate routes is dependent on the length of the gap and the minimum train length that might encounter the gap.

The typical formula used to calculate the maximum gap length for a certain number of lines (LineCount) is

'''SignalGapLength = (TrainLength + 2) * LineCount - (TrainLength - 2)'''

Where TrainLength is the minimum train length to encounter the gap, and LineCount is the sum of the alternate routes provided + 1 (the original route).<br />
(This can be quickly calculated with [[User:KenjiE20/Webster|Webster's]] @gap)

Conversely:

'''LineCount = (SignalGapLength + TrainLength -2) / (TrainLength+2)'''

Always round any fractions up to the next whole number.<br />
(This can be quickly calculated with the [[IRC Commands|PublicServer bot's]] !gap)

Refer to the section above for information about how to count a gap properly.

<br clear=all>
==The Evil X ===
[[Image:Signal gap evilx.png | thumb | 400px | right | The Evil X]]
When two lines cross each other in an oblique (non-perpendicular) way, it creates an "evil X". The main problem with the evil X is that it inherently creates a signal gap of 2.

A simple merge does not create a large gap, as long as the tiles before (on both lines) and after (on the single output line) are signalled.

However, note that when the tracks cross obliquely, it is not possible to signal the output line, creating the gap.

In practically all cases, evil X's should be avoided.

[[Category:Guides]]
[[Category:Basic networking]]

File:Signals basic fixed.png

2024-01-22T02:30:29Z

OpenTTD Player9876556789: More accurate descriptions Version: OpenTTD Stable 13.4

More accurate descriptions
Version: OpenTTD Stable 13.4

File:Signals basic.png

2024-01-22T02:27:50Z

OpenTTD Player9876556789: OpenTTD Player9876556789 uploaded a new version of File:Signals basic.png

The signals without combo's, but including two-way.

Two-way end of line

2024-01-22T02:21:38Z

OpenTTD Player9876556789:

=== Two-way end of line ===
''Two-way end of line'' is a setting in OpenTTD that can be altered to create interesting train behaviour. By default it has been on in recent years (as of Jan 2024), but was off in the years when Openttdcoop was popular, but it is activated on every openttdcoop server.
A red two-way signal directs train to a different route if one is available.

''While used in combination with the default YAPF pathfinder, two-way signals (exculding the two way PBS/Path-Based Signal) have a weird and often misunderstood property. This property, called yapf.rail_firstred_twoway_eol, means that if the first encountered signal is a red two-way, that signal is considered a dead end. Now to understand the impact of this, one must first understand the basics of YAPF. In a nutshell: YAPF calculates all possible routes, called paths, from the train's current position. Each path is evaluated to a single score, determined by the length of the path, obstacles like stations, roads and hills, and upcoming red signals and of course the ability to reach the destination (station). The train then chooses the path with the lowest penalty score.

Consider the train is on a junction and has multiple exit possibilities. The issue with red two-way signals is that if the first signal on a path is a red two-way, that path is not evaluated at all as it is considered a dead end. You could say that the path gets a penalty score of infinity. This also means that any other possible path, if it exists, is automatically better than the two-way path. Even if the other possibility is a wrong direction, detouring or actual dead end path.
What this means in practice is:
* If all possible paths start with red two-way signals, the paths are considered equal and a choice is made without considering the network after the signals.
Note: If the red two-way signals are exit/combo signals in a presignal setup, trains will wait at the entry signal as though the exit/combo signals were normal red signals.
* If there is a single path not starting with a red two-way signal, that path is automatically chosen without considering the usefulness of the path itself.
Most important is that a choice is made without looking ahead at all. This includes checking if the chosen path actually leads to the desired destination. This can cause massive problems in our games, with trains detouring or even driving themselves into a non-penalty station or actual dead end.

Now is the EOL (End of Line) property a setting that can be changed. However, on our servers it is always on, as it gives trains the ability of free choice. If two different paths share a destination, but are considered by the pathfinder to be very unequal penalty-wise, with single signals a train might decide to take the path with the lowest penalty, even though that means waiting for a red light. With two-way signals this will never happen.

In short:
* Only use two-way block signals when you understand their workings and use. Otherwise, use one way block signals or PBS.
* Only use two-way block signals in situations where each path has the same destination but a possibly very unequal penalty, and where it is important for the train to make an indiscriminate choice. You can think of mergers and SLH joins. But please remember that you don't always have to use them. If you can avoid them, do so.
* Especially avoid two-way signals when not all of the exits are two-way, and not all paths lead to the same place. The most common error is combining a double bridging of a mainline with the exit of a track.
* The exception is of course for track that actually has to be two-way, like the signals next to platforms in terminus stations.
* Two-way signals can also legitimately be used in logic systems and the creation of priorities.''

=== Pathfinder trap ===
A major use of this setting is found in our [[SRNW]] games, where we control trains to either take an exit to the sideline or stay on the mainline. We also combine this signal with a certain station or shortcut to create pathfinder traps. Pathfinder traps give us options to trick trains, we can decrease the pathfinder penalties to an actual station and so create more balanced traffic or we can balance mainline mergers. There are occasions where the inner lane is preferred so much we will create a shortcut from each lane to the inner lane after a merger. We disable an exit with the pathfinder trap so the trains will not actually take this path (which would create a train traffic jam) and a merger gives us a balanced output.
{| align="center"
|| [[File:Pftrap.png|300px|thumb|center|Pathfinder trap in its raw form.]]
|| [[File:Pftraponmainline.png|300px|thumb|center|Pathfinder trap on mainline to create a shortcut that can never be used.]]
|}
=== Station with overflow ===
[[Overflow|Full article]]

In our games we often use overflows and this setting can help us create easy to implement overflows for our primaries. One example of this is found in the picture below.

{| align="right"
|| [[File:Overflow primary.png|300px|thumb|center|Overflow on the a primary with reverser arrows.]]
|| [[File:TerminusPrimary.png|300px|thumb|right|Arrows on a primary station]]
|}

In the picture you can see the “ arrow” in the reverser. It is not eye-candy it actually has a use. The pathfinder sees that the other tracks are blocked and considers the reverser only a viable line if it has at least 2 options. This means we create a split in the reverser so the pathfinder thinks it has two options.

Similarly we advise you to also use this arrow on every reverser, and in every terminus station with pre-signals at the final X as seen in picture below. In theory only the track that has a straight line to the exit track should have one, but we still prefer using them on all platforms for a terminus station.

=== Setting up two-way end of line ===
To setup this behaviour in your own game you can do this in two ways: We at openttdcoop prefer you use the second way because it is permanent, stable and easier.

*Either in game trough the console command accessible with the “~” key. Follow this by sending the following command:
“set yapf.rail_firstred_twoway_eol 1”
*The second way of changing this setting is by editing your openttd config file. And please do this when the game is closed, otherwise the file won't save or your game might malfunction. The location of this file is a question Google Search has an answer to. In here you find the line “yapf.rail_firstred_twoway_eol = false” and change it to “yapf.rail_firstred_twoway_eol = true” Follow this by saving and closing the config file.

[[Category:Guides]]
[[Category:Advanced Networking]]

Main Page/editcopy

2024-01-22T01:48:34Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
| class="frontpage_box" |
==<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>==
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]
</div>
| class="frontpage_box" |
==<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>==
<div style="padding-left: 1em;">
===General===
; [[Orders]] • [[Terraforming]] • [[Logic]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
===Tracks===
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]] • [[Max Curve Speed|Curves (CL)]]
; [[Sideline]]
===[[Signalling]]===
; [[Guides:Presignals|Pre-signals]] • [[Two-way end of line|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary - Mergers|Mergers]] • [[Junctionary - City Networks|City Networks]] • [[Junctionary - Logic and Other|Logic and Other]]
;[[Advanced Building Revue|Advanced Building Revue (ABR)]]
</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Max Curve Speed

2024-01-22T01:44:19Z

OpenTTD Player9876556789:

Making trains keep their speed at maximum is key for keeping traffic fluent.

==Numbering Convention==

Because the most important part of everything happening on this page is creating an actual curve that demonstrates the building convention.

It is necessary know how to name curves by numbers.
This is fairly simple if you turn on counting in the game interface.

'''Advanced settings -> Interface -> Display Options -> Display measurement tooltip...'''

Then we just use those values the game says. An exception is when the used curves are in between - one from each. In that case when, for example between 1 and 2, we say CL1.5 as the picture below demonstrates.

[[Image:Curve_convention.png|600px]]

==Travel speed mechanism==

Here is how it is decided whether a train will slow down on a curve and by how much. Getting the Curve Speed value is shown below.

[[Image:Curve_mechanism.png|600px]]

==Curve Speed==

The easiest way to know how fast a train can go through a curve is by simply testing, but it can also be counted by taking:

'''[https://wiki.openttd.org/en/Manual/Game%20Mechanics/#trains Base Curve Speed]''', multiplied by:

• monorail bonus - x1,5

• maglev bonus - x2

• tilt - x1,2

• short wagons - about x1,2 for "half-length wagons"

The base curve speed can be found on the [http://wiki.openttd.org/Game_mechanics#Trains OpenTTD wiki], but this graph demonstrates it too (plus monorail and maglev as well)

[[Image:curve_speeds1.png]]

==Special Curves==

There are not always just full curves, but also Sbends and such.
Counting their maximum speed is quite complicated so it is easier to just try it in game if the train slows down in the specific curve or not.

[[Image:slow_corners.png|frame|none|An example showing which corners are affected]]

==Side Notes==
'''The real calculation OpenTTD does is counting wagons''' (vehicles) between curves, meaning that shorter wagons can travel through curves faster.

However, because the actual output of all the curve counting for us is setting up a convention how to build in a specific game,
it is most useful to use counting by curve lengths (as shown in the beginning of this page) instead of counting vehicles.

From observation, half length wagons get about 20% bonus so it is something like if they had tilt. Those two bonuses stack however, so the combined bonus can be around 40%.

'''In the newGRF code''', railtypes can allow higher speeds. The smallest possible is what normal and electrified rail has. [http://newgrf-specs.tt-wiki.net/wiki/NML:Railtypes#Base_speeds_for_curves.] In addition, certain NewGRF trains (such as some trains in the NUTS Unrealistic Train Set) can go faster than would normally be possible on certain curves.

== See Also ==
* For some more detailed information see {{User|Mark}}'s blog post: http://www.openttdcoop.org/blog/2009/05/13/about-curve-lengths/
* [[User:KenjiE20/Webster#Curve Length Calculator|Webster's helper function]]

[[Category:Guides]]
[[Category:Basic networking]]

Guide: Road Vehicle Feeders

2024-01-22T01:35:18Z

OpenTTD Player9876556789:

As of OpenTTD 13.4 (July 2023)
Note: If you opted to set up a Road Vehicle Network earlier on, skip this part.

Trains are great at carrying lots of things far, fast. But what if you find a coal mine making hardly any coal, but close to one of your existing stations? Trains are too expensive for that, at least early on. (Eventually, the industry will increase production to the point that a train makes sense, as long as you "buy" from it, unless you changed some settings, but that takes time.) That's where Road Vehicles come in. Road Vehicles cost a lot less to buy and run, so you hopefully won't loss money.

First find a coal mine close to one of your pickup stations, without much water in between.

[[File:RV_Guide_1.png|x500px|]]

Build a road between the coal mine and the station nearby, as though they were tracks.

[[File:RV_Guide_2.png|x500px|]]

Under Road Vehicles, buy a depot, just like you did with the trains, and put it close to the coal mine.

[[File:RV_Guide_3.png|x500px|]]

Select LORRY station and place down a station touching the train station, or nearby and Ctrl+Place down and select the train station's name. Place down another LORRY station near the coal depot. Then, buy a coal truck.

[[File:RV_Guide_4.png|x500px|]]

Then, give the orders like with the train, only this time use "Transfer and leace empty" at the train station. This makes it so that the train will take the coal afterwards. Then Ctrl+clone the vehicle a few times. You're good to go.

[[File:RV_Guide_5.png|x500px|]]

Watch your trucks head off, and enjoy.

[[File:RV_Guide_6.png|x500px|]]

[[File:RV_Guide_7.png|x500px|]]

File:RV Guide 7.png

2024-01-22T01:28:04Z

OpenTTD Player9876556789: Watching Road Vehicles Version: OpenTTD Stable 13.4

Watching Road Vehicles
Version: OpenTTD Stable 13.4

File:RV Guide 6.png

2024-01-22T01:27:24Z

OpenTTD Player9876556789: Watching RVs Closeup Version: OpenTTD Stable 13.4

Watching RVs Closeup
Version: OpenTTD Stable 13.4

Guide: Road Vehicle Feeders

2024-01-22T01:26:28Z

OpenTTD Player9876556789:

Note: If you opted to set up a Road Vehicle Network earlier on, skip this part.

Trains are great at carrying lots of things far, fast. But what if you find a coal mine making hardly any coal, but close to one of your existing stations? Trains are too expensive for that, at least early on. (Eventually, the industry will increase production to the point that a train makes sense, as long as you "buy" from it, unless you changed some settings, but that takes time.) That's where Road Vehicles come in. Road Vehicles cost a lot less to buy and run, so you hopefully won't loss money.

First find a coal mine close to one of your pickup stations, without much water in between.

Insert photo of coal mine here.

Build a road between the coal mine and the station nearby, as though they were tracks.

Under Road Vehicles, buy a depot, just like you did with the trains, and put it close to the coal mine.

Insert photo with depot and road.

Select LORRY station and place down a station touching the train station, or nearby and Ctrl+Place down and select the train station's name. Place down another LORRY station near the coal depot. Then, buy a coal truck.

Insert photo with two lorry stations and a vehicle.

Then, give the orders like with the train, only this time use "Transfer and leace empty" at the train station. This makes it so that the train will take the coal afterwards. Then Ctrl+clone the vehicle a few times. You're good to go.

Show order page and some cloned vehicles.

Watch your trucks head off, and enjoy.

Insert trucks photo.

File:RV Guide 5.png

2024-01-22T01:25:03Z

OpenTTD Player9876556789: Making Orders and Buying more Vehicles Version: OpenTTD Stable 13.4

Making Orders and Buying more Vehicles
Version: OpenTTD Stable 13.4

File:RV Guide 4.png

2024-01-22T01:23:32Z

OpenTTD Player9876556789: Building a Lorry Station and Buying a Vehicle Version: OpenTTD Stable 13.4

Building a Lorry Station and Buying a Vehicle
Version: OpenTTD Stable 13.4

File:RV Guide 3.png

2024-01-22T01:22:07Z

OpenTTD Player9876556789: Building a Depot Version: OpenTTD Stable 13.4

Building a Depot
Version: OpenTTD Stable 13.4

File:RV Guide 2.png

2024-01-22T01:21:23Z

OpenTTD Player9876556789: Building a Road Version: OpenTTD Stable 13.4

Building a Road
Version: OpenTTD Stable 13.4

File:RV Guide 1.png

2024-01-22T01:20:19Z

OpenTTD Player9876556789: Finding a Coal Mine Version: OpenTTD Stable 13.4

Finding a Coal Mine
Version: OpenTTD Stable 13.4

Main Page/editcopy

2024-01-21T03:22:59Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
| class="frontpage_box" |
==<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>==
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]
</div>
| class="frontpage_box" |
==<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>==
<div style="padding-left: 1em;">
===General===
; [[Orders]] • [[Terraforming]] • [[Logic]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
===Tracks===
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]] • [[Max Curve Speed|Curves (CL)]]
; [[Sideline]]
===[[Signalling]]===
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary - Mergers|Mergers]] • [[Junctionary - City Networks|City Networks]] • [[Junctionary - Logic and Other|Logic and Other]]
;[[Advanced Building Revue|Advanced Building Revue (ABR)]]
</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Main Page/editcopy

2024-01-21T03:21:57Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
| class="frontpage_box" |
==<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>==
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]
</div>
| class="frontpage_box" |
==<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>==
<div style="padding-left: 1em;">
===General===
: [[Orders]] • [[Terraforming]] • [[Logic]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
===Tracks===
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]] • [[Max Curve Speed|Curves (CL)]]
; [[Sideline]]
===[[Signalling]]===
: [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary - Mergers|Mergers]] • [[Junctionary - City Networks|City Networks]] • [[Junctionary - Logic and Other|Logic and Other]]
;[[Advanced Building Revue|Advanced Building Revue (ABR)]]
</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Main Page/editcopy

2024-01-21T03:12:14Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
|| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>
<div style="padding-left: 1em;">
; General
: [[Max Curve Speed|Curves (CL)]] • [[Orders]] • [[Terraforming]] • [[Logic]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]]
; [[Sideline]]
; [[Signalling]]
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary - Mergers|Mergers]] • [[Junctionary - City Networks|City Networks]] • [[Junctionary - Logic and Other|Logic and Other]]
;[[Advanced Building Revue|Advanced Building Revue (ABR)]]
</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Main Page/editcopy

2024-01-21T03:08:12Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Main Page/editcopy

2024-01-21T03:07:12Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-

| class="frontpage_box" |<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Main Page/editcopy

2024-01-21T03:06:14Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
|| class="frontpage_box" |<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Main Page/editcopy

2024-01-21T03:05:16Z

OpenTTD Player9876556789:

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
|| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

User:OpenTTD Player9876556789

2024-01-20T23:23:00Z

OpenTTD Player9876556789:

| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
===[[Obtaining OpenTTD]]===
: [http://nightly.openttd.org Nightly Builds]
===[[Game Start]]===
; [[Planning]]
; [[Moneymaker]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
===OpenTTD Coop Server===
; [[GRF|#openttdcoop GRF Pack]]
; [[Quickstart|Joining a Public Server Game]]
; Server Rules, Guidelines and Glossary
: [[Cooperation]] • [[Ruleset|Building Guidelines]] • [[Communication]] • [[Glossary]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>
<div style="padding-left: 1em;">
; General
: [[Max_Curve_Speed|Curves (CL)]] • [[Orders]] • [[Terraforming]] • [[Logic]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]]
; [[Sideline]]
; [[Signalling]]
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging_Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
-----------

-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
; [[Quickstart]]
; [[Obtaining OpenTTD]]
: [http://nightly.openttd.org Nightly Builds]
: [[GRF|#openttdcoop GRF Pack]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
; [[Cooperation]]
; [[Ruleset|Building Guidelines]]
; [[Communication]]
; [[Glossary]]
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

User:OpenTTD Player9876556789

2024-01-20T23:00:44Z

OpenTTD Player9876556789:

| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>
<div style="padding-left: 1em;">
; General
: [[Max_Curve_Speed|Curves (CL)]] • [[Orders]] • [[Terraforming]] • [[Logic]]
: [[Game_types|Game types]] • [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]]
; [[Sideline]]
; [[Signalling]]
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging_Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
-----------

-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
; [[Quickstart]]
; [[Obtaining OpenTTD]]
: [http://nightly.openttd.org Nightly Builds]
: [[GRF|#openttdcoop GRF Pack]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
; [[Cooperation]]
; [[Ruleset|Building Guidelines]]
; [[Communication]]
; [[Glossary]]
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

User:OpenTTD Player9876556789

2024-01-20T22:57:35Z

OpenTTD Player9876556789:

| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>
<div style="padding-left: 1em;">
; General
: [[Max_Curve_Speed|Curves (CL)]] • [[Orders]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]]
; [[Sideline]]
; [[Signalling]]
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations, Junctions, and Designs</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]] • [[Refit]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging_Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
;Other
: [[Terraforming]]
: [[Game_types|Game types]] • [[Cargo]] • [[PAX]] • [[Chaos]]
: [[Logic]]
-----------

-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
; [[Quickstart]]
; [[Obtaining OpenTTD]]
: [http://nightly.openttd.org Nightly Builds]
: [[GRF|#openttdcoop GRF Pack]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
; [[Cooperation]]
; [[Ruleset|Building Guidelines]]
; [[Communication]]
; [[Glossary]]
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

User:OpenTTD Player9876556789

2024-01-20T22:55:44Z

OpenTTD Player9876556789:

| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Trains, Tracks, and Signals</div>
<div style="padding-left: 1em;">
; General
: [[Max_Curve_Speed|Curves (CL)]] &bull : [[Orders]] • [[Refit]]
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]]
; [[Sideline]]
; [[Signalling]]
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations, Junctions, and Designs</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging_Tracks|Merging Tracks]]
; [[Junctionary|Junctionary (Design Examples)]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
;Other
: [[Terraforming]]
: [[Game_types|Game types]] • [[Cargo]] • [[PAX]] • [[Chaos]]
: [[Logic]]
-----------

-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
; [[Quickstart]]
; [[Obtaining OpenTTD]]
: [http://nightly.openttd.org Nightly Builds]
: [[GRF|#openttdcoop GRF Pack]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
; [[Cooperation]]
; [[Ruleset|Building Guidelines]]
; [[Communication]]
; [[Glossary]]
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

User:OpenTTD Player9876556789

2024-01-20T22:50:55Z

OpenTTD Player9876556789: Created page with "| class="frontpage_box" | <div class="frontpage_bar"><div style="float: right;">*</div>Tracks and Signals</div> <div style="padding-left: 1em;"> ; General : Max_Cu..."

| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Tracks and Signals</div>
<div style="padding-left: 1em;">
; General
: [[Max_Curve_Speed|Curves (CL)]] &bull
; [[Line hierarchy|Network Design]]
: [[SRNW|Self Regulated Network]]
; [[Mainline]]
: [[SML|Shift Mainline]] • [[Priority]]
; [[Sideline]]
; [[Signalling]]
; [[Guides:Presignals|Pre-signals]] • [[Two-way-Signals|Two way signals]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Stations and Junctions</div>
<div style="padding-left: 1em;">
; Stations
: [[Main station|Main stations]] • [[Sideline#Sideline stations|Sideline stations]] • [[Road stations]]
; Junctions (Hubs)
: [[BBH|Backbone Hub]] • [[Sideline Hub]] • [[MSH|Main Station Hub]] • [[Merging_Tracks|Merging Tracks]]
; [[Junctionary]]
: [[Junctionary - BBHs|Backbone Hub]] • [[Junctionary - SLHs|Sideline Hub]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]

-----------
: [[Orders]] • [[Refit]]
: [[Terraforming]]
: [[Game_types|Game types]] • [[Cargo]] • [[PAX]] • [[Chaos]]
; [[Logic|Logic]]

-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
; [[Quickstart]]
; [[Obtaining OpenTTD]]
: [http://nightly.openttd.org Nightly Builds]
: [[GRF|#openttdcoop GRF Pack]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
; [[Cooperation]]
; [[Ruleset|Building Guidelines]]
; [[Communication]]
; [[Glossary]]
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

Main Page/editcopy

2024-01-20T22:06:20Z

OpenTTD Player9876556789: Syncing with the Main Page

__NOTOC__
{| style="width: 100%;" cellspacing="5" cellpadding="0"
| colspan="3" | <div style="width: 75%; margin: auto; background:#f5faff; border: 1px solid #AAA;"><div style="background:#f5faff; border: 1px solid #7BC; padding: 5px; margin: 3px; font-weight: bold; text-align: center;">
Welcome to the #openttdcoop wiki,<br>the definitive source for cooperative building and design of transportation networks.</div></div>



|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Getting Started</div>
<div style="padding-left: 1em;">
; [[Quickstart]]
; [[Obtaining OpenTTD]]
: [http://nightly.openttd.org Nightly Builds]
: [[GRF|#openttdcoop GRF Pack]]
; [[Tutorial Savegame|#openttdcoop Tutorial]]
: [http://www.openttdcoop.org/wiki/images/6/6a/Tutorial.sav Download Savegame]
: [[Tutorial Savegame Mainline|Mainline]] • [[Tutorial Savegame Sideline|Sideline]]
: [[Tutorial Savegame Stations|Stations]] • [[Tutorial Savegame Feeder|Feeder]] • [[Tutorial Savegame Towns|Towns]]
; [[Cooperation]]
; [[Ruleset|Building Guidelines]]
; [[Communication]]
; [[Glossary]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Basic Building Concepts</div>
<div style="padding-left: 1em;">
; [[Game Start]]
: [[Planning]] • [[Moneymaker]]
; [[Line hierarchy|Basic Networking]]
: [[Mainline]] • [[Sideline]] • [[Signalling]]
: [[SLH]] • [[Priority]]
: [[Road stations]]
; [[Guides:Presignals|Pre-signals]] • [[Max_Curve_Speed|Curves (CL)]]
; [[Terraforming]]
; [[Orders]]
: [[Copy orders|Copying Orders]] • [[Shared Orders]]
; [[Game_types|Game types]]
: [[Cargo]] • [[PAX]] • [[Chaos]] • [[Refit]] • [[SRNW]] • [[SML]]

</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Advanced Building Concepts</div>
<div style="padding-left: 1em;">
; [[Junctionary]]
: [[Junctionary - BBHs|BBH]] • [[Junctionary - SLHs|SLH]] • [[Junctionary - Stations|Stations]] • [[Junctionary_-_Mergers|Mergers]] • [[Junctionary_-_City_Networks|City Networks]] • [[Junctionary_-_Logic_and_Other|Logic and Other]]
; [[:Category:Advanced Networking|Advanced Networking]]
: [[BBH]] • [[Main station|Main stations]] • [[MSH]] • [[Merging_Tracks|Merging Tracks]]
; [[Shift_Mainlines|SML (Shift Mainlines)]]
; [[Self-regulating Network]]s
; [[Sbahn|S-Bahns]]
; [[Two-way-Signals|Two way signals]]
; [[Logic|Logic]]
;

[[Advanced_Building_Revue|Advanced Building Revue (ABR)]]

</div>
|-
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Technical Info</div>
<div style="padding-left: 1em;">
; [[Servers|#openttdcoop Servers]]
: [[Public Server | (PS) Public Server]] ([[PublicServer:Archive|Archive]])
: [[Pro Zone | (PZ) ProZone Server]] ([[ProZone:Archive|Archive]])
: [[Member Zone| (MZ) Member Server]] ([[MemberZone:Archive|Archive]])
: [[Coopetition|Coopetition Server]] • [[Dev Server|Patched Server]]
; [[IRC]]
: [[IRC Commands]] • [[IRC Highlighting]]
; [[Teamspeak]]
; [[GRF|#openttdcoop GRF Pack]]
: [[GRF Table Current|Current GRF Table]] • [[GRF History|Version History]]
: [[GRF Dev Guide|Development Guide]] • [[GRF Table (Trunk)|Development Table]]
; [[Server Administration]] • [[Autopilot]] • [[Autostart]]
; [[Soap]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Development</div>
<div style="padding-left: 1em;">
; [[Gametypes]]
: [[Gametype:ICE SBahn|ICE/SBahn]] • [[Gametype:Chaos Theory|Chaos]] • [[Gametypes|more...]]
: [[Game Proposals|Proposals for Future Gametypes]]
; [[Map Preparation| Preparing good maps]] | [[Premade Scenarios| Proposed and prepared future games]]
; [[:Category:Coopetition|Coopetition]]
; [[OSQC|Scenario Quest/Competition (OSQC)]]
; [[WWOTTDGD|WorldWide OpenTTD Game Day (WWOTTDGD)]]
; [[Webbased configurator | Web-based Configurator]]
; [[:Category:Research|Current Research Projects]]
</div>
| class="frontpage_box" |
<div class="frontpage_bar"><div style="float: right;">[[Image|*]]</div>Community Info</div>
<div style="padding-left: 1em;">
We are maintaining [[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:Allpages|articles]]!<br />
<span style="margin-left: 2em;"><small>See...[[Special:Recentchanges|Recent changes]] | [[Special:Newpages|New pages]] | [[Special:Wantedpages|Missing pages]]</small></span>
; [http://www.openttdcoop.org/blog #openttdcoop Blog]
; [[Membership|Becoming an #openttdcoop Member]]
: Join the cooperative building community!
; [[Users|User List]]
: See the list of current members and active players
; [[History|History of #openttdcoop]]
; [[Contact|Contact Info]]
; [[#openttdcoop Wiki:Sandbox|Sandbox]]
</div>
|}

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Changes for the main page can be proposed [[Main Page/editcopy|here]].</div>

Chaos

2024-01-20T22:01:47Z

OpenTTD Player9876556789:

Chaos games can consist of pretty much anything, but generally it is an organically growing network which just gets messier and messier over time, eventually resulting in a rebuild and then getting messier again. A lot of chaos viabilty depends on which parts of the plan do you specify and which you leave as free or "up to builders".
Generally chaos is only used on the ProZone where people have at least some basic habits of our building style so we can expect what they would build.
The idea behind Chaos is to make a more realistic build up of the network where you don't have a Mainline with hardly any trains on it right after the Plan is chosen.

{{Archive_ExamplePS|PSG 90|90|This is how it ends when the plans answers all questions: Any. A nice relaxing game overall.|[[File:PSG90plan.png|200px]]}}
{{Archive_ExamplePS|PSG 166|166|Another chaos game which ended up quite nicely as the ML structured quite quickly.|[[File:PSG166plan.png|200px]]}}
{{Archive_ExamplePS|PSG 181|181|Here we experienced what it means to have a total mess on our network, but then we rebuilt vast majority of it, which let us to play the game some more. As there was no planned ML structure, we could add various hubs and create new connections which helped us handle the situation. Amazing output of chaos for a lot of effort and fun while building.|[[File:PSG181plan.png|200px]]}}
{{Archive_ExamplePS|PSG 231|231|What is a better way to test a new train set than having a random chaos game?|[[File:PSG231plan.png|200px]]}}

Orders

2024-01-20T21:58:11Z

OpenTTD Player9876556789:

{{update|Everything, Read talk page}}

[[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 train that carries both passengers and mail, with full load any cargo the train will keep loading until either passengers or mail has reached 100% then continue to the next order. This keeps an train full of passengers from waiting at the station waiting for more mail to fill up the train. 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. Note: If this order is applied to an airplane carrying both passengers and mail, "Full load any cargo" will wait until the passengers are fully loaded. In other words, the plane will wait for passengers even if the plane is carrying all the mail it can. This is true as of 2011.
* '''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.(verify, possibly stays in station.) This unload order will append "(Unload and <load order>)" to the orders list, where <load> is the load order. By default, adding the "Unload all" order will make the loading status "No Loading", displaying "Unload all and Leave Empty".
*'''Transfer'''- This unload order tells the vehicle to unload all cargo, regardless of station acceptance. Unlike "Unload all", all the cargo stays in the station, even if the cargo is accepted and would normally go directly to an industry. in addition, it will create "[[Digital Income]]". This unload order appends "(Transfer and <load order>)" to the orders list, where <load> is the load order. By default, adding the "Transfer" order will make the loading status "No Loading", displaying "Transfer and Leave Empty".
*'''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 RVs 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 RVs will go to without stopping 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 are 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 performs 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 go to 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, is 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 train's orders 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 that 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 practical 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 unload all cargo that it has to the station, collect it's "[[Digital Income|virtual money]]" for the distance(s) that the cargo has traveled, and to load cargo until either the train is full or there is no more cargo waiting to load. Sometimes, this means loading the same cargo it just unloaded. However, this could be useful in NewGRF Industry sets like FIRS to give small amounts of cargo to each Primary Industry. See [[Reverse Feeder]]
* '''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 unload all cargo that it has to the station, collect it's "virtual money" for the distance(s) that the cargo has traveled, and load cargo until the train is full. Sometimes, this means loading the same cargo it just unloaded.
* '''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 unload all cargo that it has to the station, collect it's "virtual money" for the distance(s) that the cargo has traveled, and to load cargo until any accepted cargo is full. Sometimes, this means loading the same cargo it just unloaded.
* '''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 No Unloading 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 order 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]]

change the photo, no unloading makes more sense than transfer sometimes.

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

==Copy orders==

It's useful to copy orders if you have vehicles that all have the same route. For example you have 10 airplanes and have to set them to 10 airfields. It's boring to look for the airfields over and over again.

To copy the orders of a vehicle you simple click on "Go To" in the orders screen (Note: The vehicle must have no orders on that moment) and click on the vehicle where you want to copy the orders from.

==Shared orders==
''
(This is just a copy of the page at the OpenTTD Wiki. At #openttdcoop, we ALWAYS use shared orders!)''

You probably already know how to [[Orders#Copy orders|copy orders]]. The 'problem' with copying orders is that although all such vehicles have the same orders, they are all independent from each other. So if you would like to add another station to a particular group of buses servicing Chudingstone Bay (Fig 1.) for example, you would have to go through each bus and change that particular order for all of them.

===There must be an easier way, right?===
Yes there is an easier way. A way that also is more advanced, difficult, but also a lot more powerful.
We will use the example in the picture below (Fig 1.). Once again, start giving out orders as you would normally for Bus#3. Nothing special has happened so far.

#Select Bus#4, and click on '''''Go To'''''.
#Hold down '''''CTRL''''' and click on Bus#3.
#Now the two buses ''share'' the same schedule; they are linked together.

You will see 2 things happen. First all Bus#4 will get the whole schedule from Bus#3, just as in [[Guides:Glossary:Copy orders|copy orders]]. Secondly, you will see that '''''"- - End of Orders - -"''''' has been changed to '''''"- - End of <u>Shared</u> Orders - -"''''' for both buses. This is your proof that the schedule of the 2 vehicles are now linked together.

<center>[[Image:shared-orders.png|center|none|frame|Fig 1. - The schedule of the 2 buses have been ''linked'' together]]</center>

===Wow cool, can you tell me more about it?===
You can link together as many vehicles as you want, there is no limit. Of course you can only link buses together with buses, trains together with trains, etc. etc.
Having the schedule list linked together opens up some nice possibilities.
*If you want to update the schedule for that whole group of vehicles, you only have to do it for one. Since they are all linked together, all others will also get the new schedule. This includes adding orders, as well as removing them.
Well, that's about it. But it saves you a lot of clicking and time-wasting that you could better use for expanding your world-domination conglomerate.

===How do I get rid of these Shared Orders?===
It is possible that you would like a vehicle that has shared orders removed from the share and reset its schedule. The service might not pay enough, you might want to open a new line, etc. Do the following:
#Open the '''''Orders Window''''' of the vehicle you want to remove from the share.
#Click on the last line, the one that says '''''"- - End of Shared Orders - -"'''''
#Press the '''Delete''' button.
You will see that all orders are removed from the schedule of that vehicle, and now the last line says '''''"- - End of <u>Orders</u> - -"'''''. All other previously linked vehicles are unaffected by this change. Only our target vehicle has been removed. You can now control its schedule independently from all other vehicles as you would normally do without this fancy stuff.

===Various Tidbits===
*When trying to remove a vehicle from a shared schedule, don't be tempted to just delete all its orders as you normally would for deleting destinations. This will cause all linked vehicles to lose their orders and that was probably not the intention. Use the method described the just above paragraph.
*Sharing orders is also possible for vehicles that already have an existing schedule. To share orders you must hold down the "'''CTRL'''", thus you cannot accidentally lose the target vehicle's schedule. When doing so the vehicle will lose all of its orders, and only have the linked one. Something to keep in mind perhaps.

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

Orders

2024-01-20T21:54:05Z

OpenTTD Player9876556789:

{{update|Everything, Read talk page}}

[[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 train that carries both passengers and mail, with full load any cargo the train will keep loading until either passengers or mail has reached 100% then continue to the next order. This keeps an train full of passengers from waiting at the station waiting for more mail to fill up the train. 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. Note: If this order is applied to an airplane carrying both passengers and mail, "Full load any cargo" will wait until the passengers are fully loaded. In other words, the plane will wait for passengers even if the plane is carrying all the mail it can. This is true as of 2011.
* '''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.(verify, possibly stays in station.) This unload order will append "(Unload and <load order>)" to the orders list, where <load> is the load order. By default, adding the "Unload all" order will make the loading status "No Loading", displaying "Unload all and Leave Empty".
*'''Transfer'''- This unload order tells the vehicle to unload all cargo, regardless of station acceptance. Unlike "Unload all", all the cargo stays in the station, even if the cargo is accepted and would normally go directly to an industry. in addition, it will create "[[Digital Income]]". This unload order appends "(Transfer and <load order>)" to the orders list, where <load> is the load order. By default, adding the "Transfer" order will make the loading status "No Loading", displaying "Transfer and Leave Empty".
*'''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 RVs 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 RVs will go to without stopping 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 are 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 performs 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 go to 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, is 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 train's orders 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 that 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 practical 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 unload all cargo that it has to the station, collect it's "[[Digital Income|virtual money]]" for the distance(s) that the cargo has traveled, and to load cargo until either the train is full or there is no more cargo waiting to load. Sometimes, this means loading the same cargo it just unloaded. However, this could be useful in NewGRF Industry sets like FIRS to give small amounts of cargo to each Primary Industry. See [[Reverse Feeder]]
* '''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 unload all cargo that it has to the station, collect it's "virtual money" for the distance(s) that the cargo has traveled, and load cargo until the train is full. Sometimes, this means loading the same cargo it just unloaded.
* '''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 unload all cargo that it has to the station, collect it's "virtual money" for the distance(s) that the cargo has traveled, and to load cargo until any accepted cargo is full. Sometimes, this means loading the same cargo it just unloaded.
* '''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 No Unloading 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 order 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]]

change the photo, no unloading makes more sense than transfer sometimes.

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

==Copy orders==

It's useful to copy orders if you have vehicles that all have the same route. For example you have 10 airplanes and have to set them to 10 airfields. It's boring to look for the airfields over and over again.

To copy the orders of a vehicle you simple click on "Go To" in the orders screen (Note: The vehicle must have no orders on that moment) and click on the vehicle where you want to copy the orders from.

==Shared orders==

(This is just a copy of the page at the Openttd Wiki. At #openttdcoop, we ALWAYS use shared orders!)

You probably already know how to [[Orders#Copy orders|copy orders]]. The 'problem' with copying orders is that although all such vehicles have the same orders, they are all independent from each other. So if you would like to add another station to a particular group of buses servicing Chudingstone Bay (Fig 1.) for example, you would have to go through each bus and change that particular order for all of them.

===There must be an easier way, right?===
Yes there is an easier way. A way that also is more advanced, a bit more difficult, but also a lot more powerful.
We will use the example in the picture below (Fig 1.). Once again, start giving out orders as you would normally for Bus#3. Nothing special has happened so far.

#Select Bus#4, and click on ''Go To'''.
#Hold down ''CTRL''' and click on Bus#3.
#Now the two buses ''share'' the same schedule; they are linked together.

You will see 2 things happen. First all Bus#4 will get the whole schedule from Bus#3, just as in [[Guides:Glossary:Copy orders|copy orders]]. Secondly, you will see that "- - End of Orders - -" has been changed to '''''"- - End of <u>Shared</u> Orders - -"''''' for both buses. This is your proof that the schedule of the 2 vehicles are now linked together.

<center>[[Image:shared-orders.png|center|none|frame|Fig 1. - The schedule of the 2 buses have been ''linked'' together]]</center>

===Wow cool, can you tell me more about it?===
You can link together as many vehicles as you want, there is no limit. Of course you can only link buses together with buses, trains together with trains, etc. etc.
Having the schedule list linked together opens up some nice possibilities.
*If you want to update the schedule for that whole group of vehicles, you only have to do it for one. Since they are all linked together, all others will also get the new schedule. This includes adding orders, as well as removing them.
Well, that's about it. But it saves you a lot of clicking and time-wasting that you could better use for expanding your world-domination conglomerate.

===How do I get rid of these Shared Orders?===
It is possible that you would like a vehicle that has shared orders removed from the share and reset its schedule. The service might not pay enough, you might want to open a new line, etc. Do the following:
#Open the '''''Orders Window''''' of the vehicle you want to remove from the share.
#Click on the last line, the one that says '''''"- - End of Shared Orders - -"'''''
#Press the '''Delete''' button.
You will see that all orders are removed from the schedule of that vehicle, and now the last line says '''''"- - End of <u>Orders</u> - -"'''''. All other previously linked vehicles are unaffected by this change. Only our target vehicle has been removed. You can now control its schedule independently from all other vehicles as you would normally do without this fancy stuff.

===Various Tidbits===
*When trying to remove a vehicle from a shared schedule, don't be tempted to just delete all its orders as you normally would for deleting destinations. This will cause all linked vehicles to lose their orders and that was probably not the intention. Use the method described the just above paragraph.
*Sharing orders is also possible for vehicles that already have an existing schedule. To share orders you must hold down the "'''CTRL'''", thus you cannot accidentally lose the target vehicle's schedule. When doing so the vehicle will lose all of its orders, and only have the linked one. Something to keep in mind perhaps.

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

Orders

2024-01-20T21:21:24Z

OpenTTD Player9876556789:

{{update|Everything, Read talk page}}

[[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 train that carries both passengers and mail, with full load any cargo the train will keep loading until either passengers or mail has reached 100% then continue to the next order. This keeps an train full of passengers from waiting at the station waiting for more mail to fill up the train. 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. Note: If this order is applied to an airplane carrying both passengers and mail, "Full load any cargo" will wait until the passengers are fully loaded. In other words, the plane will wait for passengers even if the plane is carrying all the mail it can. This is true as of 2011.
* '''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.(verify, possibly stays in station.) This unload order will append "(Unload and <load order>)" to the orders list, where <load> is the load order. By default, adding the "Unload all" order will make the loading status "No Loading", displaying "Unload all and Leave Empty".
*'''Transfer'''- This unload order tells the vehicle to unload all cargo, regardless of station acceptance. Unlike "Unload all", all the cargo stays in the station, even if the cargo is accepted and would normally go directly to an industry. in addition, it will create "[[Digital Income]]". This unload order appends "(Transfer and <load order>)" to the orders list, where <load> is the load order. By default, adding the "Transfer" order will make the loading status "No Loading", displaying "Transfer and Leave Empty".
*'''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 RVs 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 RVs will go to without stopping 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 are 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 performs 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 go to 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, is 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 train's orders 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 that 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 practical 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 unload all cargo that it has to the station, collect it's "[[Digital Income|virtual money]]" for the distance(s) that the cargo has traveled, and to load cargo until either the train is full or there is no more cargo waiting to load. Sometimes, this means loading the same cargo it just unloaded. However, this could be useful in NewGRF Industry sets like FIRS to give small amounts of cargo to each Primary Industry. See [[Reverse Feeder]]
* '''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 unload all cargo that it has to the station, collect it's "virtual money" for the distance(s) that the cargo has traveled, and load cargo until the train is full. Sometimes, this means loading the same cargo it just unloaded.
* '''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 unload all cargo that it has to the station, collect it's "virtual money" for the distance(s) that the cargo has traveled, and to load cargo until any accepted cargo is full. Sometimes, this means loading the same cargo it just unloaded.
* '''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]]

change the photo, no unloading makes more sense than transfer sometimes.

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.

==Copy orders==

It's useful to copy orders if you have vehicles that all have the same route. For example you have 10 airplanes and have to set them to 10 airfields. It's boring to look for the airfields over and over again.

To copy the orders of a vehicle you simple click on Go To in the orders screen ''(Note: The vehicle must have no orders on that moment)'' and click on the vehicle where you want to copy the orders from.

==Shared orders==
''
(This is just a copy of the page at the openttd wiki. At #openttdcoop, we ALWAYS use shared orders!)''

You probably already know how to [[Orders#Copy orders|copy orders]]. The 'problem' with copying orders is that although all such vehicles have the same orders, they are all independent from each other. So if you would like to add another station to a particular group of buses servicing Chudingstone Bay (Fig 1.) for example, you would have to go through each bus and change that particular order for all of them.

===There must be an easier way, right?===
Yes there is an easier way. A way that also is more advanced, difficult, but also a lot more powerful.
We will use the example in the picture below (Fig 1.). Once again, start giving out orders as you would normally for Bus#3. Nothing special has happened so far.

#Select Bus#4, and click on '''''Go To'''''.
#Hold down '''''CTRL''''' and click on Bus#3.
#Now the two buses ''share'' the same schedule; they are linked together.

You will see 2 things happen. First all Bus#4 will get the whole schedule from Bus#3, just as in [[Guides:Glossary:Copy orders|copy orders]]. Secondly, you will see that '''''"- - End of Orders - -"''''' has been changed to '''''"- - End of <u>Shared</u> Orders - -"''''' for both buses. This is your proof that the schedule of the 2 vehicles are now linked together.

<center>[[Image:shared-orders.png|center|none|frame|Fig 1. - The schedule of the 2 buses have been ''linked'' together]]</center>

===Wow cool, can you tell me more about it?===
You can link together as many vehicles as you want, there is no limit. Of course you can only link buses together with buses, trains together with trains, etc. etc.
Having the schedule list linked together opens up some nice possibilities.
*If you want to update the schedule for that whole group of vehicles, you only have to do it for one. Since they are all linked together, all others will also get the new schedule. This includes adding orders, as well as removing them.
Well, that's about it. But it saves you a lot of clicking and time-wasting that you could better use for expanding your world-domination conglomerate.

===How do I get rid of these Shared Orders?===
It is possible that you would like a vehicle that has shared orders removed from the share and reset its schedule. The service might not pay enough, you might want to open a new line, etc. Do the following:
#Open the '''''Orders Window''''' of the vehicle you want to remove from the share.
#Click on the last line, the one that says '''''"- - End of Shared Orders - -"'''''
#Press the '''Delete''' button.
You will see that all orders are removed from the schedule of that vehicle, and now the last line says '''''"- - End of <u>Orders</u> - -"'''''. All other previously linked vehicles are unaffected by this change. Only our target vehicle has been removed. You can now control its schedule independently from all other vehicles as you would normally do without this fancy stuff.

===Various Tidbits===
*When trying to remove a vehicle from a shared schedule, don't be tempted to just delete all its orders as you normally would for deleting destinations. This will cause all linked vehicles to lose their orders and that was probably not the intention. Use the method described the just above paragraph.
*Sharing orders is also possible for vehicles that already have an existing schedule. To share orders you must hold down the "'''CTRL'''", thus you cannot accidentally lose the target vehicle's schedule. When doing so the vehicle will lose all of its orders, and only have the linked one. Something to keep in mind perhaps.

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

Guide: Road Vehicle Feeders

2024-01-20T07:21:57Z

OpenTTD Player9876556789: Created page with "Note: If you opted to set up a Road Vehicle Network earlier on, skip this part. Trains are great at carrying lots of things far, fast. But what if you find a coal mine making..."

Note: If you opted to set up a Road Vehicle Network earlier on, skip this part.

Trains are great at carrying lots of things far, fast. But what if you find a coal mine making hardly any coal, but close to one of your existing stations? Trains are too expensive for that, at least early on. (Eventually, the industry will increase production to the point that a train makes sense, as long as you "but" from it, unless you changed some settings, but that takes time.) That's where Road Vehicles come in. Road Vehicles cost a lot less to buy and run, so you hopefully won't loss money.

First find a coal mine close to one of your pickup stations, without much water in between.

Insert photo of coal mine here.

Build a road between the coal mine and the station nearby, as though they were tracks.

Under Road Vehicles, buy a depot, just like you did with the trains, and put it close to the coal mine.

Insert photo with depot and road.

Select LORRY station and place down a station touching the train station, or nearby and Ctrl+Place down and select the train station's name. Place down another LORRY station near the coal depot. Then, buy a coal truck.

Insert photo with two lorry stations and a vehicle.

Then, give the orders like with the train, only this time use "Transfer and leace empty" at the train station. This makes it so that the train will take the coal afterwards. Then Ctrl+clone the vehicle a few times. You're good to go.

Show order page and some cloned vehicles.

Watch your trucks head off, and enjoy.

Insert trucks photo.

Guide

2024-01-20T06:58:57Z

OpenTTD Player9876556789:

Work In Progress
This is a Guide, going from the very basics to advanced constructions. The guide is based on a coal train start, but includes other features over time.

IMPORTANT: These are guides. Other ways of building something are on the revlant page.

[[Guide: Getting Started]] (Entire page copied from OpenTTD wiki website.)

[[Guide: Road Vehicle Feeders]]-How to supply low production Industries without trains.

[[Guide: Creating a basic Ro-Ro Station]]-Increasing throughput at the power plant.

[[Guide: Your first Mainline]]-Reducing unnecessary slowdowns.

[[Guide: Priorities on your Mainline merges]]-Approaching a free-flowing Mainline.

[[Guide: Introducing the Main Station Hub]]-No station queues, all day, every day.

[[Guide: What's Next?]]-What to learn next, and how to go deeper into what you learned.

Note to editors: include other industries, SRNWs, Overflows, Passengers, Mail, and Secondary Processing, Sidelines, etc.

*Except for small stations and if you don't flood stations, which makes sense sometimes.

Guide

2024-01-20T06:58:02Z

OpenTTD Player9876556789:

Work In Progress
This is a Guide, going from the very basics to advanced constructions. The guide is based on a coal train start, but includes other features over time.

IMPORTANT: These are guides. Other ways of building something are on the revlant page.

[[Guide: Getting Started]] (Entire page copied from OpenTTD wiki website.)
[[Guide: Road Vehicle Feeders]]-How to supply low production Industries without trains.
[[Guide: Creating a basic Ro-Ro Station]]-Increasing throughput at the power plant.
[[Guide: Your first Mainline]]-Reducing unnecessary slowdowns.
[[Guide: Priorities on your Mainline merges]]-Approaching a free-flowing Mainline
[[Guide: Introducing the Main Station Hub]]-No station queues, all day, every day
[[Guide: What's Next?]]-What to learn next, and how to go deeper into what you learned.
Note to editors: include other industries, SRNWs, Overflows, Passengers, Mail, and Secondary Processing, etc.

*Except for small stations and if you don't flood stations, which makes sense sometimes.

Guide

2024-01-20T06:50:30Z

OpenTTD Player9876556789: Created page with "Work In Progress This is a Guide, going from the very basics to advanced constructions. The guide is based on a coal train start, but includes other features over time. IMPOR..."

Work In Progress
This is a Guide, going from the very basics to advanced constructions. The guide is based on a coal train start, but includes other features over time.

IMPORTANT: These are guides. Other ways of building something are on the revlant page.

Guide: Getting Started (Entire page copied from OpenTTD wiki website.)
Guide: Road Vehicle Feeders-How to supply low production Industries without trains.
Guide: Creating a basic Ro-Ro Station-Increasing throughput at the power plant.
Guide: Your first Mainline-Reducing unnecessary slowdowns.
Guide: Priorities on your Mainline merges-Approaching a free-flowing network
Guide: Introducing the Main Station Hub-On time trains, all day, every day.*
Guide: What's Next?-What to learn next, and how to go deeper into what you learned.

*On your Mainlines.

JGR

2024-01-20T06:30:19Z

OpenTTD Player9876556789: Created page with "The OpenTTD JGR Patch Pack (JGRPP) is a patch pack that makes advanced constructions like Logic, Penalties, Priorities, SRNWs, etc. much easier."

The OpenTTD JGR Patch Pack (JGRPP) is a patch pack that makes advanced constructions like Logic, Penalties, Priorities, SRNWs, etc. much easier.