carrouting:operationsgame-it
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | carrouting:operationsgame-it [2018/11/12 08:56] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Operator====== | ||
+ | [[: | ||
+ | [[: | ||
+ | * **[[: | ||
+ | * [[: | ||
+ | |||
+ | \\ | ||
+ | Author: Mark Edwards. | ||
+ | {{ http:// | ||
+ | \\ | ||
+ | ===== Overview ===== | ||
+ | |||
+ | 3 or more people use a Rocrail layout to operate 2 or more trains, moving some or all of the cars on the layout from one place to another according to a plan. | ||
+ | |||
+ | This is called a Session or a Run. The Session can be played as a game, or just run to enjoy controlling the layout as a team. | ||
+ | |||
+ | Each train starts with a Starting Position, a Consist of already coupled cars, and a Switchlist, detailing cars to be dropped off and picked up. | ||
+ | |||
+ | Each car has a Waybill, detailing the different locations it is supposed to occupy on its journey through the layout. | ||
+ | |||
+ | The layout is divided into different Destinations, | ||
+ | |||
+ | Switchlists are updated when new cars are added, adding any destination locations for new cards to the list. This may change a train' | ||
+ | |||
+ | All players can play against the clock as a team. All players also receive a score. | ||
+ | |||
+ | ==== Requirements ==== | ||
+ | |||
+ | |||
+ | At least 3 people | ||
+ | ===Dispatcher=== | ||
+ | * Uses Rocrail client as a monitor | ||
+ | * Does not operate any trains directly | ||
+ | * Tells all Engineers what to do | ||
+ | * Plays against a minimum number of moves | ||
+ | |||
+ | === 2 Engineers === | ||
+ | * Uses Rocrail client to move trains | ||
+ | * Only allowed to use the Loc Control window or right click on blocks to select destinations and schedules | ||
+ | * Can perform Brakeman Duties if they do not have a Brakeman | ||
+ | * May use the Main Loc to switch cars between tracks | ||
+ | * Plays against par time | ||
+ | |||
+ | === Optional === | ||
+ | * 1 or more Brakemen | ||
+ | * Uses uncoupler pick to uncouple cars | ||
+ | * Uses fingers/ | ||
+ | * Uses fingers/ | ||
+ | * Rerails cars & locs | ||
+ | * Better if 1 Brakeman per Engineer | ||
+ | * Additional Engineers/ | ||
+ | * Yardmasters | ||
+ | * For layouts with a large yard | ||
+ | * Must have his own switching loc | ||
+ | * Responsible for taking dropped off cars into the yard, and supplying picked up cars to the main line | ||
+ | |||
+ | === One Server and 3 or more Clients === | ||
+ | * The Server can run one of the Clients | ||
+ | * Laptops can be used to run clients over the local home lan via TCP/IP | ||
+ | |||
+ | |||
+ | ===== Winning The Game ===== | ||
+ | |||
+ | Players win the game if they complete all the moves in all the Switch Lists for the trains and cars set up at Start, at or under the current Par score for the layout. | ||
+ | |||
+ | Points are awarded to Engineers for completing drop offs and pick ups, based on the number of cars. | ||
+ | |||
+ | Points are deducted from Engineers for derailments, | ||
+ | |||
+ | Bonus points are awarded to an Engineer for arriving at their Final Destination. | ||
+ | |||
+ | Points are awarded to the Dispatcher for each Engineer completing a Switching Operation. | ||
+ | |||
+ | Points are deducted from Dispatchers for each Hold command. | ||
+ | |||
+ | Bonus points are awarded to the Dispatcher for each Engineer reporting Final Destination with no faults or derailments. | ||
+ | |||
+ | |||
+ | ===== Starting Position ===== | ||
+ | |||
+ | The Dispatcher is isolated from the layout, preferably in a separate location where they cannot see the track. | ||
+ | |||
+ | One train per Engineer is setup in a block, with 0 or more coupled cars. 0 or more cars are " | ||
+ | |||
+ | Each Engineer has a switch list, which designates the Starting Position, which cars must be dropped off and picked up at different Destinations, | ||
+ | |||
+ | |||
+ | ===== Playing The Game ===== | ||
+ | |||
+ | The Dispatcher annouces they are Open For Dispatch. | ||
+ | |||
+ | All players try to complete the required moves on the layout in the minimum number of moves, the fastest time, and with the fewest faults. | ||
+ | |||
+ | When all the Engineers reach their Final Destinations or are removed from the game by crashing their trains, the game is over, and a final score is computed for each player. | ||
+ | |||
+ | ==== Communications ==== | ||
+ | |||
+ | |||
+ | When an Engineer requests or reports to the Dispatcher, they must always begin with their Train Number or Engineer Name. Examples: "3265 requesting destination block Grant Hills" or "Tony requesting block North" | ||
+ | |||
+ | When a Dispatcher commands an Engineer, they must always begin with the Engineer' | ||
+ | |||
+ | The Engineer must also report any accidents, such as a car derailing, crashing into another train, etc., immediately | ||
+ | |||
+ | Generally, Engineers make requests to the Dispatcher, and then the Dispatcher issues commands to the Engineers in response. | ||
+ | |||
+ | ==== Move To Destination ==== | ||
+ | |||
+ | |||
+ | The Engineer requests to move to his Destination block on the layout. | ||
+ | |||
+ | If the Engineer is moving manually, the Dispatcher should tell them what speed to use. Also, the Dispatcher must switch all turnouts as required if the Engineer is moving manually. | ||
+ | |||
+ | When the Engineer arrives at the end of his move, he requests another command from the Dispatcher. | ||
+ | |||
+ | If he is still not at his Destination he again requests the same Destination block. | ||
+ | |||
+ | If the Engineer moves to the wrong block, or fails to move at all after two requests from the Dispatcher, it is considered a fault. | ||
+ | |||
+ | ==== Switching Operations ==== | ||
+ | |||
+ | |||
+ | When the Engineer is told to begin Switching Operations, he reports how many cars he is dropping off and picking up, and the time. Example: | ||
+ | |||
+ | When the Engineer (and his Brakeman) are done Switching Operations, the Engineer then reports Switching Operations Done and checks his Switchlist. | ||
+ | |||
+ | Note that his switchlist may have changed based on the cars dropped off and picked up. | ||
+ | |||
+ | He then requests his next Destination from the Dispatcher. | ||
+ | |||
+ | ==== Marking Car Positions ==== | ||
+ | |||
+ | |||
+ | Each car has a position on the layout. | ||
+ | |||
+ | When an Engineer drops off a car, it is moved from the train' | ||
+ | |||
+ | ==== Finishing A Run ==== | ||
+ | |||
+ | |||
+ | When an Engineer has finished his Run, and all cars have been moved to their correct Destinations and his train is at the Final Position, he reports that his run has ended with the time to the Dispatcher. | ||
+ | |||
+ | His Switch List is examined to determined if he spotted any cars in the wrong location, and if he picked up any wrong cars along the way. | ||
+ | |||
+ | ==== Faults ==== | ||
+ | |||
+ | |||
+ | A fault is any mistake an Engineer makes in completing a Move or Switching Operation. | ||
+ | |||
+ | ==== Derailments ==== | ||
+ | |||
+ | |||
+ | Derailments are not normally considered a fault. | ||
+ | |||
+ | ==== Crashes ==== | ||
+ | |||
+ | |||
+ | |||
+ | ===== Keeping Score ===== | ||
+ | |||
+ | The Dispatcher keeps score for each train and car. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Faults ===== | ||
carrouting/operationsgame-it.txt · Last modified: 2018/11/12 08:56 by 127.0.0.1