*
*
Home
Help
Login
Register
Welcome, Guest. Please login or register.
November 27, 2014, 06:20:49 AM

Login with username, password and session length
Forum changes: Editing of posts has been turned off until further notice.
Search:     Advanced search
46709 Posts in 5588 Topics by 13297 Members Latest Member: - Shane786 Most online today: 33 - most online ever: 429 (November 03, 2007, 04:35:43 AM)
Pages: [1]
Print
Author Topic: [Polaris]  (Read 1255 times)
Salsa
Registree

Posts: 2


« on: October 01, 2011, 10:11:19 AM »

http://indie-rpgs.com/archive/index.php?topic=29465.msg274363#msg274363
Quote from: Ben Lehman on March 10, 2010, 09:46:35 PM
I don't like it when conflicts skip big amounts of time. As the Mistaken, I would close the conflict after "but only if he follows the trail of blood and catches up to the assassin three blocks later." with a simple "and so it was that Fornax came across the assassin only to discover it was Dr. Cygnus." Basically, apparently the scene we've set is not what we're actually interested in, so let's just jump to what we want, plus play hand-off with the Moon and get him involved in play.

Although, I'd like to note that the Heart has no "it was not meant to be" option against "and so it was."

I've read this reply by Ben on the archives, and I was wondering. If someone simply cuts off another with "and so it was" that would make "and that's how it happened" kind of useless. Right? Unless, by "and so it was" you mean the beginning of another scene just after the "and that's how it happened". Or that you actually meant "and that's how it happened" instead of "and so it was" in that last sentence.

I was so close to understanding, until I read this. :(
Logged
Ben Lehman
Member

Posts: 2183

Blissed


WWW
« Reply #1 on: October 03, 2011, 09:32:02 AM »

"And so it was" ends the scene. No response is allowed against it.
Logged

Frank Tarcikowski
Member

Posts: 387

a.k.a. Frank T


WWW
« Reply #2 on: October 03, 2011, 12:54:27 PM »

I think the examples in the linked thread are confusing. It kind of looks like the whole scene was played as a conflict, which is not at all how it's supposed to be done. The way the players use every key phrase to turn what the other player has established into something entirely different seems pretty frustrating to me. Rules-conform, sure, but poor play to my taste. As fore the rules question:

My understanding of "and so it was" is that if it ends the scene, nothing is allowed to follow after it. And furthermore, my understanding is that you'd have to resolve a conflict with one of the conflict-ending key phrases before you can end the scene. Correct or incorrect?

- Frank
Logged

BARBAREN! - The Ultimate Macho Role Playing Game - finally available in English
Salsa
Registree

Posts: 2


« Reply #3 on: October 06, 2011, 03:50:47 PM »

My thought exactly. So it should be "and that's how it happened" before "and so it was" I never doubted this key phrase ended the scene, but i don't think it's supposed to end a conflict. Which would render pretty much every other conflict-ending phrase useless. I would just need to be quick enough to say "and so it was" and include something in there the player didn't want and he wont be able to respond to it (which is a rules-breaker in my opinion).

I don't think that impairing how one can use the key phrases will do any good either. Of course some would prefer short and small scope "But only ifs"  instead of the "time-space modifying" kind but indeed is too hard to get players to understand that and soon they will be complaining about the numerous sub-conflicts within a scene that could have been solved in a single conflict and ending the scene. I prefer the former but I don't think the latter is poor play, some people don't roleplay that much and prefer to describe a series of chained actions.

Anyways, guess i wasn't wrong after all. I could really use an official take on this.
Logged
Pages: [1]
Print
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines
Oxygen design by Bloc
Valid XHTML 1.0! Valid CSS!