Clarify Rules for train times when hiding #16
Labels
No labels
Build Infrastructure
Card Clarification
New Card
New Rule
Rule Clarification
Status
Approved
Status
Finished
Status
Pending Discussion
Status
Tacit Approval
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JetLag/house-rules#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Do we want to optimise for a longer hiding time? Or do we want to optimise for a specific amount of time in which to hide?
Expanding on that: In the hour between 9am and 10am at Nürnberg Hbf there's a bunch of ICEs that leave at 9:00, 9:01, 9:03, 9:05. There's also another bunch of ICEs that leave at 9:25, 9:28, 9:29, 9:31 and 9:36. Most of those are to Munich and Berlin, but there's an IC at 9:41 that leaves to Karlsruhe, and arrives after 12:00, but before 12:41.
Do we say "Your hiding time is 9am to 12pm" or do we say "As long as you leave between 9 and 10, and don't take more than three hours on trains". Similarly, would a train that leaves at 08:59 be allowed?
Similarly, what if the hider gets Deutsche Bahned on the way to their chosen location, but the seekers have already started? Obviously this is to a certain extent contextual:
I know both @kitty and I have selected interesting places to go to, and I think we would prefer to go to those locations rather than have to settle for somewhere less interesting or well-researched.
The response to these questions may also imply that the first hider has to start in the same location as the seekers an hour earlier, even on the first game.
For the record, the April version of the house rules state that:
Up to 65 mins flexibility
3 hours travel time
3h 5 mins or similar is allowable
Optimise for game experience for everybody
Issue moved here from: moof/jltg-eu#50