Author | Message | Time |
---|---|---|
CrAzY | Can some people define a packet for me?? like if i get it off a sniffer... how could i be able to put it in to place and make it work?? for instance, I'm using WPE Pro and for sending something it just has a few dots like .....Hi.. would be High... for ascii. And FF 0E 07 00 48 69 00. Explain to me how i could make this work in a bot? | May 3, 2003, 3:39 PM |
Kp | [quote author=CrAzY link=board=17;threadid=1222;start=0#msg9048 date=1051976342] Can some people define a packet for me?? like if i get it off a sniffer... how could i be able to put it in to place and make it work?? for instance, I'm using WPE Pro and for sending something it just has a few dots like .....Hi.. would be High... for ascii. And FF 0E 07 00 48 69 00. Explain to me how i could make this work in a bot? [/quote]Most packet sniffing tools default to a period for characters deemed unprintable, as most below 0x20 and above 0x7e are. BNCS packets are composed of a magic byte, a command byte, and a length short. Any data following is packet specific. To make the pasted data work in a bot, you'd send it to the server - and people would see you say "Hi". Any other questions? | May 3, 2003, 5:27 PM |
St0rm.iD | [quote author=CrAzY link=board=17;threadid=1222;start=0#msg9048 date=1051976342] Can some people define a packet for me?? like if i get it off a sniffer... how could i be able to put it in to place and make it work?? for instance, I'm using WPE Pro and for sending something it just has a few dots like .....Hi.. would be High... for ascii. And FF 0E 07 00 48 69 00. Explain to me how i could make this work in a bot? [/quote] AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH | May 3, 2003, 8:13 PM |
iago | [quote author=Kp link=board=17;threadid=1222;start=0#msg9052 date=1051982844] BNCS packets are composed of a magic byte, a command byte, and a length short. [/quote] Magic byte? I don't see anything particularely magical about FF or -1, but maybe I'm just missing the magic stuff :-/ | May 3, 2003, 8:16 PM |
Kp | [quote author=iago link=board=17;threadid=1222;start=0#msg9073 date=1051992990]Magic byte? I don't see anything particularely magical about FF or -1, but maybe I'm just missing the magic stuff :-/[/quote] Magic in the sense that it is a magic number. Magic numbers have some special meaning assigned by the code interpreting them, but nothing is inherently special about them. In this case, it is used to indicate a bnpacket header. See the battle message decomposer for more info on why this is useful. | May 3, 2003, 8:37 PM |
Camel | [quote author=Kp link=board=17;threadid=1222;start=0#msg9076 date=1051994221] [quote author=iago link=board=17;threadid=1222;start=0#msg9073 date=1051992990]Magic byte? I don't see anything particularely magical about FF or -1, but maybe I'm just missing the magic stuff :-/[/quote] Magic in the sense that it is a magic number. Magic numbers have some special meaning assigned by the code interpreting them, but nothing is inherently special about them. In this case, it is used to indicate a bnpacket header. See the battle message decomposer for more info on why this is useful. [/quote] usually "magic" is used to describe the data in the pipe (first packet to/from server; for BNCS that is the 0x01 byte) | May 4, 2003, 1:56 AM |
tA-Kane | [quote author=Camel link=board=17;threadid=1222;start=0#msg9103 date=1052013384]usually "magic" is used to describe the data in the pipe[/quote]AFAIK, all BNCS packets start with 0xFF. As such. any packet that does not start with 0xFF is not a BNCS packet. So, 0xFF is a magic byte. | May 4, 2003, 8:55 PM |