Reply to thread

Message: <blockquote data-quote="Skywalker" data-source="post: 4970854" data-attributes="member: 1538">One thing I will add here is that remember that just because a Skill Challenge has started does not mean that every Skill Check will have a bearing on it. Some Skill Checks will only an indirect bearing through the granting of bonuses i.e. Secondary Skills. However, some Skill Checks will have no bearing on the SC whatsoever.Some players do tend to become suddenly super-focussed when a SC is announced, and expect that the SC will be resolved before the game moves on. This isn't the case. I suggest running some session or multiple session long SC to try and help players get past this issue.I think this also impacts on keterys issue with matching Complexity with the flow of RP. When setting up a SC, I generally come up with a number of "milestones" equal to the number of successes called for by the Complexity. These milestones are actions that significantly progress the PCs toward the success result of the SC and can be kept broad. For example in a Complexity 1 negotiation SC where the goal is "Win over an NPC", the milestones might be:1. Overcome cultural differences.2. Notice the powerplay behind the scenes.3. Reveal the powerplay so as to neutralise it.4. Win over the NPC.What the PCs do to acheive each of the above is left to their own devising. However, if the PCs, go off on a tangent to win over another NPC or something else, then Skill Checks related that seperate goal will not add Successes or Failures to this SC. If the SC becomes redundant due to the PCs' tangent, then simply end the SC and create a new one or move one.The question then becomes should a GM let a player know in advance when a Skill Check will impact a SC or not before the roll. IMO, the GM should. Not only will that add more tension to the roll as the player will have more invested in the outcome but I think that level of transparency is important as it ties together the previous revelations of the SC commencing and its  Complexity.</blockquote>

Verification