Steve Jackson Games - Site Navigation
Home General Info Follow Us Search Illuminator Store Forums What's New Other Games Ogre GURPS Munchkin Our Games: Home

Go Back   Steve Jackson Games Forums > Roleplaying > GURPS

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
Old 12-05-2014, 06:36 AM   #17
Langy
 
Join Date: May 2008
Location: CA
Default Re: [TS] Slicing the pie, a question?

Quote:
Originally Posted by vicky_molokh View Post
Huh? In that case, nothing prevents Waiting and Attacking at the same time. Now, that doesn't seem to make sense.
A state-of-conditional-Waiting is when a character does nothing unless the trigger event registers. If you're placing the Step outside the conditional block of the turn, then it's not part of the conditional block.

Otherwise the following situation becomes possible:
Opponents both have a Reach 1 weapon.
A declares a Wait, opting to whack B if B steps into Reach 1.
B does a Step And Wait, with the wait condition being 'when A is in reach' and the action being 'whack A'.
As B Steps, B becomes in range, and B's Wait is triggered, allowing to contest A's priority.
This way, B gets the best of both worlds, with no drawback.
What prevents Waiting and Attacking at the same time is that those are two separate maneuvers. Step and Wait aren't separate Maneuvers. They're something that can be done at the same time - just like you can Attack and Step at the same time, not having to Step prior to the attack or after it.

Also: Why do you think that A should automatically have priority in that situation? Making it a contest actually seems to make some sense as opposed to always prioritizing the person who gives up the initiative.
Langy is offline   Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Fnords are Off
[IMG] code is Off
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 04:16 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.