VGOEmulator.net

Started Character Create discussion, and sorting out what is now known as "PacketType" (0x1, 0x2, 0x9) and Opcode location, and discovering something screwy with the Spawn Packets.

[quote]Session Start: Tue Oct 15 09:51:11 2013
[09:51] <@Xinux_Work> character create
[09:51] <@Xinux_Work> name already taken
[09:51] <@Xinux_Work> 18 :0 0.0.0.0:52331 19 RecvFrom
[09:51] <@Xinux_Work> 0000 00 09 00 07 02 00 86 03 00 00 03 00 00 00 01 00 ................
[09:51] <@Xinux_Work> 0010 00 D4 88 ...
[09:51] <@Xinux_Work> character accepted
[09:51] <@Xinux_Work> 22 :0 0.0.0.0:52331 19 RecvFrom
[09:51] <@Xinux_Work> 0000 00 09 00 08 02 00 86 03 00 00 03 00 00 00 00 00 ................
[09:51] <@Xinux_Work> 0010 00 0A 49 ..I
[11:34] <@Xinux_Work> hopefully this helps explains the 09 packet better
[11:34] <@Xinux_Work> viewtopic.php?f=7&t=45
[13:08] <~john> does my pasting tons of packets do any good? I know you can dig them out of the logs yourself.
[13:09] <@Xinux_Work> yea helps to berak them down
[13:09] <~john> more importantly, do you have any ideas why the "opcode" collector finds isn't correct on some logs? is it that chopping header off thingy?
[13:10] <~john> i'm confused on the spawn packet opcode values.
[13:10] <@Xinux_Work> yea but it need's to be tweaked to handle locations better
[13:12] <@Xinux_Work> plus the packets seem to be different based off the subopcode atleast that is what i'm calling it
[13:12] <@Xinux_Work> did the post help explain soe opcode 9 better?
[13:12] <~john> you mean like eq2's EqCommand::EqOtherOpcode?
[13:13] <~john> yeah, we were pretty confused by SWG's packet docs, though it kinda made sense.
[13:22] <@Xinux_Work> the packet header seem's to be differnt based off the subopcode
[13:23] <~john> interesting.

