more info on train moves in history. train info added to tooltip on timetable and division map. support for multiple trains in area switching. more info on train7/8 wrt location of coach on initial train build.
This commit is contained in:
+10
-1
@@ -120,9 +120,18 @@ export function timetableHtml(f: Frame, justSet: number | null): string {
|
||||
]
|
||||
.filter(Boolean)
|
||||
.join(' ');
|
||||
/**
|
||||
* THE CARD ITSELF, not just the number.
|
||||
*
|
||||
* A train card is played once and then lives only as a number in a Timetable slot — but what
|
||||
* it prints is what decides whether the train can be switched, worked by Porters, or loaded at
|
||||
* all. Reported from play: "once a train card's been played, how would I see that particular
|
||||
* train card again?" This is where the player already looks for that train.
|
||||
*/
|
||||
const tip =
|
||||
t !== null
|
||||
? `Train ${t} departs at Stage ${stage}. A train's NUMBER is its seniority and direction — odd runs west, even runs east — and the Stage it leaves is set by the 1D12 roll made when its card was played, so Train 8 at Stage 6 is normal.`
|
||||
? `Train ${t} departs at Stage ${stage}. A train's NUMBER is its seniority and direction — odd runs west, even runs east — and the Stage it leaves is set by the 1D12 roll made when its card was played, so Train 8 at Stage 6 is normal.` +
|
||||
(f.timetableWhat[k] ? `\n\nITS CARD — ${f.timetableWhat[k]}` : '')
|
||||
: `Stage ${stage} — no train due out.`;
|
||||
return (
|
||||
`<div class="tt-slot ${cls}" data-tip="${esc(tip)}" tabindex="0">` +
|
||||
|
||||
Reference in New Issue
Block a user