about mod_hane

Some info on how it's patched:

mod_Hane use to turn regular wings into Waxen Wings (which allow you to specify where to warp).

They fixed it by A. Checking what type of wing you're trying to use on the server and
B. Checking if the warp location is one the wing allows you to go to.

~ ,~ didn't hane just alter the variable of where the normal wing was set to...?

like, if the wing was set to dunby (@1,135,233 (<-- random numbers)) it'd just change those numbers on the wing the moment you used it

well, patched it patched. thats just how i understood hane. seeing as you could type in the exact coördinates. probably something like <map number>,<X-axis>,<Y-axis>

Quote:

Originally Posted by cloudkiller2006 ~ ,~ didn't hane just alter the variable of where the normal wing was set to...? like, if the wing was set to dunby (@1,135,233 (<-- random numbers)) it'd just change those numbers on the wing the moment you used it well, patched it patched. thats just how i understood hane. seeing as you could type in the exact coördinates. probably something like <map number>,<X-axis>,<Y-axis>

Nah because hane teleports to @pos and portals which are waxen wings, normal wings go to last area waxen wings go anywhere lol.

You can see that when you use a waxen wing the packet is a portal one lol

Quote:

Originally Posted by Rican~ Nah because hane teleports to @pos and portals which are waxen wings, normal wings go to last area waxen wings go anywhere lol. You can see that when you use a waxen wing the packet is a portal one lol

If you look at the packet for both, it's the exact same opcode.
Just with waxen wings there's two more bits of data, a T_STR with the portal name and an int which I have no clue what it does.

The 01 T_BYTE determined which type of wing it was.