Orders - Revision history

OpenTTD Player9876556789 at 21:58, 20 January 2024

2024-01-20T21:58:11Z

OpenTTD Player9876556789 at 21:54, 20 January 2024

2024-01-20T21:54:05Z

OpenTTD Player9876556789 at 21:21, 20 January 2024

2024-01-20T21:21:24Z

Antimarvin: /* Go Orders */

2019-10-11T16:06:07Z

‎Go Orders

Benny: Added {{update}}

2013-12-04T07:18:27Z

Added {{update}}

Benny: Link fix

2013-12-03T14:26:39Z

Link fix

Benny: Merged with Shared orders and Copy orders

2013-12-03T14:24:12Z

Merged with Shared orders and Copy orders

Benny: proposed merge

2013-11-07T12:13:02Z

proposed merge

Bodo Thiesen: improved inter guides linking

2010-07-19T16:04:29Z

improved inter guides linking

Andyp: finished transfer section

2009-03-08T07:18:54Z

finished transfer section

@@ Line 86: / Line 86: @@
 ==Shared orders==
+''
-(This is just a copy of the page at the Openttd Wiki. At #openttdcoop, we ALWAYS use 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.
+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'''.
+#Select Bus#4, and click on '''''Go To'''''.
-#Hold down ''CTRL''' and click on Bus#3.
+#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.
+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>

@@ Line 69: / Line 69: @@
 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:
+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]]
@@ Line 75: / Line 75: @@
 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.
+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.
@@ Line 82: / Line 82: @@
 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.
