Auzzy
commented
5 years ago Deployed in a series of commits:
- https://github.com/Auzzy/1846-routes-web/commit/154de5548b188c518b7f7d4beacd8374e29167f6 - Add dropdown and labels to mark railroads as removed.
- https://github.com/Auzzy/1846-routes-web/commit/b4e585853ca1f81173e0222c3611a467baf7fe55 - Add special value when importing railroad to mark it as removed.
- https://github.com/Auzzy/1846-routes-web/commit/1b656bd5e9915d67d7b3e7b08a4bf7562011685f - Instead of allowing all railroads to be removed, allow only the 3 denoted by the game rules.
- https://github.com/Auzzy/1846-routes-web/commit/aca742d3f29609269695fc43107bdda98f23bd54 - Draw a station on the home city of each removed railroad, to signal that it's impassable.
- https://github.com/Auzzy/1846-routes-web/commit/c38b449fd6b72cd93227b448ae7c0e3ad7449a5b - Include the removed railroads in the calculation. That is, this commit actually uses all the data established in the previous commits.
I overlooked a route rule: the home city of a railroad removed from play (due to less than 5 players) cannot be run through. My app currently has no way to differentiate between an unfounded railroad and a removed one; clearly, it needs one. The answer is not to just add all the railroads always; the home cities of unfounded railroads which have not been removed from the game are fair game to pass through.
In the mean time, the work around is to add the removed railroads to the game. This will place their home stations, preventing their home from being run through.