Quote:
Originally Posted by Syloxx
[25/02/15 20:25:23] Khaled (xExorcist): fucking nub
[25/02/15 20:25:24] Khaled (xExorcist): I said
[25/02/15 20:25:29] Khaled (xExorcist): W.O UR EMU
[25/02/15 20:25:32] Khaled (xExorcist): FECKING EMU
lol emu? it can be done by a simple packet filter
Query: SELECT ItemID FROM _Inventory WHERE Slot = 8 AND CharID = {CharID}
IF ItemID <> 0
dont send packet to gameserver / send a notice packet to client
gg
or a way better method to fix that... "don't add fellow pets"
|
You clearly didn't read what i wrote did you?
What i wrote doesn't allow you RIDE the pet, however you can still use it for attacking etc.
The bug gets fixed, however, you can completely use the fellow pet elsewise.
In fact, since I've completed IntelliTracing today, I can just disable tracing via fellow pets. So you can still ride the fellow and do all kinda shit. Just not abuse.
Do that in the filter please, and before you say something. Go sniff some packets. You will notice that you only get a objectid. Then you'll notice that you have to parse the singlespawn for the pet, or groupspawn. Depends if it's pre-spawned. Then you'll notice that you have to get ur own id as well. So you parse either 3020 or 3013. I recommend the former for that. Then you'll notice that you have to check if the char is riding the fellow pet. Then you'll have to disable tracing once that is done.
So yeah, don't come up with shit fixes that disable part of the game. Instead fix things properly, that's the level of professionalism that should be achieved.
PS: How is your filter in python going? Already hit the limits of performance or still coding it?