| | Re: BrickFest TimeSaver Layout
|
|
(...) I would strongly favor counting moves as uncoupling really could take a fair bit of variable time. I also would not penalise someone for accidentally recoupling right after uncoupling, it is SO easy with these speed regs to go in the wrong (...) (22 years ago, 30-Apr-02, to lugnet.trains.org)
|
|
| | Re: BrickFest TimeSaver Layout
|
|
(...) Yes, typically that is how it is graded, however, I recently learned that the original article in the 1972 (I think) Model Railroader magazine called for it to be timed. So I think we can use whatever method works best. (...) I agree, the (...) (22 years ago, 30-Apr-02, to lugnet.trains.org)
|
|
| | Re: BrickFest train events and displays
|
|
(...) Congrats. Tom sent me (as curator) an offline note about holding train related BrickFest discussions here, in the root of the trains.org hierarchy, asking my opinion. I wanted to say publicly that I think it's a good fit and we ought to (...) (22 years ago, 30-Apr-02, to lugnet.trains.org)
|
|
| | Re: BrickFest TimeSaver Layout
|
|
(...) Note (to the uninitiated, everyone that knows who John Allen is already knows this) TimeSaver is a bit of a misnomer, it's really MOVEsaver, as in you are judged on total number of moves to solve the puzzle, not the elapsed time. A move is a (...) (22 years ago, 30-Apr-02, to lugnet.trains.org)
|
|
| | BrickFest TimeSaver Layout
|
|
As part of the Train activities for BrickFest, I am planning a switching puzzle game based on John Allen's TimeSaver layout. One attempt at a LEGO track plan is: (URL) you are interested, please take a look, and let me know what you think. (22 years ago, 30-Apr-02, to lugnet.trains.org)
|