martian-a/greenwood

Analysis of the game Ticket to Ride

greenwood

Analysis carried out as background research while developing a new Ticket to Ride map (fan contribution) based on West Dorset. Includes assets for West Dorset game.

greenwood's Issues

Total carriages

Per game. State how many carriages each player starts the game with.

Starting hand

How many tickets is each player dealt? How many must they keep?

How many carriage cards is each player dealt?

Create a view of the printable board that shows only segments of track of a single length

For example, all (and only) the segments that are 6 carriages long. Need to be able to produce a separate view for each of the unique segment lengths on the board, typically: 1, 2, 3, 4, 5 and 6 carriages long but sometimes longer.

Create a view of the printable board that shows only segments of a specific colour

For example, all (and only) the segments that are red. Need to be able to produce a separate view for each of the unique track colours on the board, typically: red, orange, yellow, green, blue, pink, white, black, grey.

Set structral edges to opaque in tickets network

Should be possible using hidden.

Freeze network visualisation in place

Add a control to the interface that enables a user to stop the network visualisation from moving of its own accord. User should still be able to move nodes manually.

Add sub-menu to routes tab

Present each sub-section (Options, Double Routes, Tunnels, Microlights, Ferries) as an individual tab. Only show the menu for these tabs when the main "Routes" tab has been selected.

Rename "Options" to "Overview" or "Summary".
Rename "Double Routes" to "Double".

Write stylesheet that collates the cards in a printable document

For example a PDF. Currently, the result needs to be laid out for printing on labels.

Optimise for speed

Consider this approach: https://twitter.com/dracos/status/868103849193742337

Revise data model for double routes

The Nordic Countries map features a double route with each option having different ferry requirements. They're currently represented by nesting the asset requirements within the colour expression.
Change so that colour elements no longer also represent a route option. Instead, use an explicit option element.

Before:

• route
  -- colour
  ---- asset
  -- colour
  ---- asset

After:

• route
  -- option
  ---- colour
  ---- asset
  -- option
  ---- colour
  ---- asset

Stations

Per game. How many does each player start the game with? Typically 0, but sometimes 3.

Style tables in Routes

Zebra striping? Try using board colours on the columns, ie. red board colour for the red column.
Aim is to make each table easier to read. Keep the styling consistent across all the route tables.

Ticket values summary table

In game view. So can see the range of points available and which are most common.

One row per unique ticket points value. State total number of tickets of that value.

Rule book

Generate custom rule books for each game.