This hack is kinda designed to replace the editing time limit.

The time limit check is done before this plugin is reached, so it'd have to be flipped over so that everyone can edit any aged post but you can input usergroups that are limited by time.

It's a possibility but not something I'm planning at the moment. Perhaps in future.

I missed this one until I saw it in your sig. Very nice, thanks for the contribution!

Very nice mod. Is it compatible with vB 3.5.x or is there a version for this vBulletin-Version?

I haven't tested it with 3.5 though for some reason I'm thinking it's not compatible. I'm not sure why, must have been a thought that came to me when I was coding it.

I did do a 3.5 version. It's much more complicated and requires file edits but does practically the same thing: https://vborg.vbsupport.ru/showthread.php?t=110918

Would it be possible to add a per forum on / off feature?

Nice. Thanks.

Yes, it will work for 3.5.x if you delete in the product the line:

executionorder="2"

Thanks, good stuff!

Edit:

Aaarggll..., on issue left:

Invalid SQL:

SELECT dateline
FROM vb3_deletionlog
WHERE userid = 4549
UNION ALL
SELECT dateline
FROM vb3_editlog
WHERE userid = 4549
ORDER BY dateline DESC
LIMIT 4, 1;

MySQL-Fehler : Unknown column 'dateline' in 'field list'
Fehler-Nr. : 1054
Datum : Monday, November 27th 2006 @ 11:06:05 AM

Any idea bairy?

Yes. 3.5's deletionlog doesn't have a dateline field.
I don't think the deletion date is recorded at all in 3.5.

a) You can't use this 3.6 product.
b) You can edit the code so it doesn't left join the deletionlog table, though that means that the "how many deletions have they done in the last x mins" won't work (meaning people can delete all they want), and makes the "how many edits and deletions have they done in the last x mins" more unreliable. However it will still be acceptable if people only edit, e.g. if you don't allow people to delete their posts.
Even with that fixed there may be other problems on 3.5

Thanks.

doesn't work for 3.6.8?...