Dev Chat: 10/8/2013 - Wiki
Posted: Tue Oct 08, 2013 2:48 pm
Just some information/links to Wiki pages we need.
[quote][15:14] ->> Channel created on 10/8/2013 2:48:27 PM
[17:21] <~john> btw, packet stuff. I re-found the SWG/SOE protocol pages, and copied some of them to a backup in our wiki (since a few weeks ago this stuff was totally gone... they are unstable...)
[17:21] <~john> http://wiki.vgoemulator.net/Docs/Backup:Packet_Guides
[17:22] <~john> not sure how much it will help us, but Xinux thinks it has some value. SOE Prot and all.
[17:22] <~john> http://wiki.swganh.org/index.php/SWG_Protocol_Wiki
[17:28] <~john> their wiki is creepily detailed. someone had a LOT of spare time
[17:32] <~john> so the one I wanted to show you was the Protocol Breakdown. This is what Kyle walked us through a while back.
[17:32] <@Scatman> this looks like good info
[17:34] <~john> Looks like some of what Xinux already figured out here: viewtopic.php?f=11&t=17
[17:35] <@Scatman> yeah cool
[17:35] <@Scatman> so they really use the same protocol across soe products
[17:35] <@Scatman> or, similar, at least
[17:37] <@Scatman> Thanks to Acid1789 for the abundant information on the SOE Protocol!
[17:37] <@Scatman> heh nice
[17:37] <~john> yeah i saw that too lol
[17:51] <~john> so here's something that doesn't make sense. the SWG dudes say the SOE opcodes are a 16-byte uint.
[17:51] <~john> but the page showing their opcodes, they are clearly int32.
[17:51] <~john> 9CA80F98
[17:51] <~john> that ain't no uint16
[17:52] <@Scatman> where do you see int32?
[17:52] <~john> on their protocol wiki page. still looking over SWG's stuff.
[17:52] <~john> http://wiki.swganh.org/index.php/SWG_Protocol_Wiki
[17:54] <@Scatman> even in xinux's examples the opcodes are int16 tho
[17:54] <~john> yeah. weird. just confused by their text. maybe it's outdated.
[17:54] <~john> or maybe i have no idea what they mean by opcode lol
[17:54] <@Scatman> yeah could be
[17:56] <~john> anyway, if you don't need anything from this guy, I gotta scoot.
[17:56] <@Scatman> now i can study this no after datastructs
[17:56] <@Scatman> this is great[/quote]
[quote][15:14] ->> Channel created on 10/8/2013 2:48:27 PM
[17:21] <~john> btw, packet stuff. I re-found the SWG/SOE protocol pages, and copied some of them to a backup in our wiki (since a few weeks ago this stuff was totally gone... they are unstable...)
[17:21] <~john> http://wiki.vgoemulator.net/Docs/Backup:Packet_Guides
[17:22] <~john> not sure how much it will help us, but Xinux thinks it has some value. SOE Prot and all.
[17:22] <~john> http://wiki.swganh.org/index.php/SWG_Protocol_Wiki
[17:28] <~john> their wiki is creepily detailed. someone had a LOT of spare time
[17:32] <~john> so the one I wanted to show you was the Protocol Breakdown. This is what Kyle walked us through a while back.
[17:32] <@Scatman> this looks like good info
[17:34] <~john> Looks like some of what Xinux already figured out here: viewtopic.php?f=11&t=17
[17:35] <@Scatman> yeah cool
[17:35] <@Scatman> so they really use the same protocol across soe products
[17:35] <@Scatman> or, similar, at least
[17:37] <@Scatman> Thanks to Acid1789 for the abundant information on the SOE Protocol!
[17:37] <@Scatman> heh nice
[17:37] <~john> yeah i saw that too lol
[17:51] <~john> so here's something that doesn't make sense. the SWG dudes say the SOE opcodes are a 16-byte uint.
[17:51] <~john> but the page showing their opcodes, they are clearly int32.
[17:51] <~john> 9CA80F98
[17:51] <~john> that ain't no uint16
[17:52] <@Scatman> where do you see int32?
[17:52] <~john> on their protocol wiki page. still looking over SWG's stuff.
[17:52] <~john> http://wiki.swganh.org/index.php/SWG_Protocol_Wiki
[17:54] <@Scatman> even in xinux's examples the opcodes are int16 tho
[17:54] <~john> yeah. weird. just confused by their text. maybe it's outdated.
[17:54] <~john> or maybe i have no idea what they mean by opcode lol
[17:54] <@Scatman> yeah could be
[17:56] <~john> anyway, if you don't need anything from this guy, I gotta scoot.
[17:56] <@Scatman> now i can study this no after datastructs
[17:56] <@Scatman> this is great[/quote]