32 lines
1.3 KiB
HTML
32 lines
1.3 KiB
HTML
<link rel="stylesheet" href="/css/book-page.css" />
|
|
<link rel="stylesheet" href="/css/book-page.css" />
|
|
<section>
|
|
<h2>d OKAY , BUT...</h2>
|
|
<p>
|
|
There are situations in which distances and positions are supposed to play
|
|
an important role: what if there's a sniper atop a tower? What if a terrible
|
|
ritual tears open a chasm in the middle of the battlefield?
|
|
</p>
|
|
<p>The advice boils down to the following:</p>
|
|
<ul>
|
|
<li>
|
|
Don't overcomplicate things. Play to this game's strengths, and avoid
|
|
situations in which suspension of disbelief becomes too strained.
|
|
</li>
|
|
<li>
|
|
Sometimes, experiment. If you want to introduce distance as an important
|
|
element in the game, treat it as a "puzzle" that can be solved in creative
|
|
ways while the conflict progresses. For instance, you might make melee
|
|
attacks useless in a battle between two flying galleons — at that point,
|
|
engaging in close combat would require approaching and boarding the enemy
|
|
ship... time for a Clock!
|
|
</li>
|
|
</ul>
|
|
<p>
|
|
In the end, the most important thing to remember is that conflicts shouldn't
|
|
be resolved through careful movement and positioning, but through clever use
|
|
of the character's Skills and actions.
|
|
</p>
|
|
<p>Philip Forlenza (Order #)</p>
|
|
</section>
|