From: Chris S. <chr...@gm...> - 2008-10-25 01:23:34
|
> 5. I use the term Revenue Center specifically, because it is an object that > produces revenue. A Junction is simply a connection point between two or > more track segments. I don't see a Junction object as having any real value. > Or put another way, I double a Junction object would have any code at all > associated with it, and no data either. It is purely an abstract concept. Some games allow re-use of the tiny bit of track at the center of a plain track X tile, others do not. Thus, in some cases, a junction is an important concept. > The code base is designed so that when I get to the point of selecting a > track route, you go from point-to-point. If a point has a Revenue Center, > you add that to you run (or not, if the train type and game allows you to > ignore it). The selection code would not allow you to select a track segment > already used by another train in the same operational step. Note that the TGV in 1826 can re-use track. > 9. Erik mentioned the need for a hex name "A1, B2, etc". If you launch my > current product, and then let you mouse hover over a hex, a tool tip shows > you the cell name. Note that it is very important that this matches the notation used on the printed version of the game. I think you might have said you were accounting for that, but wanted to be sure it's included. > 11. I do track Red-Off Board cells as having a special type of location > "dead-end" where the code would allow you to stop (or start) a train at, but > not pass through. They also need to be counted as a location that some trains can't visit - in 1844, H trains cannot go to off-board hexes; in 18Scan, you can only go to an off-board hex if you have a token in it, etc. -- Chris Please consider the environment before printing this e-mail. |