Reply to thread

Message

<blockquote data-quote="ccs" data-source="post: 7927935" data-attributes="member: 6803664">Well, I've been running this series (either the individual&nbsp; modules or the compilation) every&nbsp; few years since the mid 80s, &amp; checking 1/HR has always worked well enough.But hey, maybe it's just how the dice have rolled &amp; the next time I run it the curve will catch up &amp; things'll go south via constant random encounter.....(In my games The random encounter&nbsp; dice are rolled by the players.&nbsp; I don't tell them the trigger range &amp; I change the exact #s daily. It's written down.&nbsp;&nbsp; So if you figure out encounters happen 1/6 or whatever? , you won't know wich # triggers it - in case you want to try &amp; avoid stuff by telling me the wrong #, knowing I'm not going to come over &amp; look at what you rolled)And not everything on the charts is (or has to be) a combat/rest interrupting encounter.&nbsp; Additionally I've had encounters where the distance between the party &amp; the ? Put them on opposite sides of a dune.The most amusing of those:One 3x play through saw an ongoing joke develop as multiple nights running the dice gave one particular player a herd of donkeys passing the camp on thier watch - on the other side of the dune.&nbsp; The player never made a single perception check to notice them.&nbsp; The dice indicated the donkeys travel direction wich never crossed into the camp.It became a joke - &quot;HOW do you not ever notice these donkeys that are trailing us???&quot;No combat occured, no rest was interrupted.&nbsp; It was just something going on near the party.</blockquote>

[QUOTE="ccs, post: 7927935, member: 6803664"] Well, I've been running this series (either the individual modules or the compilation) every few years since the mid 80s, & checking 1/HR has always worked well enough. But hey, maybe it's just how the dice have rolled & the next time I run it the curve will catch up & things'll go south via constant random encounter..... (In my games The random encounter dice are rolled by the players. I don't tell them the trigger range & I change the exact #s daily. It's written down. So if you figure out encounters happen 1/6 or whatever? , you won't know wich # triggers it - in case you want to try & avoid stuff by telling me the wrong #, knowing I'm not going to come over & look at what you rolled) And not everything on the charts is (or has to be) a combat/rest interrupting encounter. Additionally I've had encounters where the distance between the party & the ? Put them on opposite sides of a dune. The most amusing of those: One 3x play through saw an ongoing joke develop as multiple nights running the dice gave one particular player a herd of donkeys passing the camp on thier watch - on the other side of the dune. The player never made a single perception check to notice them. The dice indicated the donkeys travel direction wich never crossed into the camp. It became a joke - "HOW do you not ever notice these donkeys that are trailing us???" No combat occured, no rest was interrupted. It was just something going on near the party. [/QUOTE]

Verification