+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!)''
+(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.
+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'''''.
+#Select Bus#4, and click on ''Go To'''.
-#Hold down '''''CTRL''''' and click on Bus#3.
+#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.
+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>

@@ Line 23: / Line 23: @@
 * '''Load if available''' - The default load order.  This order is not explicitly listed in the orders list so unless one of the other three load orders is present, this is the load order that the vehicle will use.  When a vehicle stops at a station it will load all waiting cargo of any type that it can accept.  The train will keep loading until it is either 100% full, or there is no cargo at the station to load.
 * '''Full load all cargo''' - This load order tells the vehicle to stay at the station and load until it has reached 100% total cargo capacity.  This load order will append "(Full load)" to the order.
-* '''Full load any cargo''' - This load order tells the vehicle to stay at the station any load until any single cargo type that the vehicle accepts has reached 100%.  An example would be an airplane that carries both passengers and mail, with full load any cargo the airplane will keep loading until either passengers or mail has reached 100% then continue to the next order.  This keeps an airplane full of passengers from sitting on the tarmac waiting for more mail to fill up the airplane.  This order can be useful anywhere that vehicles can carry multiple cargo types.  This load order will append "(Full load any cargo)" to the order.
+* '''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.
+* '''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.
@@ Line 31: / Line 31: @@
 An unload order tells a vehicle what to do with any cargo it may have.
 *'''Unload if accepted'''- The default unload order.  This order is not explicitly listed in the orders list so unless one of the other three unload orders is present, this is the unload order that the vehicle will use.  When a vehicle stops at a station it will unload any cargo that it is carrying that is also accepted by the station.
-*'''Unload all'''- This unload order tells the vehicle to unload all cargo, regardless of station acceptance.  Any non accepted cargo will disappear.  This unload order will append "(Unload and <load order>)" to the orders list, where <load> is the load order.
+*'''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 is explained later this page.  This unload order appends "(Transfer and <load order>)" to the orders list, where <load> is the load order.
+*'''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.
@@ Line 55: / Line 55: @@
 When building multiple stations that are meant to be serviced by one train (or multiple trains sharing orders) you might need to use transfer orders. This kind of orders allow vehicles to keep cargo in the train and allow trains to unload all cargo at a station without loosing money. Transfer orders use virtual money this means that vehicles earn money so they don't show up as making a loss but the money won't be added to the bank balance. This is extremely usefull for making feeders.
 There are four kinds of transfer orders:
-* '''Transfer and take cargo''' - the combination of the "Transfer" unload order, with the "Load if available" load order.  This order tells a vehicle to keep any cargo it has, and to load cargo until either the train is full or there is no more cargo waiting to load.
+* '''Transfer and 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 keep any cargo it has, and to load cargo until the train is full.
+* '''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 keep any cargo it has, and to load cargo until any accepted cargo is full.
+* '''Transfer and wait for any full load''' - the combination of the "Transfer" unload order with  the "Full load any cargo" load order.  This order tells a vehicle to 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.
@@ Line 72: / Line 72: @@
 [[Image:Transfer_orders.png]]
 These kind of orders are very usefull when working with SBahn and must be used when working with SBahn rings with 3 stations or more.

@@ Line 38: / Line 38: @@
 ==Go Orders==
-Go orders are only available to trains and road vehicles(RV's).  By default trains and RV's will stop at each station they pass through.  Go orders can modify this behavior.  The go order will immediately precede the station name in the orders list.
+Go 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 via'''- Trains and RV's will go to, and continue through the station in the order without stopping.  They will, however, stop at any other stations they encounter.  This order has the same functionality as waypoints.  This order may have usefulness as a waypoint on a [[Self-regulating Network]], after the loading stations, otherwise, the go non-stop via is preferred on the public server.
-*'''Go non-stop via'''- With this order trains and RV's will go to without stoping at any station, and continue through the station in the order without stopping.  This effectively turns stations into waypoints.  The benefits of using stations as waypoints is that they can be built across several tracks, and thereby serve as a single waypoint across all (or only some if so desired) tracks of a ML.  This preforms the same as waypoints with non-stop orders, and as station waypoints with the old TTDPatch non-stop compatible handling.
+*'''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:
@@ Line 48: / Line 48: @@
 [[Image:Orders1.png]]
-The first order has the "Full load all cargo" load order, the second order has the "No loading" load order, and both orders have the "Go non-stop to" order.  So the train will goto the station Sleningville Mines without stopping at any other station it may encounter on the way.  It will unload any accepted cargo that it may have and stay at that station until all wagons, and the locomotive(s) if they have their own cargo capacity, are completely full.  When fully loaded, the train will then go to the station Breadborune Cross Woods without stopping at any other stations it may encounter on the way.  There the train will unload any accepted cargo that it may have, and leave without loading.
+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 trains order have the default "Unload if accepted" order.  Taking a view of the entire order list for this train tells us that the only place that it can get coal from is Sleningville Mines because there are only two stations the train is allowed to stop at, and it is only allowed to load at one of them.  And even if a power station did open up within the catchment of Sleningville Mines the train would leave the station full of coal as unloading always happens before loading.  The reason that the second order does not need the "Unload all" order is because on the public server a secondary industry drop station (as Breadborune Cross Woods is in this example) will always have the necessary industry within the catchment area, and therefore always accept the coal.  It is also important to only have the default "Unload if accepted" order in games using newgrf industries that have a maximum stock of raw materials (such as Pikkas Basic Industries or ECS), then the unaccepted coal can continue to another possible drop station.  In piratical use the "Unload all" order is just not necessary.
 ==Transfer orders==

← Older revision		Revision as of 07:18, 4 December 2013
Line 1:		Line 1:
		+	{{update\|Everything, Read talk page}}
		+
	[[Trains\|<< Trains]] \| [[Guides:Building\|^^ Back to Building Guides Index]] \| [[How not to build\|How not to build >>]]		[[Trains\|<< Trains]] \| [[Guides:Building\|^^ Back to Building Guides Index]] \| [[How not to build\|How not to build >>]]
	----		----

@@ Line 1: / Line 1: @@
 [[Trains|<< Trains]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[How not to build|How not to build >>]]
 ----
@@ Line 75: / Line 73: @@
 These kind of orders are very usefull when working with SBahn and must be used when working with SBahn rings with 3 stations or more.
 ----
 [[Trains|<< Trains]] | [[Guides:Building|^^ Back to Building Guides Index]] | [[How not to build|How not to build >>]]
 [[Category:Guides]]

← Older revision		Revision as of 12:13, 7 November 2013
Line 1:		Line 1:
		+	{{Merge \|Shared Orders}}
		+
	[[Trains\|<< Trains]] \| [[Guides:Building\|^^ Back to Building Guides Index]] \| [[How not to build\|How not to build >>]]		[[Trains\|<< Trains]] \| [[Guides:Building\|^^ Back to Building Guides Index]] \| [[How not to build\|How not to build >>]]
	----		----