Request

[Fuzion Zero]

Can someone make a hack that gets rid of the "Pease wait before using another magic attack." error.

[Xiphu]

rofl

[Fuzion Zero]

is that all im gonna get as a reply is being laughed at?

[DeadEnd]

Pretty much

[rgs-]

you could probably get rid of it in some way but it would be the same you just wouldent see the message

[Xiphu]

Originally posted by Fuzion Zero@Dec 9 2005, 18:10
Can someone make a hack that gets rid of the "Pease wait before using another magic attack." error.

ur serious? lol i thought u made a joke, no its not possible duh

[Fuzion Zero]

well sry im not knowledgable on hacks. so i asked. you shouldnt make fun of people just because they dont know something. im sure you dont like it when someone makes fun of you cuz you dont know something. i asked because they have the jump hjack so you can jump as high as you want. and you dont get the You Can Not Jump That High error. so i assumed it would work with this

[anhang]

use a hex editor, search for that string, and delete it, or change them all to spacebars.

This won't let you cast magic any faster, just gets the message off.

[Fuzion Zero]

well thats not what i meant. i meant like you can cast magic and stuff faster

[anhang]

very unlikely, the time between spells is checked server side, although maybe you can get just a little faster, and i mean just a little, if you somehow get your CO to connect to the server better, or Ping=0.

[evulhotdog]

yea same anhang not possible

[omega02]

well it really botheres everyone so dont feel bad

[ConquerHaxor]

Originally posted by Fuzion Zero@Dec 9 2005, 22:11
is that all im gonna get as a reply is being laughed at?

ROFLMFAO ROFLMFAO x4 ROFL U R SO ROFLMFAO LOOOOL

[t3hn00bz0r]

First, dont laugh at him. Every time you see "Pease wait before using another magic attack.", it is client side. No packets are sent to the server. That means that it can be modified in the code. You could remove the check for whether you could cast another in the client. I don't know where you would change values, but I'm sure it could be done. Also, does anyone know how the server actually checks time? Almost every packet contains the tick-count of the client. If this is the only thing that is checked, then perhaps it could be spoofed. Something like modifying the tick-count in the packet before it is sent to make the server believe that more time has elapsed client side. However, if the server uses its own clock to determine whether or not you can attack (and it likely does) this will have no effect. On second thought, this might be a way to DOS a CO server.... Well, anyway, the client side can be modified and it might be worth someone changing the time values in the action packets unless someone knows for a fact that the time is handled server side when checking action times.