Rail Route/tutorials — English @ Weblate: Tutorial passed

The translation is temporarily closed for contributions due to maintenance, please come back later.

	Key	English	Actions
	tutorial_passed	Tutorial passed
	tutorial_next	Click here for the [next one]
	tutorial_failed	Failed
	tutorial_restart	Restart
	tutorial_completed	These were the absolute basics how to control the traffic. Much more awaits you – contracts, system upgrades, automation etc. We recommend to play the [Endless mode] next.
	tutorial_completed_finish	Click to [exit the tutorial]
	endless_welcome_title	Welcome
	endless_welcome_description	It's up to you now. Grow your railway empire from scratch. Build up your traffic by accepting [contracts]. Don’t worry; we have already accepted a few to give you an easier start. [Accept] more and shape your business with them. Do not hesitate to [reject] contracts that do not match your needs. Everything repeats in [Cycles] of [{0.RepeatingInterval} {0.RepeatingInterval:minute\|minutes}], so you can plan ahead. When you feel comfortable, [buy new platforms] and [expand] to new stations and accept contracts there.
	endless_welcome_dontshow	Don't show any tips
	task_accept_contract	Accept a contract
	task_build_track	Build a track
	task_unlock_upgrade	Unlock an upgrade
	task_not_completed	not completed
	task_done	done
	hints_recurrent_contract	As a train dispatcher, effectively managing contracts is key to maintaining a smooth operation of your railroad network. Here's what you need to know: <b>Contract Types:</b> You will deal with two main types of contracts: [Recurrent contracts] and [One-Off contracts]. · <indent=1%>[Recurrent contracts] regularly bring new trains into your network, providing a stable and predictable traffic flow. This predictability allows for strategic planning and optimization of resources.</indent> · <indent=1%>[One-Off contracts] offer unique, singular challenges and rewards, diversifying your traffic management experiences.</indent> <b>Contract Preparation:</b> · <indent=1%>To generate contracts, specific buildings are required: [Conductor Offices] for green contracts and [Dispatcher Offices] for red contracts. While some Conductor Offices are pre-built, constructing additional ones is essential for acquiring more contracts.</indent> <b>Contract Planning and Trial Trains:</b> · <indent=1%>Each contract starts with a planning phase. During this phase, a schedule is suggested based on distances between stations and the speed limits of unlocked tracks. The reward is calculated from the scheduled travel time compared to the optimal time. Adjusting the schedule can lead to higher rewards but beware of penalties if the schedule is unrealistic.</indent> · <indent=1%>Following planning is the [trial train]. The trial train serves to validate the planned schedule. Based on its performance, adjustments to the schedule might be necessary for future trains.</indent> · <indent=1%>After the trial train completes its journey, you can further adjust the schedule to better align with real-world conditions and optimize contract fulfillment.</indent> <b>Optimizing Contracts:</b> · <indent=1%>You have the option to [optimize] or [reject] contracts as your network evolves.</indent> · <indent=1%>Two key upgrades, [Platform Adjustments] and [Timetable Adjustments], can be utilized for refining accepted contracts, enhancing platform efficiency and train timings.</indent> · <indent=1%>Carefully consider each contract before acceptance. Reviewing station timetables and planning resources is crucial to ensure your network can handle the additional traffic.</indent> <i>Dispatcher's Tip: Effective planning and strategic management are essential for a successful railroad operation. Careful assessment and timely adjustments of contracts will lead to a more efficient and profitable network.</i>
	hints_oneoff_contract	Your first [one-off contract]! You only need to dispatch [one train] for this contract... but it has a [predefined schedule]. No trial needed! Just comply with the schedule to receive the reward. Be sure to check how long the Freight will stay on the platforms.

	Key	English	Actions
	task_wait_for_intermission_time	All good for now. Regional train will be stabled while other traffic passes by.
	task_wait_for_train_arrival_at_damascus	The train's final destination is [Aleppo] after stopping at [Homs]. The train has only one locomotive [pulling] it now. If we sent the train directly to Homs, its locomotive would be at the dead end. After departing to Aleppo, the locomotive would [push] the train, making the train [slow]. To overcome this, we can perform a turn-around maneuver (wye turn) on an empty track to enter Homs in a pushing configuration. Then, the locomotive will be at the head of the train departing to Aleppo, and the train will reach its maximum speed. Instead of doing it manually, we will configure [Shunting Sensor] to automate this operation for all subsequent trains.
	task_wait_for_train_arrival_at_damascus_loco	The train's final destination is [Aleppo] after stopping at [Homs]. Currently, the train is being [pulled] by a single locomotive. If we were to send the train from Homs to Aleppo in its current configuration, the locomotive would [push] the train, making the train [slow]. To overcome this, we can perform a [run-around] manuver with the locomotive once the train arrives at Homs. Then, the locomotive will be at the head of the train departing to Aleppo, allowing the train to reach its maximum speed. Instead of doing it manually, we will configure [Shunting Sensor] to automate this operation for all subsequent trains.
	task_wait_for_train_arrival_at_hama	[Reg1/I0] has its scheduled [intermission] in [Homs] that takes a while. It needs to be stabled away from the platform not to block it. [Stabling Sensor] can fully automate the stabling process. When triggered by a [multi-leg] train that already finished its leg, it [enqueues] the pre-configured shunting commands to the shunting queue of the train. We will go through it step-by-step once the train arrives to [Hama].
	task_wait_for_train_arrival_at_homs	[Reg1/I0] has its scheduled [intermission] in [Homs] that takes a while. [Shunting Commands] can control the train during its intermission. They can be enqueued to the [Shunting Queue] of the train so all is set up [at once] and then executed automatically. But first, let's wait for our train to arrive at [Homs] and finish the first leg. It wouldn't actually stop there if we switched it to [Shunting Mode] beforehand.
	task_wait_for_transfer_next_leg	The train already prepares for the [next leg]. Wait for the transfer to the first station of it.
	task_watch_sensor_working	Let's see how the sensor works.
	tutorial_completed	These were the absolute basics how to control the traffic. Much more awaits you – contracts, system upgrades, automation etc. We recommend to play the [Endless mode] next.
	tutorial_completed_finish	Click to [exit the tutorial]
	tutorial_custom_completed	Tutorial Completed
	tutorial_custom_completed_finish	[click here] to return back
	tutorial_failed	Failed
	tutorial_finished_dialog_button_text	Click to return to the game.
	tutorial_finished_dialog_title	Tutorial finished successfully.
	tutorial_next	Click here for the [next one]
	tutorial_passed	Tutorial passed
	tutorial_restart	Restart

Loading…

None

String updated in the repository

English

English 0 characters edited Current translation Translated

10 months ago

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Reused translation: Polish, Swedish, Dutch, Spanish

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Key

tutorial_passed

Flags

xml-text

String age

3 years ago

Last updated

10 months ago

Source string age

3 years ago

Translation file

tutorials/export_en.xlf, string 1