When creating layouts specifically for scenarios that are few questions we must keep in mind. Am I creating this Layout/Scenario for me or am I creating it for someone else to make a scenario from it? Assuming you are making a layout for someone else to make a scenario from it. If this is the case than there are a few things to keep in mind. First, we do not want to confuse the scenario creator, since it takes so much time to layout all the triggers, markers, junctions, and station names. We want to keep the layout simple. Simple, in this case, just means that you must have a direction, guide and goal in mind.
Example:
1. Direction : Amatrak leaves NYC at 6:33am & arrives at Boston at 10:11am
2. Guide: How much information are you willing to provide the player?
3. Goal: What do you want to accomplish at the end of the scenario?
In creating a layout for a scenario there must be a "START" point and a "STOP" point. This is your direction.
Guide is how many triggers you will use to inform the player of valuable information such as "Trackworkers, slow down", "Red light ahead"... basically anything you want.
For me I see the goal as an extension to another scenario. Ex: I completed a scenario using Jeff Morris' IRT 7 Line. At the end of the scenario you are ask if you want the second shift. Of course, the second shift is the second scenario. Anyways, I believe a train doesn't have an ending, only beginnings.
Also, it's always a good idea to write things down on a notepad or wordpad on your computer.
Below is a guideline from Paulsid, Peter5, Shutter, Adamasloco, Audace, Smileyman. This is how they name their junctions. triggers, markers, stations:
FROM PETER5
Trigger = t
Trackmark = m
Junction = j
Signal = s
No spaces and Title case
Example:
tBigYardApproach
jBigYardN
jBigYardS
mBigYardEmpties1
mbigYardLoads2
sBYNE
For signals I like to keep it short so they will display on the little name boards in Driver.
FROM ADAMSLOCO
I named the stations by names of cities in my area/past (Norwich, Midland, Barrie, Brockville, Ottawa, etc), and Named Triggers with the additional T at the end. Junctions were named according to purpose/city and track marks I added TM to the end. Ie.
Barrie NCOL - Cross over junction to the north or Barrie Station, Point 1 (numbered clockwise from Northermost point).
Mine 4 TM - Mine track 4, Trigger in the Barrie Station on the East Track.
Signals, I didn't unless I needed them directly. They are named after the junction, plus S on the end.
FROM AUDACE
I usually use the form prefix+number:
Trigger: T1, T2,.... T23 and so on;
Junctions: J1, J2.... J34 and so on;
Signals: S1, S2..... S12 and so on;
FROM ISH
Warnings, Stations, and Overruns I use Smileyman's WARN1, STAT1, ORR1...
But for triggers I have used
T1M1, T2 M1, T3M1...
T = Track, (#) id's Tracks 1,2,3...
M = Messanges, (#) id's messages for specific tracks Ex: T1M2, T3M3...
Station Signals: SS1, SS2
Junctions are tricky because the wrong junction can throw off your scenario. So I only name those I'm going to used, plus it saves time writng command after command. In the config file i will instruct the player not to touch any junctions unless call for. Ex: Manual T3J2
I strongly recommend this site if you want to learn more on how to name triggers, junctions, and markers.
IMPORTANT NOTE:
If you want a "around-the-world" scenario than name all triggers, junctions, stations, and markers. The scenario creator will use TrainzMap to find him or herself around the map
Also, please be aware that scenario creators just need a layout since they enjoy making the scenario instead of trying to figure out what the layout creator wants. If this is the case than I believe both parties can work together. Layout creators throw their layouts out there and Scenario creators would just select. If a layout creator wants someone else to write his or her idea of a scenario than I suggest you become buddies, because scenario takes a very long time, lots of e-mails, and communication to complete.
