Me 2 :D

yeah, i have to look at the ajaxprocess, so it updates the last post instead of just doing nothing until a reload.

the hack itself works as designed, just Ajax doesn'T ^^

for the ajax thing, it's kinda tricky... the quick-reply have to be interacting with the Edit ajax of the last post if you are the author of that one, so if you post from the quick-reply, it will be connected to the EDIT of the last post you've made instead of posting a new one with the quick-reply ajax...

the problem with that situation, or at least the logic behind a problem, is that if someone else posts when you use the quick-reply, your post will be merged with your last post, even if someone posted between the two... logic applyed tell that it's not a problem, because if you use the quick-reply, you don't know if someone else reply afterward, so you don't actually reply to that last one...

someone is lost here?!

;)

i'll see with what i can come up :)

vBulletin should just have a function built in to autoban doubleposters. That would make everything so much easier for us all! lol

autoban doubleposters ?!... i think you did not quite understood the goal of this hack... but anyway...

A real admin; always blame the software ;)

Definatly keeping an eye on this one :)

I fixed the AJAX process by adding..

at the bottom of the "if ($isdoublepost)" before the "} else".

You need to add a new phrase "redirect_automerged" too.


edit: It works but is printing the message twice.

Working for gold?