signaller.org wiki - Recent changes [en-gb]

File:Map editor publish.png

4shveil — Fri, 09 Oct 2026 14:04:43 GMT

Describe the released editor's Publish dialog

← Older revision		Revision as of 14:04, 9 October 2026
Line 1:		Line 1:
	== Summary ==		== Summary ==
	~~The~~ Publish ~~tab of~~ the map editor~~, ready to send~~ a map to the workshop.		Publish to the workshop, the map editor's dialog for sending a map to the workshop, with a title and description filled in.

	Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.		Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

	[[Category:Map editor]]		[[Category:Map editor]]

File:Map editor your maps.png

4shveil — Fri, 09 Oct 2026 14:04:42 GMT

Describe the released editor's Your maps list

← Older revision		Revision as of 14:04, 9 October 2026
Line 1:		Line 1:
	== Summary ==		== Summary ==
	~~The~~ Your maps ~~window of~~ the map editor, with one map.		Your maps in the map editor: the list of your saved maps, with one map.

	Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.		Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

	[[Category:Map editor]]		[[Category:Map editor]]

Publishing a map

4shveil — Fri, 09 Oct 2026 14:04:29 GMT

Match the released editor: Publish is a dialog, and there are no AI-assisted maps yet

← Older revision		Revision as of 14:04, 9 October 2026
Line 7:		Line 7:

	== Publishing ==		== Publishing ==
	[[File:Map editor publish.png\|thumb\|none\|700px\|~~The~~ Publish ~~tab~~, with a title and description filled in.]]		[[File:Map editor publish.png\|thumb\|none\|700px\|Publish to the workshop, with a title and description filled in.]]

	# Press '''Publish''' in the toolbar.		# Press '''Publish''' in the toolbar. '''Publish to the workshop''' opens.
	# Give it a '''Title''' (the name players see) and a '''Description''' (what's on the map, and anything players should know).		# Give it a '''Title''' (the name players see) and a '''Description''' (what's on the map, and anything players should know).
	# Press '''Publish'''.		# Press '''Publish'''.
Line 16:		Line 16:

	== Where it's up to ==		== Where it's up to ==
	~~Open the~~ '''Publish''' ~~tab~~ again to see:		Press '''Publish''' again to see:

	* '''Waiting for review''': nothing to do yet.		* '''Waiting for review''': nothing to do yet.
