Die rolls: for conflict resolution, or task resolution?

Post/Author/DateTimePost
#1

Foxface

Oct 28, 2011 21:43:47
Because it deserves its own thread, and it doesn't need to take over my other thread (even though it is kinda sorta somewhat related).

So yeah, the topic.  Conflict or task resolution?

For me, I like it as conflict resolution.  If there is no conflict, I and my players roll no dice.  Non-conflict moments are handled by narrative exposition, with our conceptions of our characters and the overall tone of the campaign governing what we do and how we do it.
#2

Kalnaur

Oct 28, 2011 22:18:41
Because it deserves its own thread, and it doesn't need to take over my other thread (even though it is kinda sorta somewhat related).

So yeah, the topic.  Conflict or task resolution?

For me, I like it as conflict resolution.  If there is no conflict, I and my players roll no dice.  Non-conflict moments are handled by narrative exposition, with our conceptions of our characters and the overall tone of the campaign governing what we do and how we do it.



Both and neither, as my whim as DM commands. ;)

By which I mean that I can see asking for a roll to perform what might be thought of as a simple task if I either think of a way to make it interesting, or if I'm feeling puckish.

Always or almost always for conflict resolution though, unless the passive skill check would just beat the pants off of the difficulty of the task as I had or would set it. Also subject to terms and conditions, as it were.

#3

OleOneEye

Oct 29, 2011 7:38:39
Please define what the difference is between conflict and task resolution.
#4

Herrozerro

Oct 29, 2011 8:29:13
my understanding is that task resolution is just as it sounds, to get things done.  While conflict resolution is related to the conflict of the story.

I guess he is saying for instance, a character wants to do something that is unrelated to the plot or something not integral to the plot.  They just do it.  Because it is of no consiquence to the plot.  However dice should be rolled if it moves the story foreward. 
#5

Hocus-Smokus

Oct 29, 2011 9:16:39
For me, these two terms are virtually synonymous.

By my D&D interpretation (which might not agree with anyone else's):

Conflict: Anything that has a chance of failure and a predetermined (by either the DM, player, or RAW) outcome for success and failure. Usually initiated by the DM through storyline (combat, SCs, etc.) and is a significant milestone for the storyline.

Task: Same as above, though it is typically not as significant to the storyline.

While I might not mandate that dice be rolled for either conflicts or tasks, I typically will. The results can help sway the storyline in various directions.
#6

Garthanos

Oct 29, 2011 11:12:06
Unless a task is dynamic ie has opportunities for back and forth ie choices and implications and as you say significance to the story... I dont think it even needs mechanical representation..dice or otherwise. It can be purely dm or player decided.