Conflict v. Task Resolution: An Outmoded Distinction?

Hi all,

My latest thoughts on Task vs. Conflict resolution are that rather than calling them different kinds of resolution, we should think of them as different factors involved in resolution in toto. I'm thinking of something like - whenever you resolve anything in an RPG, you will be resolving both Task(s) and Conflict(s). Something will be at stake (the conflict(s)), and something will be done/attempted (the task(s)) in the context of that. The question is: who knows the details of the Conflicts and the Tasks at hand, and how does our system allow us to address them?

What I'm reading in this thread seems to me more evidence that such a construction is a good idea - but then, it's no surprise that I'd see support for what I've been thinking of late. Still, this seemed like a good place to put that thought down in "print."

Gordon