Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="howandwhy99" data-source="post: 6412540" data-attributes="member: 3192">A game module is basically a calendar map which when generated into a session scenario includes a breadth of time for players to investigate in. Just use that scenario calendar to note current time in the game (like a game piece on a map) for days, weeks, months, and so on. For time periods within a day I like to use a dice clock. A d12 (or d24) for hours, d6 for Turns in an hour (10-minutes), and d10 for Rounds (1-minute). Other dice can be used as special cases dictate.A nice thing about dice clocks is you can set other dice down next to it for Time-Based Effects. For example, a spell in combat may last 5 rounds. You can set a different colored 1d10 next to the clock's with the appropriate finishing round number face up.Effects lasting in Turns and Hours are simple too. If stopped short just check how much time is remaining, like for a 1 hour torch, and note it next to the item.Exactly. It's a game. The players can screw things according to their actions. Or can actually save the day. It's why it's also a good idea to track location on a map too.Unless players own (and carry around) those massive water clocks they basically don't know what time it is. The referee can only ever tell them what their characters can sense. They know the sun and moon in the sky. But maybe they've studied the stars turning at night? Have measured the lengths of shadows and have access to a sun dial. Or maybe they make their own shadow clock? Accurate time tracking is essential to refereeing. Allow the Players to game with their ability being rewarded for at tracking time is the same as when they map or log something. Or not when they judge it's not important.</blockquote>

Verification