[14:10] <@Xinux_Work> dod thta post help explain it Scat?
[14:10] <@Xinux_Work> did that
[14:12] <@Scatman> yes i just read it
[14:12] <@Scatman> thanks very much
[14:30] <@Xinux_Work> spawn packets atleast that is what they look like seem to have 2 seperate sequences
[14:36] <@Xinux_Work> and obviously some of the spots where the collector is reading opcodes is length
[14:41] <~john> i think that answered my question about why 4 spawns had 4 different opcodes
[14:41] <@Scatman> heh
[14:41] <~john> and Xinux, do you see any packed/reversed/compressed packet data yet? like those spawns... packed? I couldn't unpack them using what we know about eq2emu.
[14:43] <@Xinux_Work> well they are utilizing zlib to what extent i don't know
[14:45] <~john> well you know how eq2's spawn packet is packed. and, we unpack it, and it grows ginormous. where all the details of the spawn are. tried doing that with Chi Sau Openpalm and couldn't. Has to be more to his spawn info than that little 135 or so bytes.
[15:01] <@Xinux_Work> vanguard stores alot of info client side compared to eq2 tho
[15:03] <@Scatman> xin. so what is up with the 16 bit subopcode, then 32 bit opcode?
[15:03] <@Xinux_Work> yea trying to figure that out
[15:04] <@Xinux_Work> for instance spam inc
[15:04] <@Xinux_Work> –- OP_Unknown_104 --
[15:04] <@Xinux_Work> 10/14/2013 15:10:22
[15:04] <@Xinux_Work> 69.174.203.10 -> 192.168.1.100
[15:04] <@Xinux_Work> 0000: 01 00 68 00 00 00 32 19 5B C6 00 48 60 98 CD BE ..h...2.[..H`...
[15:04] <@Xinux_Work> 0010: 67 63 28 9B 3E 18 60 16 00 00 00 00 00 F8 13 70 gc(.>.`........p
[15:04] <@Xinux_Work> 0020: 18 21 40 68 54 05 00 00 00 76 0D 41 6F 6D 61 20 .!@hT....v.Aoma
[15:04] <@Xinux_Work> 0030: 53 69 78 66 69 73 68 00 57 DF B3 31 94 4D 1F A4 Sixfish.W..1.M..
[15:04] <@Xinux_Work> 0040: 02 90 01 00 00 04 E9 13 00 18 00 00 00 60 63 0D .............`c.
[15:04] <@Xinux_Work> 0050: 00 00 B2 44 0E 00 00 6C 08 00 00 80 F8 40 C2 DE ...D...l.....@..
[15:04] <@Xinux_Work> 0060 6E 00 00 20 FF FF FF FF 8F FF FF FF FF 0F n.. ..........
[15:04] <@Xinux_Work> .
[15:04] <@Xinux_Work> this is what i have so far
[15:04] <@Xinux_Work> 01 00 subopcode
[15:04] <@Xinux_Work> 68 00 00 00 total length
[15:04] <@Xinux_Work> 32 19 Sequence
[15:04] <@Xinux_Work> 5B C6 Sequence 2
[15:06] <@Xinux_Work> it's almost like differnt subopcodes use different structs all together
[15:07] <@Scatman> hmm
[15:11] <@Xinux_Work> here is the first line from a few packets inorder with skipping a few packets that don't look like them
[15:11] <@Xinux_Work> .
[15:11] <@Xinux_Work> 01 00 F9 01 00 00 2F 19 1B C2 01 68 F1 9D CD 7E
[15:11] <@Xinux_Work> 01 00 5D 00 00 00 30 19 DB 03 01 28 55 98 CD BE
[15:11] <@Xinux_Work> 01 00 6C 00 00 00 31 19 4B C6 00 48 64 98 CD AE
[15:11] <@Xinux_Work> 01 00 68 00 00 00 32 19 5B C6 00 48 60 98 CD BE
[15:11] <@Xinux_Work> 01 00 9A 00 00 00 33 19 6B C6 00 E8 91 58 0F 5C
[15:11] <@Xinux_Work> 01 00 55 00 00 00 4F 19 7B 46 00 68 4D 98 CD 1E
[15:16] <@Scatman> so is it 00 00 01 F(
[15:16] <@Scatman> F9
[15:16] <@Scatman> or 00 00 and 01 F9
[15:16] <@Scatman> hmmmm
[15:17] <@Xinux_Work> f9 01 00 00 is the correct length for the packet
[15:17] <@Scatman> ok
[15:17] <@Xinux_Work> 505
[15:17] <@Scatman> so then those were combined?
[15:17] <@Xinux_Work> those are the very first line from 6 different packets
[15:18] <@Xinux_Work> i see sub opcode , packet length, sequence 1 and sequence 2
[15:19] <@Scatman> 2 sequences?
[15:19] <@Xinux_Work> that is what it looks like to me
[15:20] <@Scatman> i do agree, the numbers appear to be incrementing

[16:53] <@Xinux_Work> humm the collector misses stuff like /who results
[19:41] <~john> beginning some docs. Review, critique. Too much info? Too soon to waste time writing? Doxygen will do all this for me?
[19:41] <~john> http://wiki.vgoemulator.net/Docs/LoginServer[/quote]

More Char Create packet info

[quote]Session Start: Sat Oct 19 03:43:43 2013
[12:57] <@Xinux> i was thinking
[12:57] <@Xinux> we still have to tell the client the world server address
[12:57] <@Xinux> which i think we can do via a packet
[12:58] <@Xinux> ready for spam
[12:58] <~john> yes
[12:58] <@Xinux> 16 :0 0.0.0.0:52277 458 RecvFrom
[12:58] <@Xinux> 0000 00 09 00 07 02 00 27 00 00 00 BA 01 00 00 37 00 ......'.......7.
[12:58] <@Xinux> 0010 30 00 30 00 31 00 37 00 38 00 38 00 35 00 35 00 0.0.1.7.8.8.5.5.
[12:58] <@Xinux> 0020 00 00 B0 83 00 0A 90 A2 5B 01 96 0A 00 00 30 D9 ........[.....0.
[12:58] <@Xinux> 0030 40 00 10 F6 00 01 14 00 00 00 08 50 7F 08 C6 85 @..........P....
[12:58] <@Xinux> 0040 00 0A 9C 50 7F 08 FF FF FF FF BA 83 00 0A 9C 46 ...P...........F
[12:58] <@Xinux> 0050 85 00 9C 61 D7 09 09 00 00 00 0A 00 00 00 9C 46 ...a...........F
[12:58] <@Xinux> 0060 85 00 64 BC F7 08 05 00 00 00 06 00 00 00 E8 2E ..d.............
[12:58] <@Xinux> 0070 E4 08 97 5F 15 E3 00 00 6C 00 61 00 68 00 68 00 ..._....l.a.h.h.
[12:58] <@Xinux> 0080 00 00 50 94 4A 09 00 00 00 00 07 00 00 00 44 00 ..P.J.........D.
[12:58] <@Xinux> 0090 57 00 36 00 5A 00 65 00 36 00 69 00 36 00 6E 00 W.6.Z.e.6.i.6.n.
[12:58] <@Xinux> 00A0 38 00 56 00 79 00 62 00 43 00 68 00 63 00 00 00 8.V.y.b.C.h.c...
[12:58] <@Xinux> 00B0 2C 00 58 AD 2C 00 18 AD 2C 00 A8 BC 7E 00 FF FF ,.X.,...,...~...
[12:58] <@Xinux> 00C0 FF FF 67 72 42 00 03 79 AD E3 48 3D 29 06 36 A4 ..grB..y..H=).6.
[12:58] <@Xinux> 00D0 00 00 58 AD 2C 00 78 AE 2C 00 C3 D5 7E 00 FF FF ..X.,.x.,...~...
[12:58] <@Xinux> 00E0 FF FF 8B 77 AD E3 90 AD 2C 00 5C A6 7E 00 FF FF ...w....,.\.~...
[12:58] <@Xinux> 00F0 FF FF F3 E9 40 00 48 AD 2C 00 00 00 32 01 D4 F7 ....@.H.,...2...
[12:58] <@Xinux> 0100 61 7D A8 07 32 01 70 AF 2C 00 68 F7 61 7D 54 00 a}..2.p.,.h.a}T.
[12:58] <@Xinux> 0110 65 00 6C 00 6F 00 6E 00 00 00 86 F6 61 7D 6B 79 e.l.o.n.....a}ky
[12:58] <@Xinux> 0120 AD E3 6B 00 00 00 E4 49 2E 06 6B 00 00 00 4F 4A ..k....I..k...OJ
[12:58] <@Xinux> 0130 2E 06 4F 4A 2E 06 00 00 00 00 DC 40 85 00 02 00 ..OJ.......@....
[12:58] <@Xinux> 0140 00 00 6F 00 00 00 61 00 00 00 EE 49 2E 06 C4 AD ..o...a....I....
[12:58] <@Xinux> 0150 2C 00 80 8C 7E 00 FF FF FF FF 16 4F 40 00 E4 49 ,...~......O@..I
[12:58] <@Xinux> 0160 2E 06 6B 00 00 00 7B 0E ED 9C 7B 0E ED 9C 01 00 ..k...{...{.....
[12:58] <@Xinux> 0170 00 00 FF 30 67 00 0C 00 00 00 7B 0E ED 9C 01 00 ...0g.....{.....
[12:58] <@Xinux> 0180 00 00 48 3F 67 00 7B 0E ED 9C 7B 0E ED 9C 6C 00 ..H?g.{...{...l.
[12:58] <@Xinux> 0190 76 00 73 00 76 00 67 00 6F 00 2D 00 30 00 31 00 v.s.v.g.o.-.0.1.
[12:58] <@Xinux> 01A0 2D 00 30 00 31 00 2E 00 76 00 61 00 6E 00 67 00 -.0.1...v.a.n.g.
[12:58] <@Xinux> 01B0 75 00 61 00 72 00 64 00 73 00 6F 00 68 00 2E 00 u.a.r.d.s.o.h...
[12:58] <@Xinux> 01C0 6E 00 65 00 74 00 00 00 8C 4C n.e.t....L
[12:58] <@Xinux> down at the bottom instead of the address it is pointing to we just send our info
[12:58] <~john> that is exactly the packet I was looking at til 3 this morning. the first time I see the "connectionID" or whatever that number is up top.
[13:00] <@Xinux> also
[13:00] <~john> i was waiting for you to wake up so I could ask you, it looks like Scat is basically sending packet after packet from our test logs... so essentially, that should work right?
[13:01] <@Xinux> yea will have to work out the ack at some point tho
[13:02] <~john> is it always the same ack? cuz I tried throwing a few in there, didn't make a diff without that world packet.
[13:03] <@Xinux> nope the ack is based off the packet number
[13:04] <@Xinux> basically the client/server saying i receieved packet number 200
[13:04] <@Xinux> 201 ect ect
[13:04] <@Xinux> etc
[13:04] <@Xinux> ready for some more spam
[13:04] <~john> you know the whiteboard is working, if you need it lol
[13:05] <@Xinux> atleast that is how the acknowledgment should work lol
[13:05] <@Xinux> i know
[13:05] <@Xinux> inc
[13:05] <@Xinux> 01C0 00 00 00 00 00 00 00 00 00 32 32 01 01 01 01 01 .........22.....
[13:05] <@Xinux> 01D0 01 01 01 01 01 32 32 32 32 32 32 32 32 32 32 32 .....22222222222
[13:05] <@Xinux> 01E0 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 2222222222222222
[13:05] <@Xinux> 01F0 32 32 32 32 32 32 32 32 32 32 32 32 32 32 97 DE 22222222222222..
[13:05] <@Xinux> 33 :0 0.0.0.0:62368 512 RecvFrom
[13:05] <@Xinux> 0000 00 0D 00 0C 32 32 32 32 32 32 32 32 32 32 32 39 ....222222222229
[13:05] <@Xinux> 0010 20 31 36 33 30 32 36 20 35 37 20 31 36 20 31 36 163026 57 16 16
[13:05] <@Xinux> 0020 32 30 30 34 20 35 38 20 31 32 20 31 36 31 30 30 2004 58 12 16100
[13:05] <@Xinux> 0030 39 20 36 30 20 31 32 20 31 36 31 30 30 33 20 37 9 60 12 161003 7
[13:05] <@Xinux> 0040 33 20 39 20 31 36 32 30 31 34 20 37 31 20 31 36 3 9 162014 71 16
[13:05] <@Xinux> 0050 20 31 36 32 30 30 31 20 37 32 20 39 20 31 33 31 162001 72 9 131
[13:05] <@Xinux> 0060 30 31 35 20 36 20 31 36 20 31 33 31 30 31 35 20 015 6 16 131015
[13:05] <@Xinux> 0070 33 32 20 31 32 20 31 33 31 30 31 35 20 32 36 20 32 12 131015 26
[13:05] <@Xinux> 0080 31 34 20 31 33 31 30 31 35 20 33 33 20 31 38 20 14 131015 33 18
[13:05] <@Xinux> 0090 31 33 31 30 31 35 20 33 35 20 31 35 20 31 33 31 131015 35 15 131
[13:05] <@Xinux> 00A0 30 31 35 20 30 20 32 32 20 31 30 30 20 32 38 20 015 0 22 100 28
[13:05] <@Xinux> 00B0 32 38 20 31 31 30 31 33 20 32 39 20 39 20 31 36 28 11013 29 9 16
[13:05] <@Xinux> 00C0 32 30 32 30 20 34 39 20 31 36 20 31 36 32 30 30 2020 49 16 16200
[13:05] <@Xinux> 00D0 30 20 35 30 20 31 32 20 31 36 32 30 30 30 20 35 0 50 12 162000 5
[13:05] <@Xinux> 00E0 32 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 2 -1 -1 -1 -1 -1
[13:05] <@Xinux> 00F0 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:05] <@Xinux> 0100 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:05] <@Xinux> 0110 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 1 -1 -1 -1 -1 -1
[13:05] <@Xinux> 0120 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:05] <@Xinux> 0130 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:05] <@Xinux> 0140 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 1 -1 -1 -1 -1 -1
[13:05] <@Xinux> 0150 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:05] <@Xinux> 0160 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:05] <@Xinux> 0170 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 1 -1 -1 -1 -1 -1
[13:05] <@Xinux> 0180 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:06] <@Xinux> 0190 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:06] <@Xinux> 01A0 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 1 -1 -1 -1 -1 -1
[13:06] <@Xinux> 01B0 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:06] <@Xinux> 01C0 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:06] <@Xinux> 01D0 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 1 -1 -1 -1 -1 -1
[13:06] <@Xinux> 01E0 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:06] <@Xinux> 01F0 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 AA E1 -1 -1 -1 -1 -1..
[13:06] <@Xinux> 34 :0 0.0.0.0:62368 110 RecvFrom
[13:06] <@Xinux> 0000 00 0D 00 0D 20 2D 31 20 2D 31 20 2D 31 20 2D 31 .... -1 -1 -1 -1
[13:06] <@Xinux> 0010 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:06] <@Xinux> 0020 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:06] <@Xinux> 0030 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 1 -1 -1 -1 -1 -1
[13:06] <@Xinux> 0040 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 -1 -1 -1 -1 -1
[13:06] <@Xinux> 0050 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D 31 20 2D -1 -1 -1 -1 -1 -
[13:06] <@Xinux> 0060 31 20 2D 31 20 2D 31 20 2D 31 00 00 2B 37 1 -1 -1 -1..+7
[13:06] <@Xinux> that is your character apperance and equipment visual
[13:06] <~john> oh yeah, i saw that too. Those numbers are kinda literal, eh?
[13:07] <@Xinux> when you create a character you will oly get this roughly
[13:07] <@Xinux> 01C0 00 00 00 00 00 00 00 00 00 32 32 01 01 01 01 01 .........22.....
[13:07] <@Xinux> 01D0 01 01 01 01 01 32 32 32 32 32 32 32 32 32 32 32 .....22222222222
[13:07] <@Xinux> 01E0 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 2222222222222222
[13:07] <@Xinux> 01F0 32 32 32 32 32 32 32 32 32 32 32 32 32 32 97 DE 22222222222222..
[13:07] <@Xinux> 33 :0 0.0.0.0:62368 512 RecvFrom
[13:07] <@Xinux> 0000 00 0D 00 0C 32 32 32 32 32 32 32 32 32 32 32 39 ....222222222229
[13:08] <@Xinux> once you log in and get your starting equipment and log back to character select you will see it is now that big blob
[13:09] <~john> right, i was going to also mention that my new account (Flarney's acct) with no chars, is exactly like Scat's code with NOCHAR defined. Ie., no waiting for Telon.
[13:09] <~john> So I think you are right, formatting that world packet now for a test.
[13:10] <@Xinux> you are using the collect from the other program right not the collector
[13:10] <~john> what other program? no. the collector, with the packet starting with 00 09
[13:11] <@Xinux> you need to use the one not from the collector
[13:11] <~john> looks just like yours above
[13:11] <@Xinux> the packets from that post for example are fine
[13:11] <~john> –- OP_Unknown_39 --
[13:11] <~john> 10/14/2013 15:02:27
[13:11] <~john> 69.174.203.28 -> 192.168.1.100
[13:11] <~john> 0000: 00 09 00 15 02 00 27 00 00 00 BA 01 00 00 37 00 ......'.......7.
[13:11] <@Xinux> thta is not from the collector
[13:12] <@Xinux> since the collector will strip what you need is resending the packets
[13:12] <@Xinux> is = if
[13:12] <~john> strips just the start, right? i just pasted you my packet.
[13:12] <~john> the top line
[13:12] <@Xinux> nope it will also strip lengths from the middle of the packets to i have noticed
[13:12] <~john> omfg
[13:12] <@Xinux> not often but it does
[13:13] <~john> so what magical device do I need when collecting data? since collector isn't it.
[13:13] <@Xinux> the packets from this post are fine viewtopic.php?f=7&t=17
[13:13] <~john> you want me to use your... ok haha
[13:17] <@Xinux> viewtopic.php?f=7&t=17&p=316#p316
[13:18] <~john> is this just coincidence, or one of your acct/char names?
[13:18] <~john> 0070 E4 08 97 5F 15 E3 00 00 6C 00 61 00 68 00 68 00 ..._....l.a.h.h.
[13:18] <~john> you seem to do blahhh a lot lol
[13:18] <@Xinux> that is a character
[13:19] <@Xinux> it's the first character in the screenshot
[13:19] <~john> if it's Blahh, I don't see the B.
[13:19] <@Xinux> yea i know
[13:19] <~john> so, where is it?
[13:19] <@Xinux> beats me
[13:19] <~john> these are the hijinx that scare me
[13:20] <@Xinux> lol
[13:25] <@Xinux> i wonder if that is last character played
[13:25] <@Xinux> or something
[13:25] <@Xinux> going to whiteboard you
[13:25] <~john> i need scat, to tell me how to delay sending the big packet until after the client is done connecting.
[13:25] <~john> ok
[13:26] <~john> right now it's just firing packets rapidly regardless of the Acks I'm sending.
[13:26] <@Xinux> the sever needs to look for a specific packet before firing it off
[13:27] <~john> i'm just shooting them out sequentially, i do not see how to pause to wait for client to do something specific.
[13:27] <~john> but I think we're close.
[13:27] <@Xinux> look at my whiteboard
[13:28] <@Xinux> that one doesn't have the character name so i think it may not be required in that packet
[13:29] <@Xinux> remember how ramsey server sent packet response based off the packet it received
[13:29] <@Xinux> i thought scat was doing the same
[13:30] <~john> well there are a few "opcodes" in the switch
[13:33] <~john> viewtopic.php?p=317#p317
[13:37] <@Xinux> responded
[13:38] <~john> k thx
[13:38] <~john> btw, here's another thing I haven't seen yet. I will go back to look at your "rest of the packets". but this contained my account name.
[13:38] <~john> first viewtopic.php?p=276#p276
[13:40] <@Xinux> that is further down in the packets
[13:40] <@Xinux> packet number 22
[13:40] <~john> hah just saw it. johntest
[13:40] <@Xinux> johntest88
[13:40] <~john> so by that time, you think we're passed talking to world at least once
[13:41] <@Xinux> starting at packet 17
[13:41] <@Xinux> is where it starts talkling to the world
[13:41] <@Xinux> 16 i think is where it get's the address to talk to
[13:42] <@Xinux> see how packet 17 is where it is starting a new connection
[13:42] <~john> the new API
[13:43] <@Xinux> yup
[13:43] <@Xinux> and here is aperfect example of a ack packet
[13:43] <@Xinux> 19 0.0.0.0:52277 :0 6 SendTo
[13:43] <@Xinux> 0000 00 15 00 07 87 DD ......
[13:43] <~john> i'm also not seeing any unknown opcodes received in Login console, so maybe the client isn't responding at all yet.
[13:44] <@Xinux> client is syaing it received packet number 7 which is packet number 16 from the server
[13:44] <~john> yes, if I ever convince you to open the solution, you'll see Scat's SendAck() function
[13:44] <@Xinux> well you were asking me about it lol
[13:44] <~john> no i knew it was there. just didn't see it actually doing anything i expected.

(xinux and I were on Teamspeak at this point)

[14:26] <~john> switch (header.opcode)
[14:27] <~john> case 9:
[14:27] <~john> HandleNinerDinerSixtyNiner(client, message);
[14:30] <@Xinux> 12 0.0.0.0:51527 :0 121 SendTo
[14:30] <@Xinux> 0000 00 03 04 00 15 00 06 6F 00 09 00 01 02 00 6F 00 .......o......o.
[14:30] <@Xinux> 0010 00 00 61 00 00 00 0C 00 1A 00 00 00 43 6C 69 65 ..a.........Clie
[14:30] <@Xinux> 0020 6E 74 4C 6F 67 69 6E 43 6F 6E 6E 65 63 74 69 6F ntLoginConnectio
[14:30] <@Xinux> 0030 6E 73 2E 6C 6F 67 3D 00 00 00 4C 6F 67 69 6E 20 ns.log=...Login
[14:30] <@Xinux> 0040 73 75 63 63 65 73 73 66 75 6C 20 74 6F 20 4C 6F successful to Lo
[14:30] <@Xinux> 0050 67 69 6E 20 53 65 72 76 65 72 3A 20 76 61 6E 67 gin Server: vang
[14:30] <@Xinux> 0060 75 61 72 64 6C 6F 67 69 6E 31 2E 73 6F 65 2E 73 uardlogin1.soe.s
[14:30] <@Xinux> 0070 6F 6E 79 2E 63 6F 6D B7 9A ony.com..
[14:32] <~john> 00 03
[14:32] <@Xinux> 14 0.0.0.0:51527 :0 28 SendTo
[14:32] <@Xinux> 0000 00 09 00 02 02 00 27 00 00 00 0C 00 00 00 54 00 ......'.......T.
[14:32] <@Xinux> 0010 65 00 6C 00 6F 00 6E 00 00 00 87 CB e.l.o.n.....
[14:38] * Xinux (IceChat77@hidden-9A6F8016.lv.lv.cox.net) Quit ( Quit: Say What? )
[16:06] * Xinux (IceChat77@hidden-9A6F8016.lv.lv.cox.net) has joined #VGODev
[16:06] * Xinux (IceChat77@hidden-9A6F8016.lv.lv.cox.net) has left #VGODev
[16:06] * Xinux (IceChat77@hidden-9A6F8016.lv.lv.cox.net) has joined #VGODev
[16:06] * ChanServ sets mode +o Xinux for #VGODev
[16:44] <~john> 16:43:52.399 I Net Sending ack for 0000 (0)
[16:44] <~john> 0000: 00 15 00 00 9E 7F ......
[18:52] <@Xinux> http://prntscr.com/1ygg3j[/quote]