This may come in handy.

One of the beauties of moderation is You Decide. \o/

There is the Everythinghappensatthesametime way of moderation.

There is also a NaturalActionResolution way. I'll post something from a document I've had forever:


Natural Action Resolution

The Golden Rule
Apply actions which modify other actions before the actions they modify.
Applying the Golden Rule in Three Easy Steps
Find an action such that its effect cannot possibly be modified by any other action.
Resolve it.
Repeat from step 1 until all actions are resolved.

Paradox and Ambiguity

Sometimes the actions that might affect each other form a loop, so that there's no action to pick in step 1. In other cases, the order of two actions matters but it isn't clear that one affects the other. When that happens, pick an action to resolve in this order:
Copy
Hide/commute
Bus/Redirect
Block
Protect
Miscellaneous
Kill
Recruit
Inspect/Investigate
Count minor modifications of the actions listed above the same as the basic action (e.g., randomize would be the same priority as redirect). For actions which combine two other actions use the first one listed.
If the list still doesn't narrow it down to a single action, pick one of the best candidates using any fair method, such as randomized.
Resolve the action you picked this way, then go back to the golden rule until you get another cycle. Usually one or two picks are enough to make everything work.

Killing

Killing doesn't stop the actions of the dead player. (Imagine that all kills happen at the end of the night, and everyone pulls the trigger simultaneously.) Killing a recruiter won’t stop the recruitment from occurring. Killing a killer won’t stop the kill. Killing a gift giver won’t stop the given gift.

Roleblocking

Passive actions (godfather, loved/hated, night talk) may not be roleblocked unless otherwise specified.
Triggered actions may or may not be roleblocked. See specific roles for more info.
Night actions involving a player sending in a choice can usually be blocked.
Day actions may or may not be blocked by a previous night’s actions.
Triggered Actions
Some roles might take actions that are triggered by other actions. For example, a Paranoid Gun Owner will kill if targeted by an action. Resolve triggered actions along with the regular actions, using the golden rule as normal. Any action which triggers when a player is targeted should "go off" between steps 1 and 2 (Applying the Golden Rule in Three Easy Steps), before resolving the action that triggers it. When that happens, stop and go back to step 1, this time considering the triggered action as well.

Ninja'ed


Yep...what he said.

Thanks! My setup would require some less common roles, so I should read into that as well.

But I can see already that modding, if done right, is rather rewarding experience.

Sounds like a creative part. For now I should read into what Krypsyn and flubbucket suggested, but as you already mentioned, it's highly possible I would have to create a more particular system to suit the game better. As in, mechanics that make sense.

For my LOTR-spoof game, every character had an AGI stat. That stat was the action resolution order. :)

That's actually pretty much exactly what I came up with, though I went with suicide bombers over vig. Game resolved N1, and everyone wins.


Anywho, Lift's game involved determining action priority based on RL time of when the action was submitted. My team was first to figure it out but I still really wasn't a fan. I ended up staying up too late / waking up early trying to make sure I was online when the day closed.

Wasn't good for my health. So can it be done...sure. But I don't recommend it.

You do definitely want to think through the implications not just of order but how design of one role impacts another. Yogs' example of the "tracker problem" in the last game was a good one.

The affect it had on my group was that we never got a kill because, even though I thought it was a possibility/presented the idea, everyone else said "no way that can't be it" and we decided it wasn't like that and functioned as normal scum-chat. It was interesting, but I didn't like it ultimately because it was not balanced.

C'mon next gaaaame!

Suitable reaction :D Note to myself: never base actions on time submitted - people may murder buildings.

BUILDING LIVES MATTER

Lol - the funny thing is that I proposed it as an idea (as drealmer did) but I didn't really think it was it because it seemed a bit unfair. Trent/Dedo looked at my list of theories and came down pretty firmly that time was probably the right guess, and sure enough...

When I was bluffing on the final day when cristi asked how it worked that we'd managed to get 3 kills off in 4 nights, I think I implied that the proper solution involved bribing the mod. :)

Yeah, I think there's not much funny about lying to the players as moderator. Pretending to give players night actions and then simply ignoring them due to something as capricious and unfair as time stamp - and not explaining any of that - sucks. Sucks hard.

Imagine a game where everyone bribes mod and in turn, does whatever they want. Oh, that sweet chaos... And so much pizza for mod... With pineapples and all.
It was fun reading observer's thread when after dedoporno made the bluff, you shouted how much you love lying. I can only imagine all the conspiracy theories our dear observers had in minds

Lying as a player is sweet, beautiful, golden music.

Lying as the moderator should be punishable by having your stuffed animals peed on and set on fire.

Technically if you parsed Lift's PM responses carefully, there were hints there. For example, I left my room, I had a gun - had to abort when I heard other gunfire. So it was clear that someone's kill got off before mine, and it was down to trying to puzzle out why.

That's basically what I spent all of D2 doing, and it panned out.

Which is, you know, why my team totally won that game.




Oh, no wait, we lost to the team that didn't get a single kill off and just lurked to victory by letting all the other teams blow each other up. ;)

I will stop agreeing just before the word "by" appears here