vBulletin LTS

Per user Edit/Deletion flood control (plugin)
Mod Version: 1.00, by bairy

What does it do
There are two parts to this.
1. Allows you to specify users who cannot edit or delete their posts.
2. Has an optional trigger to catch people who delete or edit too many of their posts in too short a time. You specify the limits.

Why?
If you haven't had them already you probably will at some point: The tantrumers.
These are people who one day decide they hate you and/or your board, usually just after you've deleted one of their posts or pissed them off some how, and they'll want out. Instead of leaving quietly and gracefully they'll go on a mad rampage to edit/delete/both all their posts.
With 3.5/3.6's ajax, this is made very easy so they can do a fair bit of damage before you're able to stop them.

How does it work?
When a member goes to edit their post, either via the inline editor or the "full" editor, a check is made to see if they actually can. If they can't, they're shown an error message of your choice.
If they can, a check is made to see how many edits and/or deletions they have done recently. If it's "too many too fast" (the limits are specified by you), then they are stopped and an optional PM is sent to a member of your choice (probably to you) saying so, this is so the edits and/or deletions can be investigated.

Features

• You can turn the whole system on/off
• You can manually add users to the list.
• Automatic trigger can be turned on/off. If it's on, you can specify the limits.
• You can specify the message they recieve when they are disallowed.
• You (or any member) can be sent a PM notifying you off a trigger being set off. The PM contains useful links by default.
• You can exclude usergroups and individual users from the check.
• Just one plugin.

Caveats

• Thread Tools Dropdown > Thread Delete is not checked meaning if you allow a usergroup to utilise that feature, they can do it all they like.
• Hard Deletions (physically removed) posts are not checked against. To do this would mean making a new table, and since I assume you trust people you give such power to, I have no desire to add such a check.
• Adds one query every time edit is pressed. Adds between 1 and 4 more to the edit post script, dependant on what happens.
• Private Message counts don't seem to be updating properly on my test board when a PM is sent. I'm using vB's own datamanager so I can only guess there's a bug with that.

To do

• As soon as I figure out how, allow the messages to be phrased.
• As soon as I figure out how, allow the optional PM to be sent to more than one member, e.g. two or more admins.
• Possibly make a way for moderators to control who can and can't edit. Depends if there's enough demand.
• Throw 'Thread Delete' into the check. There isn't a hook in an ideal place but it's possible. Depends if there's enough demand.

Support
Not much.
If there's a bug, I'll try and fix it.
If there's a way to edit or delete posts that I missed, I'll try and plug it.
If it clashes with another mod, I'll look at fixing it if it's an easy fix.
No "it doesn't work" support given. It works just fine on a clean install of 3.6.0 gold.

Screens
There's not really much to screenshot, so I've just taken a sample few.
options.png is the admincp options
Image1.png is the default "you can't" message for those who can't edit/delete.
Image2.png is the same message but in the inline editor (vB feature)
Image3.png is the default PM you get when someone sets off the trigger.