First I would like to apologize to WebmasterM for accidently using his account to post something... How this happened I have no idea. So sorry :ops:
Quote:
actually i was careful with what i said.
basically i stated what i knew, and asked if anyone wanted to add anything that they knew, in the hope that eventually a solution could be reached. then, it would obviously become a valuable thread in this forum because it has not been posted elsewhere.
hence, the topmost purpose for this thread is to give information about the exploit that is surrounding the reborn guard.
if you're not going to help contribute, please don't waste everyone's time and bandwidth with stupid images composed in paint.
This post has been edited by neoy2k on Yesterday 18:58
|
@blue
If you were careful of what you said, we would not have this problem.
@red
Your description of the bug sounds more like an identifier
@purple
Okay when you ask something, it implies that you want an answer (or a soulution if it is stated in a problem form), that is unless it is rhetorical, in which case it is a pointless post.
@orange
If the "topmost purpose for this thread is to give information about the exploit" then why does your post only contain 2 pieces of information on the topic, and end in a question?
@yellow
I have contributed to this forum, and I resent that statement.
@gray
I am sorry if I used up too much of anyone's time or bandwith with a 64 KB image.
@green
Paint is great for dealing with this type of situation. I wouldn't want to actually boot up Fireworks MX for this stuff. Also, notice that in all caps under the red announcement sign it says "DO NOT POST QUESTIONS IN THIS FORUM!!!"? I just figured a visual would help you a bit seeing as how you missed that.
@KP
yay Kitsune Paws is back!! Hope you got your issues worked out!
@topic
Well I have seen this happen in BI. Maybe we could edit the pet.dat file and make it so it doesn't move out of the way. The mob thing, it could be that a Summoned guard there on a disconnect.
P.S. When did my status get changed to "still a nubf00"?