Line 29:		Line 29:
	== Taking a map down ==		== Taking a map down ==
	'''Remove from workshop''' unlists it. You can publish it again later; it will be reviewed again.		'''Remove from workshop''' unlists it. You can publish it again later; it will be reviewed again.

	~~== AI-assisted maps ==~~
	If you used the [[Map editor#AI assistant\|AI assistant]] to change the map, the workshop labels it '''AI-assisted''' and lists it after maps made without one. The label stays for good, even after later updates.

	== Playing a workshop map ==		== Playing a workshop map ==

Map editor

4shveil — Fri, 09 Oct 2026 14:04:16 GMT

Match the released editor: Your maps is a list, and there is no comment tool or AI assistant yet

← Older revision		Revision as of 14:04, 9 October 2026
Line 11:		Line 11:

	== Your maps ==		== Your maps ==
	The first thing you see is ~~the editor window, open on~~ '''Your maps'''. ~~It stays open until you open a map~~.		The first thing you see is '''Your maps''', a list of the maps you've saved. You can come back to it at any time with '''Open''' (Ctrl+O).

	[[File:Map editor your maps.png\|thumb\|none\|700px\|Your maps, with one map. Click ~~a card~~ to open it.]]		[[File:Map editor your maps.png\|thumb\|none\|700px\|Your maps, with one map. Click its name to open it.]]

			* Click a map's name to open it. The buttons beside it download it as a map file or delete it.
	* '''New map''' starts a blank map.		* '''New map''' starts a blank map.
	* Each of your maps is a card with a picture of it. Click one to open it. You can also download or delete it from here.
	* Type in '''Find a map''' to find a map by name.
	* '''Open file''' adds a map file (<code>.sg</code>) that you or someone else downloaded.		* '''Open file''' adds a map file (<code>.sg</code>) that you or someone else downloaded.
			* '''Back to the map''' returns to the map you have open.

	You can keep up to 25 maps.		You can keep up to 25 maps.
Line 55:		Line 55:
	\|-		\|-
	\| B \|\| Draw zone border \|\| Click corners to outline a zone.		\| B \|\| Draw zone border \|\| Click corners to outline a zone.
	\|-
	~~\| C \|\| Add a comment \|\| Pin a note to the map. Only the editor shows comments; they are never published.~~
	\|}		\|}

Line 113:		Line 111:
	* If your sign-in runs out while you work, the map stays open. Sign in again in another tab, then save.		* If your sign-in runs out while you work, the map stays open. Sign in again in another tab, then save.
	* '''Download''' saves the map as last saved as a <code>.sg</code> map file. Only signaller.org can read inside it, but anyone can open it in their own editor with '''Open file'''.		* '''Download''' saves the map as last saved as a <code>.sg</code> map file. Only signaller.org can read inside it, but anyone can open it in their own editor with '''Open file'''.

	~~== AI assistant ==~~
	People who boost the signaller.org Discord server can use an AI assistant. It sits in the bottom-left corner of the map as '''Ask the assistant'''. It can explain how to set up signals, next signals, conflicts and routes, and can make changes to your map if you let it.

	~~The first change it makes marks the map as '''AI-assisted''', for good. In the workshop, AI-assisted maps are labelled and listed after maps made without one. Asking it questions never marks a map.~~

	== Guides ==		== Guides ==

File:Map editor publish.png

4shveil — Fri, 09 Oct 2026 14:03:40 GMT

4shveil uploaded a new version of File:Map editor publish.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
The Publish tab of the map editor, ready to send a map to the workshop.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor test bench.png

4shveil — Fri, 09 Oct 2026 14:03:40 GMT

4shveil uploaded a new version of File:Map editor test bench.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
Testing the example map: signal A is held at red by a conflict while train 1T01 crosses on Line 2.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor check tab.png

4shveil — Fri, 09 Oct 2026 14:03:40 GMT

4shveil uploaded a new version of File:Map editor check tab.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
The map editor's Check tab after Validate map, with no problems found.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor route.png

4shveil — Fri, 09 Oct 2026 14:03:39 GMT

4shveil uploaded a new version of File:Map editor route.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
A route in the map editor's Routes tab, drawn on the example map.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor conflict rules on the map.png

4shveil — Fri, 09 Oct 2026 14:03:39 GMT

4shveil uploaded a new version of File:Map editor conflict rules on the map.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
Hovering over a conflict card in the map editor: the signals in the conflict and its rule are ringed on the map.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor conflict step 3.png

4shveil — Fri, 09 Oct 2026 14:03:39 GMT

4shveil uploaded a new version of File:Map editor conflict step 3.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
A conflict card in the map editor: signal A's conflict on B, with a rule and a clearance distance.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor conflict step 2.png

4shveil — Fri, 09 Oct 2026 14:03:39 GMT

4shveil uploaded a new version of File:Map editor conflict step 2.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
A conflict card in the map editor: signal A's conflict on B, narrowed by a rule.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor signal settings.png

4shveil — Fri, 09 Oct 2026 14:03:38 GMT

4shveil uploaded a new version of File:Map editor signal settings.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
The Inspector for signal A of the example map: its settings and next signals.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor drawing track.png

4shveil — Fri, 09 Oct 2026 14:03:38 GMT

4shveil uploaded a new version of File:Map editor drawing track.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
Drawing track in the map editor: two pieces laid, and the next one following the pointer.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor your maps.png

4shveil — Fri, 09 Oct 2026 14:03:37 GMT

4shveil uploaded a new version of File:Map editor your maps.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
The Your maps window of the map editor, with one map.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor screen.png

4shveil — Fri, 09 Oct 2026 14:03:37 GMT

4shveil uploaded a new version of File:Map editor screen.png Retaken on the released map editor (main), without unreleased features

New page

== Summary ==
The whole map editor, with signal A of the example map selected: the tools on the left, the map, and the Inspector on the right.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

Publishing a map

4shveil — Fri, 09 Oct 2026 13:46:08 GMT

Add a screenshot of the Publish tab

← Older revision		Revision as of 13:46, 9 October 2026
Line 7:		Line 7:

	== Publishing ==		== Publishing ==
			[[File:Map editor publish.png\|thumb\|none\|700px\|The Publish tab, with a title and description filled in.]]

	# Press '''Publish''' in the toolbar.		# Press '''Publish''' in the toolbar.
	# Give it a '''~~title~~''' (the name players see) and a '''~~description~~''' (what's on the map, and anything players should know).		# Give it a '''Title''' (the name players see) and a '''Description''' (what's on the map, and anything players should know).
	# Press '''Publish'''.		# Press '''Publish'''.

Testing a map

4shveil — Fri, 09 Oct 2026 13:45:59 GMT

Add screenshots of the Check tab and the test bench; name the Spawn tool and the P key as the editor shows them

← Older revision		Revision as of 13:45, 9 October 2026
Line 2:		Line 2:

	== The Check tab ==		== The Check tab ==
			[[File:Map editor check tab.png\|thumb\|right\|300px\|The Check tab after Validate map: the game loads the map, and the quick checks find nothing.]]

	The '''Check''' tab lists problems as you edit, split into errors and warnings. Press the crosshair next to one to find it on the map.		The '''Check''' tab lists problems as you edit, split into errors and warnings. Press the crosshair next to one to find it on the map.

Line 18:		Line 20:

	A result marked ''(before your latest edits)'' is out of date; press Validate map again.		A result marked ''(before your latest edits)'' is out of date; press Validate map again.

			{{clear}}

	== Testing with trains ==		== Testing with trains ==
	Press '''Test''' in the toolbar. The map is loaded into a test bench, and you can no longer edit it until you press '''Stop test'''.		Press '''Test''' in the toolbar. The map is loaded into a test bench, and you can no longer edit it until you press '''Stop test'''.

			[[File:Map editor test bench.png\|thumb\|none\|700px\|Testing Example Junction. Train 1T01 is crossing Line 2 on its way to B2, so signal A is held at red: the panel at the bottom right says ''Red: conflict with 1T01''. Train 1T02 waits for it at A.]]

	=== Placing a train ===		=== Placing a train ===
	# Choose '''~~Place trains~~''' (N) in the tools on the left.		# Choose '''Spawn''' (N) in the tools on the left.
	# Click where the train starts: a signal, a buffer stop, or anywhere on a track.		# Click where the train starts: a signal, a buffer stop, or anywhere on a track.
	# Click the signal or buffer stop it should run to.		# Click the signal or buffer stop it should run to.
Line 32:		Line 38:

	=== Running the test ===		=== Running the test ===
	* Press play or pause, and pick a speed: 1×, 2×, 5×, 10× or 30×.		* Press play or pause (or P), and pick a speed: 1×, 2×, 5×, 10× or 30×.
	* The restart button clears every train and loads your map again.		* The restart button clears every train and loads your map again.
	* '''Signaller''' chooses who runs the signals:		* '''Signaller''' chooses who runs the signals:
Line 41:		Line 47:

	=== Trains ===		=== Trains ===
	Click a train in the '''Trains''' list to:		Click a train, on the map or in the '''Trains''' list, to see where it is going, its route and the blocks it holds. You can then:
	* '''Send to…''': click another signal or buffer stop for it to go to,		* '''Send to…''': click another signal or buffer stop for it to go to,
	* '''Stop at next signal''', then '''Continue''', or		* '''Stop at next signal''', then '''Continue''', or
Line 49:		Line 55:

	=== Why is this signal red? ===		=== Why is this signal red? ===
	Click a signal on the map. The panel shows its aspect and why, such as ~~which train is in its~~ block, or ~~which~~ train is holding it through a conflict.		Click a signal on the map. The panel shows its aspect and why, such as ''block occupied by 1T02'', or ''conflict with 1T01'' when another train is holding it through a [[Conflicts in the map editor\|conflict]].

	If ~~you control it~~, you can also:		If the signal is controllable, you can also:
	* choose its '''Route''' when it has more than one next signal,		* choose its '''Route''' when it has more than one next signal,
	* give it a '''Danger''', '''Caution''' or '''Proceed''' command, and		* give it a '''Danger''', '''Caution''' or '''Proceed''' command, and

Routes in the map editor

4shveil — Fri, 09 Oct 2026 13:45:44 GMT

Add a screenshot of a route being built; a new route already has its first spawn variant

Template:Clear

4shveil — Fri, 09 Oct 2026 13:45:29 GMT

New template: start the next content below any floated pictures

New page

<div style="clear: both;"></div><noinclude>
Starts what follows below any picture floated beside the text, so a heading doesn't sit next to the picture above it.

Use: <code><nowiki>{{clear}}</nowiki></code>
</noinclude>

Conflicts in the map editor

4shveil — Fri, 09 Oct 2026 13:45:19 GMT

Replace the text sketch with a diagram, add a screenshot for each step, and match the example's distances to the example map

← Older revision		Revision as of 13:45, 9 October 2026
Line 23:		Line 23:

	== A worked example ==		== A worked example ==
	~~Here a~~ branch leaves Line 1 and crosses Line 2 on the flat:		This is the junction on '''Example Junction''', the map the guides use. A branch leaves Line 1 and crosses Line 2 on the flat:

	~~<pre>~~		[[File:Conflict example diagram.svg\|thumb\|none\|700px\|The two moves that meet: A → A3 (orange) crosses Line 2 where B → B2 (teal) runs. A → A2 never goes near Line 2.]]
	Line ~~1 -->~~ A ~~----+--------------~~ A2 ~~-->~~
	\
	Line 2 ~~<-- B2 ------X------------ B <--~~
	\
	~~Branch \---------- A3 -->~~
	~~</pre>~~

	* Signal '''A''' is on Line 1, before the junction. It has two next signals: '''A2''' straight on, and '''A3''' down the branch.		* Signal '''A''' is on Line 1, before the junction. It has two next signals: '''A2''' straight on, and '''A3''' down the branch.
	* Signal '''B''' is on Line 2. Its next signal is '''B2'''.		* Signal '''B''' is on Line 2, just before the crossing. Its next signal is '''B2'''.
	* A train going from A to A3 crosses Line 2 ~~at the X~~. A train going from B to B2 passes over the same X.		* A train going from A to A3 crosses Line 2. A train going from B to B2 passes over the same spot.

	So these two moves can collide: '''A → A3''' and '''B → B2'''. A train going A → A2 never goes near Line 2, so it should never wait for B.		So these two moves can collide: '''A → A3''' and '''B → B2'''. A train going A → A2 never goes near Line 2, so it should never wait for B.

	=== Step 1: add the conflicts ===		=== Step 1: add the conflicts ===
			[[File:Map editor conflict step 1.png\|thumb\|right\|300px\|Step 1: A's conflict on B, with no rules yet.]]

	# Select signal A. In the Inspector, under '''Conflicts''', type B in '''Add conflict with…''' and press '''+'''. (Or press the pick button and click B on the map.)		# Select signal A. In the Inspector, under '''Conflicts''', type B in '''Add conflict with…''' and press '''+'''. (Or press the pick button and click B on the map.)
	# Select signal B and add a conflict with A in the same way.		# Select signal B and add a conflict with A in the same way.
Line 48:		Line 44:

	That's safe, but it is too strict: it also holds A when it is set straight on to A2, which never crosses Line 2.		That's safe, but it is too strict: it also holds A when it is set straight on to A2, which never crosses Line 2.

			{{clear}}

	=== Step 2: narrow it with a rule ===		=== Step 2: narrow it with a rule ===
			[[File:Map editor conflict step 2.png\|thumb\|right\|300px\|Step 2: a rule for A set to A3 and the other train heading for B2. The dashed ''+ A2'' is a suggestion you could add.]]

	On A's card, press '''Add a rule to narrow this conflict''', and fill in:		On A's card, press '''Add a rule to narrow this conflict''', and fill in:
	* '''Routed to (A)''': A3. The rule only applies when A is set for the branch.		* '''Routed to (A)''': A3. The rule only applies when A is set for the branch.
	* '''Routed to (other train)''': B2. It only counts a train past B that is heading for B2.		* '''Routed to (other train)''': B2. It only counts a train past B that is heading for B2.

			The fields suggest the signals that make sense, so you can usually click a suggestion rather than type.

	The card now reads:		The card now reads:
Line 60:		Line 62:
	Do the same on B's card, the other way round: '''Routed to (B)''' B2, '''Routed to (other train)''' A3.		Do the same on B's card, the other way round: '''Routed to (B)''' B2, '''Routed to (other train)''' A3.

	~~The fields suggest the signals that make sense, so you can usually click a suggestion rather than type.~~		{{clear}}

	=== Step 3: let it clear sooner ===		=== Step 3: let it clear sooner ===
	As it stands, A waits until B's train reaches B2. But once that train's tail has cleared the X, A's train could safely go. '''Clears within''' lets the conflict end earlier.		[[File:Map editor conflict step 3.png\|thumb\|right\|300px\|Step 3: Clears within set to 0.27 miles.]]

			As it stands, A waits until B's train reaches B2. But once that train's tail has cleared the crossing, A's train could safely go. '''Clears within''' lets the conflict end earlier.

	: '''Clears within''' = the miles left from the crossing to B2, less about 0.06 for the length of the train.		: '''Clears within''' = the miles left from the crossing to B2, less about 0.06 for the length of the train.

	~~Say~~ B to B2 is 0.25 miles, and the X is 0.05 miles past B. That leaves 0.20 miles after the crossing. Take off 0.06, and '''Clears within''' is '''0.14'''. A is now held only until B's train is within 0.14 miles of B2.		In the example, B to B2 is 0.4 miles, and the crossing is 0.07 miles past B. That leaves 0.33 miles after the crossing. Take off 0.06, and '''Clears within''' is '''0.27'''. A is now held only until B's train is within 0.27 miles of B2.

			Work out B's card the same way, using the miles from the crossing to A3. In the example that is 0.49, so B's rule clears within 0.43.

	~~Work out B's card the same way, using the miles from the crossing to A3.~~		{{clear}}

	== Narrowing a conflict with rules ==		== Narrowing a conflict with rules ==
Line 93:		Line 99:

	== Checking your conflicts ==		== Checking your conflicts ==
			[[File:Map editor conflict rules on the map.png\|thumb\|none\|700px\|Hovering over A's conflict card. B, the target, is ringed red; A3, which the rule needs A to be set to, is yellow; B2, where the other train must be heading, is teal.]]

	* '''Hover over a conflict card''' to light up just that conflict on the map.		* '''Hover over a conflict card''' to light up just that conflict on the map.
	* With a signal selected, its conflict target is ringed '''red''', and signals with a conflict on it are ringed '''purple'''. Rule signals are ringed orange, yellow and teal.		* With a signal selected, its conflict target is ringed '''red''', and signals with a conflict on it are ringed '''purple'''. Rule signals are ringed orange, yellow and teal.
Line 98:		Line 106:
	* A warning on a field means the signal you entered isn't linked the way the rule needs, so the rule may never apply.		* A warning on a field means the signal you entered isn't linked the way the rule needs, so the rule may never apply.
	* The '''Check''' tab warns about a rule that can never apply because its Clears within is longer than any block after the target.		* The '''Check''' tab warns about a rule that can never apply because its Clears within is longer than any block after the target.
	* Then run trains at the junction with '''Test''', and click a red signal to see why it is red. See [[Testing a map]].		* Then run trains at the junction with '''Test''', and click a red signal to see why it is red. See [[Testing a map#Why is this signal red?\|Testing a map]].

	== Common mistakes ==		== Common mistakes ==

Signals in the map editor

4shveil — Fri, 09 Oct 2026 13:44:57 GMT

Add an aspects diagram and screenshots of the Inspector and relation rings; fix the Type and Max aspect names to match the editor

← Older revision		Revision as of 13:44, 9 October 2026
Line 3:		Line 3:
	== How signals keep trains apart ==		== How signals keep trains apart ==
	Each signal protects the stretch of line up to the next signal, called a '''block'''. Only one train may be in a block at once.		Each signal protects the stretch of line up to the next signal, called a '''block'''. Only one train may be in a block at once.

			[[File:Signal aspects diagram.svg\|thumb\|none\|700px\|A train in a block holds the signal behind it at red. Each signal further back shows one step better.]]

	* A signal shows '''red''' while its block has a train in it, or while a [[Conflicts in the map editor\|conflict]] holds it.		* A signal shows '''red''' while its block has a train in it, or while a [[Conflicts in the map editor\|conflict]] holds it.
Line 27:		Line 29:
	! Type !! Use it for		! Type !! Use it for
	\|-		\|-
	\| ~~4aspect~~ \|\| Main lines. This is the default.		\| 4-aspect \|\| Main lines. This is the default.
	\|-		\|-
	\| ~~3aspect~~ \|\| Slow branch lines.		\| 3-aspect \|\| Slow branch lines.
	\|-		\|-
	\| ~~shunt~~ \|\| Depots and sidings.		\| Shunt \|\| Depots and sidings.
	\|-		\|-
	\| ~~tram~~ \|\| Lines where tram-trains run in the street.		\| Tram \|\| Lines where tram-trains run in the street.
	\|}		\|}

Line 42:		Line 44:

	== Settings ==		== Settings ==
			[[File:Map editor signal settings.png\|thumb\|right\|300px\|Signal A's settings in the Inspector. It is a controllable 4-aspect signal before a junction, so it has two next signals.]]

	Select a signal to see its settings in the Inspector.		Select a signal to see its settings in the Inspector.

Line 61:		Line 65:
	\| Speed (mph) \|\| The line speed after the signal. With none, trains run at 45. The official map uses 30 in depots, sidings and into termini, 45 to 60 over junctions, and 75 to 125 on main lines.		\| Speed (mph) \|\| The line speed after the signal. With none, trains run at 45. The official map uses 30 in depots, sidings and into termini, 45 to 60 over junctions, and 75 to 125 on main lines.
	\|-		\|-
	\| Max aspect \|\| The best aspect it may show. Set '''~~Yellow~~''' for a signal into a buffer stop, so trains run into the terminus with caution.		\| Max aspect \|\| The best aspect it may show: '''Danger''' (red), '''Caution''' (yellow), '''Preliminary caution''' (double yellow) or '''Proceed''' (green). Set '''Caution''' for a signal into a buffer stop, so trains run into the terminus with caution.
	\|-		\|-
	\| Allocation \|\| How it picks a platform when the planned one is blocked. See [[#Choosing a platform\|Choosing a platform]].		\| Allocation \|\| How it picks a platform when the planned one is blocked. See [[#Choosing a platform\|Choosing a platform]].
Line 69:		Line 73:

	=== A starter that leads nowhere ===		=== A starter that leads nowhere ===
	Sometimes a platform starter faces a way trains can never go on. Give it no next signals, set '''Max aspect''' to '''~~Red~~''', and untick '''Controllable'''. It then stays red.		Sometimes a platform starter faces a way trains can never go on. Give it no next signals, set '''Max aspect''' to '''Danger''', and untick '''Controllable'''. It then stays red.

	== Next signals ==		== Next signals ==
	A signal's '''next signals''' are where a train passing it can run to: the next signal ahead in the same direction, on each way it can take. They are listed in the Inspector under '''Next signals'''.		A signal's '''next signals''' are where a train passing it can run to: the next signal ahead in the same direction, on each way it can take. They are listed in the Inspector under '''Next signals''', each with its distance in '''Miles'''.

	To add one, either:		To add one, either:
Line 81:		Line 85:
	* '''Name the very next signal.''' If you skip one, trains ignore the signal you skipped.		* '''Name the very next signal.''' If you skip one, trains ignore the signal you skipped.
	* '''The two must be joined by track''' (not Unused track). The game sends trains along the shortest track between them, and won't load a map where there is none. Check that the shortest way is the way trains should go.		* '''The two must be joined by track''' (not Unused track). The game sends trains along the shortest track between them, and won't load a map where there is none. Check that the shortest way is the way trains should go.
	* '''One per way through a junction.''' Most signals have one next signal. A signal before a junction has one for each way through it.		* '''One per way through a junction.''' Most signals have one next signal. A signal before a junction has one for each way through it. In the example, A has two: A2 straight on and A3 down the branch.
	* '''At a buffer stop''', the last signal's next signal is the buffer stop, which shows as TERM followed by its id, such as TERM3.		* '''At a buffer stop''', the last signal's next signal is the buffer stop, which shows as TERM followed by its id, such as TERM3.

Line 106:		Line 110:
	A platform with neither is never used.		A platform with neither is never used.

	At a terminus, the signal before the platforms has the buffer stops as its next signals. Give it Max aspect '''~~Yellow~~''' and a speed of about 30, and make it controllable.		At a terminus, the signal before the platforms has the buffer stops as its next signals. Give it Max aspect '''Caution''' and a speed of about 30, and make it controllable.

	== Seeing how signals connect ==		== Seeing how signals connect ==
	When you select a signal, buffer stop or platform, the editor rings the things related to it, with a key in the corner of the map:		When you select a signal, buffer stop or platform, the editor rings the things related to it, with a key in the corner of the map. Dashed lines join the selection to each of them.

			[[File:Map editor signal relations.png\|thumb\|none\|700px\|Signal A selected (blue). Its next signals A2 and A3 are green, the signal before it (S1) is pink, and B is ringed red and purple because A and B have conflicts on each other. B2 and A3 also appear in the conflict's rule.]]

	{\| class="wikitable"		{\| class="wikitable"

Building a map

4shveil — Fri, 09 Oct 2026 13:44:27 GMT

Add the example map and a screenshot of drawing track

← Older revision		Revision as of 13:44, 9 October 2026
Line 1:		Line 1:
	<p class="sg-lede">A step-by-step way to build a map in the [[map editor]], from bare track to trains running on it. Work through the steps in order, and check each one before you start the next.</p>		<p class="sg-lede">A step-by-step way to build a map in the [[map editor]], from bare track to trains running on it. Work through the steps in order, and check each one before you start the next.</p>

			[[File:Map editor example map.png\|thumb\|none\|700px\|'''Example Junction''', the small map the guides use: two lines, a siding with a shunt signal (S1), and a branch that crosses Line 2 on the flat. Buffer stops (TERM), platforms (EC1, EC2) and the zone border (blue) are all here.]]

	== The order to work in ==		== The order to work in ==
Line 18:		Line 20:
	== Drawing track ==		== Drawing track ==
	Press '''T''' for the Draw track tool.		Press '''T''' for the Draw track tool.

			[[File:Map editor drawing track.png\|thumb\|none\|700px\|Drawing track. Each click adds a point; the dotted line shows where the next piece will go. The bar along the top repeats how the tool works.]]

	* Click to put down the first point, then click again for each bend.		* Click to put down the first point, then click again for each bend.
Line 32:		Line 36:

	=== Joins and crossings ===		=== Joins and crossings ===
	Two pieces of track are joined only where they share an end, or where one ends on the middle of another. If two tracks cross without a shared point, that is a '''flat crossing''' (a diamond): trains can't turn there, but two trains crossing it can collide, so it needs [[Conflicts in the map editor\|conflicts]].		Two pieces of track are joined only where they share an end, or where one ends on the middle of another. If two tracks cross without a shared point, that is a '''flat crossing''' (a diamond): trains can't turn there, but two trains crossing it can collide, so it needs [[Conflicts in the map editor\|conflicts]]. The branch in Example Junction crosses Line 2 like this.

	When you select a piece of track, the Inspector's '''Type''' sets how it works:		When you select a piece of track, the Inspector's '''Type''' sets how it works:
Line 41:		Line 45:

	== Buffer stops ==		== Buffer stops ==
	Press '''E''' and click the end of a track. A buffer stop must sit exactly on a track end, or the game won't draw it.		Press '''E''' and click the end of a track. A buffer stop must sit exactly on a track end, or the game won't draw it. With ids shown (I), buffer stops are labelled TERM and a number.

	== Platforms ==		== Platforms ==
Line 56:		Line 60:

	* Every signal belongs to a zone (its '''Zone''' setting): the player who controls it.		* Every signal belongs to a zone (its '''Zone''' setting): the player who controls it.
	* '''Zone borders''' (press '''B''') outline each zone's area on the map. ~~Click~~ the corners, ~~then~~ click the last one again or press Esc~~. Type the zone in '''Zones''' before you start~~.		* '''Zone borders''' (press '''B''') outline each zone's area on the map. Type the zone in '''Zones''' first, then click the corners, and click the last one again or press Esc.
	* '''Labels''' (press '''X''') show station names. Size 4 is the size the official map uses. A label's '''Zones''' setting picks which zones show it; leave it empty to show it everywhere.		* '''Labels''' (press '''X''') show station names. Click where it goes, then type the name in the Inspector's '''Text'''. Size 4 is the size the official map uses. A label's '''Zones''' setting picks which zones show it; leave it empty to show it everywhere.

	Use '''View''' in the toolbar to see the map as one zone's player will.		Use '''View''' in the toolbar to see the map as one zone's player will.

Map editor

4shveil — Fri, 09 Oct 2026 13:44:10 GMT

Add screenshots of the editor screen, Your maps and Preview

← Older revision		Revision as of 13:44, 9 October 2026
Line 13:		Line 13:
	The first thing you see is the editor window, open on '''Your maps'''. It stays open until you open a map.		The first thing you see is the editor window, open on '''Your maps'''. It stays open until you open a map.

	* '''New''' starts a blank map.		[[File:Map editor your maps.png\|thumb\|none\|700px\|Your maps, with one map. Click a card to open it.]]

			* '''New map''' starts a blank map.
	* Each of your maps is a card with a picture of it. Click one to open it. You can also download or delete it from here.		* Each of your maps is a card with a picture of it. Click one to open it. You can also download or delete it from here.
	* Type in ~~the filter~~ to find a map by name.		* Type in '''Find a map''' to find a map by name.
	* '''Open file''' adds a map file (<code>.sg</code>) that you or someone else downloaded.		* '''Open file''' adds a map file (<code>.sg</code>) that you or someone else downloaded.

Line 21:		Line 23:

	== The screen ==		== The screen ==
			[[File:Map editor screen.png\|thumb\|none\|700px\|The editor with a signal selected: the tools on the left, the map in the middle, and the signal's settings in the Inspector on the right.]]

	* '''The toolbar''' runs along the top: New, Open, Save, Save copy, Publish, Download, undo and redo, view settings, and '''Test'''.		* '''The toolbar''' runs along the top: New, Open, Save, Save copy, Publish, Download, undo and redo, view settings, and '''Test'''.
	* '''The tools''' are down the left side. Each has a key, shown below.		* '''The tools''' are down the left side. Each has a key, shown below.
Line 99:		Line 103:
	* '''Preview''' (the ` key) hides everything the editor adds, such as ids and selection marks, and shows the map exactly as the game draws it.		* '''Preview''' (the ` key) hides everything the editor adds, such as ids and selection marks, and shows the map exactly as the game draws it.
	* '''View''' in the toolbar shows the map as one zone's player sees it: that zone's borders, labels and controllable signals.		* '''View''' in the toolbar shows the map as one zone's player sees it: that zone's borders, labels and controllable signals.

			[[File:Map editor example map.png\|thumb\|none\|700px\|The example map in the editor, with ids shown (I).]]
			[[File:Map editor preview.png\|thumb\|none\|700px\|The same map in Preview (`): exactly what players see.]]

	== Saving ==		== Saving ==
Line 113:		Line 120:

	== Guides ==		== Guides ==
			The guides use one small example map throughout, '''Example Junction''': two lines and a branch that crosses one of them on the flat.

	# [[Building a map]]: the order to work in, and drawing the track		# [[Building a map]]: the order to work in, and drawing the track
	# [[Signals in the map editor]]: placing signals, their settings and next signals		# [[Signals in the map editor]]: placing signals, their settings and next signals

File:Map editor publish.png

4shveil — Fri, 09 Oct 2026 13:43:21 GMT

4shveil uploaded File:Map editor publish.png Image for the map editor guides

New page

File:Map editor test bench.png

4shveil — Fri, 09 Oct 2026 13:43:21 GMT

4shveil uploaded File:Map editor test bench.png Image for the map editor guides

New page

File:Map editor check tab.png

4shveil — Fri, 09 Oct 2026 13:43:21 GMT

4shveil uploaded File:Map editor check tab.png Image for the map editor guides

New page

File:Map editor route.png

4shveil — Fri, 09 Oct 2026 13:43:20 GMT

4shveil uploaded File:Map editor route.png Image for the map editor guides

New page

File:Map editor conflict rules on the map.png

4shveil — Fri, 09 Oct 2026 13:43:20 GMT

4shveil uploaded File:Map editor conflict rules on the map.png Image for the map editor guides

New page

File:Map editor conflict step 3.png

4shveil — Fri, 09 Oct 2026 13:43:20 GMT

4shveil uploaded File:Map editor conflict step 3.png Image for the map editor guides

New page

File:Map editor conflict step 2.png

4shveil — Fri, 09 Oct 2026 13:43:19 GMT

4shveil uploaded File:Map editor conflict step 2.png Image for the map editor guides

New page

File:Map editor conflict step 1.png

4shveil — Fri, 09 Oct 2026 13:43:19 GMT

4shveil uploaded File:Map editor conflict step 1.png Image for the map editor guides

New page

== Summary ==
A conflict card in the map editor: signal A's conflict on B, before any rules.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Conflict example diagram.svg

4shveil — Fri, 09 Oct 2026 13:43:19 GMT

4shveil uploaded File:Conflict example diagram.svg Image for the map editor guides

New page

== Summary ==
Diagram: the flat crossing in the conflict example, with the moves A to A3 and B to B2 and where B's train clears the crossing.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Signal aspects diagram.svg

4shveil — Fri, 09 Oct 2026 13:43:18 GMT

4shveil uploaded File:Signal aspects diagram.svg Image for the map editor guides

New page

== Summary ==
Diagram: how 4-aspect signals step down behind a train, from red to yellow, double yellow and green.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor signal relations.png

4shveil — Fri, 09 Oct 2026 13:43:18 GMT

4shveil uploaded File:Map editor signal relations.png Image for the map editor guides

New page

== Summary ==
Signal A selected on the example map, with the signals related to it ringed in colour and the key.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor signal settings.png

4shveil — Fri, 09 Oct 2026 13:43:17 GMT

4shveil uploaded File:Map editor signal settings.png Image for the map editor guides

New page

File:Map editor drawing track.png

4shveil — Fri, 09 Oct 2026 13:43:17 GMT

4shveil uploaded File:Map editor drawing track.png Image for the map editor guides

New page

File:Map editor preview.png

4shveil — Fri, 09 Oct 2026 13:43:17 GMT

4shveil uploaded File:Map editor preview.png Image for the map editor guides

New page

== Summary ==
Example Junction in Preview, drawn exactly as the game draws it.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor example map.png

4shveil — Fri, 09 Oct 2026 13:43:16 GMT

4shveil uploaded File:Map editor example map.png Image for the map editor guides

New page

== Summary ==
Example Junction, the small example map used in the map editor guides, with ids shown.

Screenshots are of the signaller.org map editor, taken from the example map built for the [[Map editor]] guides.

[[Category:Map editor]]

File:Map editor your maps.png

4shveil — Fri, 09 Oct 2026 13:43:16 GMT

4shveil uploaded File:Map editor your maps.png Image for the map editor guides

New page

File:Map editor screen.png

4shveil — Fri, 09 Oct 2026 13:43:16 GMT

4shveil uploaded File:Map editor screen.png Image for the map editor guides

New page

Category:Guides

4shveil — Fri, 09 Oct 2026 13:19:15 GMT

New category for how-to guides

New page

How-to guides for signaller.org: playing, signalling, and building maps of your own.

Category:Map editor

4shveil — Fri, 09 Oct 2026 13:19:15 GMT

New category for the map editor guides

New page

Guides to building, testing and publishing your own maps with the [[map editor]]. New to it? Start with [[Building a map]].

[[Category:Guides]]

Publishing a map

4shveil — Fri, 09 Oct 2026 13:19:14 GMT

New guide: publishing a map to the workshop, review, updates and removal

New page

When your map is ready, publish it to the '''workshop''', where other players find it, subscribe to it and play it in their games.

== Before you publish ==
* '''Save''' the map. The workshop gets the map as you last saved it, not unsaved changes.
* Run '''Validate map''' on the Check tab. The workshop refuses a map the game can't load, or one with no zones.
* [[Testing a map|Test it]] with trains.

== Publishing ==
# Press '''Publish''' in the toolbar.
# Give it a '''title''' (the name players see) and a '''description''' (what's on the map, and anything players should know).
# Press '''Publish'''.

The map then waits for review. Reviewers in the signaller.org Discord server check each map before it is listed. The Discord bot sends you a message when your map is sent for review, and when it is accepted or turned down, if you accept direct messages from the server's members.

== Where it's up to ==
Open the '''Publish''' tab again to see:

* '''Waiting for review''': nothing to do yet.
* '''Listed in the workshop''': players can subscribe to it. It also shows how many have.
* '''Not accepted''': with the reviewer's reason. Fix it, save, and publish again.

== Updating a map ==
Make your changes, save, then press '''Publish update'''. The update is reviewed like a new map. Meanwhile, the version already listed stays playable.

A game keeps the version it started with, even if you update the map while it's being played.

== Taking a map down ==
'''Remove from workshop''' unlists it. You can publish it again later; it will be reviewed again.

== AI-assisted maps ==
If you used the [[Map editor#AI assistant|AI assistant]] to change the map, the workshop labels it '''AI-assisted''' and lists it after maps made without one. The label stays for good, even after later updates.

== Playing a workshop map ==
Anyone can browse the workshop from '''Workshop''' on signaller.org's main menu. Subscribing needs a Discord sign-in, but you don't have to join the Discord server.

To play one, the host of a lobby opens '''Choose Map''' and picks a map they subscribe to. Nobody else in the lobby needs to subscribe. Every player then chooses a zone again.

[[Category:Map editor]]
[[Category:Guides]]

Testing a map

4shveil — Fri, 09 Oct 2026 13:19:03 GMT

New guide: the Check tab, Validate map, and testing signalling with trains

New page

Before you share a map, check it and run trains on it. The [[map editor]] uses the game's own code for both, so what works here works in a game.

== The Check tab ==
The '''Check''' tab lists problems as you edit, split into errors and warnings. Press the crosshair next to one to find it on the map.

Things it catches include:
* two signals, platforms or buffer stops with the same id,
* next signals, conflicts or routes that name a signal that isn't on the map,
* a buffer stop that isn't on a track end, so the game won't draw it,
* conflict rules that can never apply, and
* routes with no operator, no spawn variant, or no ending.

=== Validate map ===
'''Validate map''' runs the game's own map loader on your map.

* If it works, it tells you how many signals, routes and zones the game found.
* If not, it says why the game would refuse the map. Fix that first: the workshop won't take a map the game can't load.

A result marked ''(before your latest edits)'' is out of date; press Validate map again.

== Testing with trains ==
Press '''Test''' in the toolbar. The map is loaded into a test bench, and you can no longer edit it until you press '''Stop test'''.

=== Placing a train ===
# Choose '''Place trains''' (N) in the tools on the left.
# Click where the train starts: a signal, a buffer stop, or anywhere on a track.
# Click the signal or buffer stop it should run to.

The train takes the shortest way there in the direction it's facing. A train placed at a signal or buffer stop holds the block leading up to it, as if it had just run there.

You can set the train's '''Headcode''' and '''Stock''' before you place it, or type a start and end in the boxes and press '''Spawn'''.

=== Running the test ===
* Press play or pause, and pick a speed: 1×, 2×, 5×, 10× or 30×.
* The restart button clears every train and loads your map again.
* '''Signaller''' chooses who runs the signals:
** '''Nobody (all signals automatic)''': every signal clears behind trains on its own. Good for checking next signals and routes.
** '''You, zone …''': you control that zone's controllable signals, as in a game. They go back to danger after each train unless rollback is on.

Trains drive as in a game: they speed up, brake for red and yellow signals, and take time to react. There are no timetables, station stops or platform choices on the test bench.

=== Trains ===
Click a train in the '''Trains''' list to:
* '''Send to…''': click another signal or buffer stop for it to go to,
* '''Stop at next signal''', then '''Continue''', or
* '''Remove''' it.

The editor marks where each train really is and which blocks it holds.

=== Why is this signal red? ===
Click a signal on the map. The panel shows its aspect and why, such as which train is in its block, or which train is holding it through a conflict.

If you control it, you can also:
* choose its '''Route''' when it has more than one next signal,
* give it a '''Danger''', '''Caution''' or '''Proceed''' command, and
* turn rollback on or off.

The '''What happened''' list records each step, with the time.

== What to test ==
* Run a train along every line, both ways, with all signals automatic. A train that won't go where you expect usually means a missing or wrong next signal.
* At each junction, send two trains towards it at once on moves that cross. One should wait. If both go, a [[Conflicts in the map editor|conflict]] is missing.
* Send two trains on moves that don't cross. Neither should wait. If one does, a conflict is too broad.
* Run a train into each terminus, and check it comes in at caution.
* Choose your own zone and signal a few trains through, as a player would.

When it all works, [[Publishing a map|publish it]].

[[Category:Map editor]]
[[Category:Guides]]

Routes in the map editor

4shveil — Fri, 09 Oct 2026 13:18:13 GMT

New guide: making routes, spawn and turnaround variants, calling patterns and headcodes

New page

A route is a service that runs on your map: who runs it, which trains it uses, where they appear, and which way they go. Without routes, no trains run on your map in a game. You build them in the '''Routes''' tab of the [[map editor]].

Build routes last, once your [[Signals in the map editor|signals and next signals]] are done: a route follows the next signals.

== Making a route ==
In the '''Routes''' tab, press '''+''' (New route). Then fill in:

* '''Id''': a short name of its own.
* '''Operator''': Connect, Express, AirLink, Waterline or Metro. Trains show it, and a game's traffic settings use it.
* '''Name''': a longer name, such as ''Stepford Central – Airport''. Only the editor shows it.
* '''Trains''': leave this empty to run the operator's usual trains, or add the trains you want from the list.

== Variants ==
Each route has one or more '''variants''': the paths its trains take. There are two kinds.

{| class="wikitable"
! Kind !! What it is
|-
| '''Spawn''' || Where trains enter the game and the way they go from there. Trains only ever appear at a spawn variant's start.
|-
| '''Turnaround''' || Starts where the route's trains end. A train that ends there may turn round and carry on along it. Nothing appears there.
|}

A route with no spawn variant never runs.

=== Building a spawn variant ===
# Press '''+ Spawn'''.
# Give it a '''Headcode''' (see [[#Headcodes|below]]).
# Set its '''Spawn signal''': press the pick button and click the signal on the map. On the official map, every route starts at a shunt signal leading out of a siding or depot.
# Now build the path. Next to the last signal in the list:
#* '''Follow line''' adds signals along the line until it reaches a junction or the end.
#* At a junction, click one of the '''Next:''' suggestions to choose a way.
#* Or press the pick button and click the signals on the map, in order.
# Keep going until the path reaches its end: a buffer stop, or a platform trains can't go on from.

Each step must follow the signals' next signals. If it doesn't, the Check tab warns you, and the game will look for its own way along the track.

To let trains take more than one way at a junction, use the '''Also:''' suggestions, or the branch pick button, to add another way from the same signal.

=== Calling at stations ===
Each platform on the path shows as '''calls''' or '''passes'''. Click it to switch. Trains stop where it says ''calls'' and run through where it says ''passes''.

=== Building a turnaround variant ===
Add a spawn variant first; then press '''+ Turnaround'''. Its start is where the route's trains end, and the editor suggests those places for you. On the official map, turnarounds start at the buffer stop, or at the starter of the platform where trains reverse. Then build its path the same way.

How often trains turn round instead of leaving the game is set on the '''Map''' tab, under '''Traffic''': '''Continue (%)''' is the chance a train turns round at its terminus when its route has a turnaround there.

== Headcodes ==
A headcode is two characters: a class digit, then a letter for where the train is going. For example, '''2A''' is a stopping train to Airport Central. Trains add a number of their own, as in 2A04.

{| class="wikitable"
! Digit !! Train
|-
| 1 || Semi-fast
|-
| 2 || Stopping
|-
| 3 || Empty stock
|-
| 9 || High-priority express
|}

Signallers usually let trains go in this order: 9 first, then 1, 2 and 3; then late trains; then Express, AirLink, Connect, Waterline and Metro.

== Checking routes ==
The '''Check''' tab warns you when a route:
* has no operator, or no trains it can run,
* has no spawn variant, so no train will ever run it,
* has a step that doesn't follow the next signals,
* goes to a signal that isn't on the map, or
* has a turnaround where none of its other variants end.

Use the crosshair button on a route to select all its signals on the map.

[[Category:Map editor]]
[[Category:Guides]]

Conflicts in the map editor

4shveil — Fri, 09 Oct 2026 13:17:42 GMT

New guide: what conflicts do, a worked junction example, rules and clearance distances

New page

Conflicts stop two trains being sent onto the same piece of track at once at junctions, crossovers and flat crossings. They are the part of the [[map editor]] people find hardest, so this page goes slowly, with an example.

== Why you need them ==
[[Signals in the map editor|Signals]] keep trains apart along a line: only one train is allowed in each block. But at a junction, two signals on different lines can send trains over the same points, or across each other on the flat. Neither signal's block knows about the other train.

Without a conflict, the game will happily clear both signals, and the two trains meet.

Conflicts are needed at:
* junctions and crossovers,
* flat crossings (diamonds), and
* platforms trains can enter from both ends.

Tracks that pass under each other ('''Underpass''' track) never meet, so they need none.

== What a conflict does ==
A conflict is set on one signal, and points at another signal, called its '''target'''.

: '''A conflict on signal A, with target B, holds A at red while a train has just passed B.'''

It holds A at red until that train reaches B's next signal, or until it is within a set distance of it (see [[#Narrowing a conflict with rules|rules]] below).

Conflicts go '''both ways'''. If A gets a conflict on B, B gets one on A, so whichever train gets there first, the other waits.

== A worked example ==
Here a branch leaves Line 1 and crosses Line 2 on the flat:

<pre>
Line 1 --> A ----+-------------- A2 -->
\
Line 2 <-- B2 ------X------------ B <--
\
Branch \---------- A3 -->
</pre>

* Signal '''A''' is on Line 1, before the junction. It has two next signals: '''A2''' straight on, and '''A3''' down the branch.
* Signal '''B''' is on Line 2. Its next signal is '''B2'''.
* A train going from A to A3 crosses Line 2 at the X. A train going from B to B2 passes over the same X.

So these two moves can collide: '''A → A3''' and '''B → B2'''. A train going A → A2 never goes near Line 2, so it should never wait for B.

=== Step 1: add the conflicts ===
# Select signal A. In the Inspector, under '''Conflicts''', type B in '''Add conflict with…''' and press '''+'''. (Or press the pick button and click B on the map.)
# Select signal B and add a conflict with A in the same way.

Each conflict appears as a card. Under the target, the card says in plain English what it does:

: ''A is held at red while any train is past B, until that train passes its next signal.''

That's safe, but it is too strict: it also holds A when it is set straight on to A2, which never crosses Line 2.

=== Step 2: narrow it with a rule ===
On A's card, press '''Add a rule to narrow this conflict''', and fill in:
* '''Routed to (A)''': A3. The rule only applies when A is set for the branch.
* '''Routed to (other train)''': B2. It only counts a train past B that is heading for B2.

The card now reads:

: ''When set to A3, A is held at red while a train that is routed to B2 is past B, until it passes its next signal.''

Do the same on B's card, the other way round: '''Routed to (B)''' B2, '''Routed to (other train)''' A3.

The fields suggest the signals that make sense, so you can usually click a suggestion rather than type.

=== Step 3: let it clear sooner ===
As it stands, A waits until B's train reaches B2. But once that train's tail has cleared the X, A's train could safely go. '''Clears within''' lets the conflict end earlier.

: '''Clears within''' = the miles left from the crossing to B2, less about 0.06 for the length of the train.

Say B to B2 is 0.25 miles, and the X is 0.05 miles past B. That leaves 0.20 miles after the crossing. Take off 0.06, and '''Clears within''' is '''0.14'''. A is now held only until B's train is within 0.14 miles of B2.

Work out B's card the same way, using the miles from the crossing to A3.

== Narrowing a conflict with rules ==
A conflict with no rules counts any train past its target. Each rule narrows it. A rule applies when all its fields match; a conflict with several rules applies when any of them does.

{| class="wikitable"
! Field !! Means !! Empty means
|-
| Came from || Only count trains that came from these signals, before passing the target. You rarely need it. || any signal
|-
| Routed to (this signal) || Only apply when this signal is set to one of these next signals. || any route
|-
| Routed to (other train) || Only count a train past the target that is heading to one of these. || any route
|-
| Clears within || Stop counting the other train once it is this many miles from its next signal. 0 means when it passes that signal. || 0
|}

The rule the official map follows, which reproduces every conflict on it:
* Give A a conflict on B whenever a move from A and a move from B share track or cross on the flat. Then give B one on A.
* Add one rule for each pair of moves that meet: '''Routed to (A)''' is A's next signal, '''Routed to (other train)''' is B's.
* Two moves that join into the same next signal still get a rule, with Clears within 0.
* If every pair meets and every rule would have Clears within 0, leave the conflict with no rules at all.

== Checking your conflicts ==
* '''Hover over a conflict card''' to light up just that conflict on the map.
* With a signal selected, its conflict target is ringed '''red''', and signals with a conflict on it are ringed '''purple'''. Rule signals are ringed orange, yellow and teal.
* Under the cards, '''Signals with a conflict on''' lists the signals that point back at this one. If the one you expect isn't there, you've only added it one way.
* A warning on a field means the signal you entered isn't linked the way the rule needs, so the rule may never apply.
* The '''Check''' tab warns about a rule that can never apply because its Clears within is longer than any block after the target.
* Then run trains at the junction with '''Test''', and click a red signal to see why it is red. See [[Testing a map]].

== Common mistakes ==
* '''Adding it only one way.''' A waits for B, but B never waits for A.
* '''No conflicts at a junction.''' Trains are sent onto the same points at once.
* '''Conflicts between moves that never meet.''' Trains are held at red for no reason. Narrow them with rules, or remove them.
* '''Clears within too large.''' A clears while the other train is still on the crossing.

[[Category:Map editor]]
[[Category:Guides]]

Signals in the map editor

4shveil — Fri, 09 Oct 2026 13:16:34 GMT

New guide: placing signals, their settings, next signals and stopping at platforms

New page

How to place signals in the [[map editor]], what their settings do, and how to tell each signal where trains go next. Signals and their next signals are what trains actually follow: the track only shows the way.

== How signals keep trains apart ==
Each signal protects the stretch of line up to the next signal, called a '''block'''. Only one train may be in a block at once.

* A signal shows '''red''' while its block has a train in it, or while a [[Conflicts in the map editor|conflict]] holds it.
* Otherwise it shows '''yellow''' if the next signal is red, '''double yellow''' if the next signal is yellow, and '''green''' if not. (That is a 4-aspect signal; a 3-aspect one has no double yellow.)

More signals make shorter blocks, so trains can follow each other more closely.

== Placing a signal ==
Press '''S''' and click on a track. The signal faces along the track. Shift-click to face it the other way, or press '''F''' to flip one you've placed.

A signal works for trains passing it in one direction only. A track used both ways needs a signal for each direction.

A new signal takes its id and zone from the nearest signal, so check them in the Inspector.

== Where signals go ==
* '''At the far end of each platform''', in the direction trains leave it. This is the platform's starter, and it is where trains stop. Put it on the track 1 to 2 units past the end of the platform.
* '''Before every junction and crossover''', on each track a train can reach it from. These protect the points, and players usually control them.
* '''At the way out of every siding and depot''': a shunt signal.
* '''Before the platforms of a terminus''': the signal that lets trains in.
* '''Along plain line between stations''': automatic signals, about 0.2 miles apart.

== Types ==
{| class="wikitable"
! Type !! Use it for
|-
| 4aspect || Main lines. This is the default.
|-
| 3aspect || Slow branch lines.
|-
| shunt || Depots and sidings.
|-
| tram || Lines where tram-trains run in the street.
|}

== Ids ==
Every signal needs its own id. The official map uses two letters for the area and a three-digit number, counting along the line, such as SW 041.

If you rename a signal in the Inspector, the editor updates everything that refers to it: other signals' next signals, conflicts and routes.

== Settings ==
Select a signal to see its settings in the Inspector.

{| class="wikitable"
! Setting !! What it does
|-
| Type || See [[#Types|Types]] above.
|-
| Initial aspect || What it shows when a game starts.
|-
| Zone || Which player's area it belongs to. Every signal needs one.
|-
| Platform || The platform this signal stops trains at. See [[#Stopping trains at platforms|below]].
|-
| Controllable || Tick it if the player decides when it clears: at junctions, platforms, sidings, depots and terminus approaches. Leave it off for automatic signals on plain line. About half the official map's signals are controllable.
|-
| Rollback || Starts the game with rollback on: the signal goes back to the player's setting once a train has passed. Most signals have it off.
|-
| Speed (mph) || The line speed after the signal. With none, trains run at 45. The official map uses 30 in depots, sidings and into termini, 45 to 60 over junctions, and 75 to 125 on main lines.
|-
| Max aspect || The best aspect it may show. Set '''Yellow''' for a signal into a buffer stop, so trains run into the terminus with caution.
|-
| Allocation || How it picks a platform when the planned one is blocked. See [[#Choosing a platform|Choosing a platform]].
|-
| Route indicator || Puts a route indicator on top of the signal. The '''Ind.''' column under Next signals sets what it shows for each way.
|}

=== A starter that leads nowhere ===
Sometimes a platform starter faces a way trains can never go on. Give it no next signals, set '''Max aspect''' to '''Red''', and untick '''Controllable'''. It then stays red.

== Next signals ==
A signal's '''next signals''' are where a train passing it can run to: the next signal ahead in the same direction, on each way it can take. They are listed in the Inspector under '''Next signals'''.

To add one, either:
* type its id in '''Add next signal…''' and press the '''+''' button, or
* press the pick button beside it and click the signals on the map. Press Esc when you're done.

Rules to follow:
* '''Name the very next signal.''' If you skip one, trains ignore the signal you skipped.
* '''The two must be joined by track''' (not Unused track). The game sends trains along the shortest track between them, and won't load a map where there is none. Check that the shortest way is the way trains should go.
* '''One per way through a junction.''' Most signals have one next signal. A signal before a junction has one for each way through it.
* '''At a buffer stop''', the last signal's next signal is the buffer stop, which shows as TERM followed by its id, such as TERM3.

=== Distances ===
Each next signal has a distance in '''Miles'''. It sets how long trains take to get there, and where conflicts clear.

* Use the real distance if you know it.
* If you don't, divide the length of track on the drawing by 300. For example, 60 units is 0.2 miles.
* On the official map, they range from 0.13 to 0.4 miles.

=== Choosing a platform ===
When a signal's next signals lead to different platforms of a station, a train goes to the one its route plans. If that one is blocked, the signal picks a free one using its '''Allocation''':

* '''Overflow''': the first free one, in the order of its next signals. The official map uses this almost everywhere, so put the platform you'd rather use first.
* '''Random''': any free one.
* '''Increment''': each in turn.

== Stopping trains at platforms ==
Trains stop at a platform by stopping at a signal or buffer stop whose '''Platform''' setting is that platform.

* At a through station, set it on the platform's starter.
* At a terminus, set it on the buffer stop.

A platform with neither is never used.

At a terminus, the signal before the platforms has the buffer stops as its next signals. Give it Max aspect '''Yellow''' and a speed of about 30, and make it controllable.

== Seeing how signals connect ==
When you select a signal, buffer stop or platform, the editor rings the things related to it, with a key in the corner of the map:

{| class="wikitable"
! Colour !! Means
|-
| Green || A next signal: trains can run from the selection to it.
|-
| Pink || A previous signal: trains can run from it to the selection.
|-
| Red || A conflict target: the selection is held at red while a train is just past it.
|-
| Purple || This signal has a conflict on the selection.
|-
| Orange, yellow, teal || Signals named in a conflict's rules.
|-
| White || The platform the selection stops trains at, or what stops trains at the selected platform.
|}

If a signal's next signals ring the wrong things, or nothing, that's usually the first thing to fix.

[[Category:Map editor]]
[[Category:Guides]]

Building a map

4shveil — Fri, 09 Oct 2026 13:15:43 GMT

New guide: the order to build a map in, and drawing track, platforms, buffer stops and zones

New page

A step-by-step way to build a map in the [[map editor]], from bare track to trains running on it. Work through the steps in order, and check each one before you start the next.

== The order to work in ==
# '''Track.''' Lines join where trains should change track, and cross without joining where they shouldn't.
# '''Buffer stops and platforms.''' Buffer stops on track ends; platforms beside the track, named and numbered.
# '''Signals.''' A signal at the end of each platform, one before each junction from every side, shunt signals out of sidings and depots, and automatic signals along plain line. Each one facing the right way, with a zone. See [[Signals in the map editor]].
# '''Next signals.''' Tell every signal which signals trains can run to from it. See [[Signals in the map editor#Next signals|Next signals]].
# '''Conflicts.''' Keep trains apart at every junction, crossover, flat crossing and platform used in both directions. See [[Conflicts in the map editor]].
# '''Settings.''' Which platform each signal stops trains at, which signals players control, and speeds.
# '''Routes.''' The services that run on the map. See [[Routes in the map editor]].
# '''Check and test.''' Fix what the Check tab finds, then run trains with Test. See [[Testing a map]].

Save often (Ctrl+S). Nothing you do is saved until you do.

== It's a diagram, not a scale plan ==
The map is drawn like a signal box's track diagram. How long a train takes to get somewhere comes from the distances you give the signals, not from how long the track looks. So keep the drawing neat and easy to read rather than true to life.

== Drawing track ==
Press '''T''' for the Draw track tool.

* Click to put down the first point, then click again for each bend.
* To stop, click the last point again, right-click, or press Esc.
* Hold Shift to keep to 45° angles. Hold Alt to turn snapping off while you place a point.
* Ending a line on another track joins them and makes a junction.

Tips from the official map:

* Lay main lines across the screen, and only go up or down where the line has to turn.
* Put parallel tracks 20 units apart. A crossover between them is then one diagonal, 20 across and 20 along.
* Keep points on the 5-unit grid. Snapping (the magnet in the toolbar) does this for you.
* Leave a short piece of plain track before each junction, on every side trains approach from. A signal needs somewhere to stand there.

=== Joins and crossings ===
Two pieces of track are joined only where they share an end, or where one ends on the middle of another. If two tracks cross without a shared point, that is a '''flat crossing''' (a diamond): trains can't turn there, but two trains crossing it can collide, so it needs [[Conflicts in the map editor|conflicts]].

When you select a piece of track, the Inspector's '''Type''' sets how it works:

* '''Normal''': ordinary track.
* '''Underpass''': goes under the other track, like a bridge. Trains on it can't collide with trains above, so it needs no conflicts.
* '''Unused''': drawn faded. Trains never run on it.

== Buffer stops ==
Press '''E''' and click the end of a track. A buffer stop must sit exactly on a track end, or the game won't draw it.

== Platforms ==
Press '''P''' and click beside the track. A new platform takes its station name and number from the nearest platform, so check them in the Inspector.

* Put platforms 5 units from the middle of the track, parallel to it. They are normally 20 long.
* A platform serves the one track beside it.
* Platforms with the same '''Station''' name are one station. Number them 1, 2, 3 and so on.

A platform on its own does nothing. Trains stop at it only when a signal or buffer stop is set to stop them there. See [[Signals in the map editor#Stopping trains at platforms|Stopping trains at platforms]].

== Zones ==
Each zone is one player's area of control in a game.

* Every signal belongs to a zone (its '''Zone''' setting): the player who controls it.
* '''Zone borders''' (press '''B''') outline each zone's area on the map. Click the corners, then click the last one again or press Esc. Type the zone in '''Zones''' before you start.
* '''Labels''' (press '''X''') show station names. Size 4 is the size the official map uses. A label's '''Zones''' setting picks which zones show it; leave it empty to show it everywhere.

Use '''View''' in the toolbar to see the map as one zone's player will.

== Common mistakes ==
* A signal facing the wrong way.
* A next signal that skips a signal, or has no track joining them.
* A platform that no signal or buffer stop stops trains at.
* Junctions without conflicts, or conflicts between trains that never meet.
* Routes that start on plain line instead of in a siding or depot.
* Routes that never end.

[[Category:Map editor]]
[[Category:Guides]]

User:4shveil

Admin — Fri, 09 Oct 2026 13:02:51 GMT

Admin changed group membership for 4shveil: granted staff member

User:4shveil

4shveil — Fri, 09 Oct 2026 13:02:21 GMT

User account 4shveil was created