Author Topic: JavaOP Logon Sequence Modification  (Read 4817 times)

0 Members and 2 Guests are viewing this topic.

Offline Lance

  • Full Member
  • ***
  • Posts: 129
    • View Profile
JavaOP Logon Sequence Modification
« on: July 12, 2008, 02:19:43 pm »
I have JavaOP2 loaded into eclipse.
I would like to change the packets that are sent to the server when a successful connection is made (I don't want 0x01) (Experimenting with some stuff -- and this will not be connecting to a BATTLE.NET server) and change how JavaOP2 responds to what the server sends. But I'm interested more in the sending part :P.

In what package can I find the classes to change this stuff? Thanks
« Last Edit: July 16, 2008, 09:26:35 pm by SarCaSTiC »
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Offline Joe

  • B&
  • Moderator
  • Hero Member
  • *****
  • Posts: 10319
  • In Soviet Russia, text read you!
    • View Profile
    • Github
Re: JavaOP Logon Sequence Modification
« Reply #1 on: July 12, 2008, 03:28:38 pm »
BNetLogin
I'd personally do as Joe suggests

You might be right about that, Joe.


Offline Lance

  • Full Member
  • ***
  • Posts: 129
    • View Profile
Re: JavaOP Logon Sequence Modification
« Reply #2 on: July 12, 2008, 04:42:10 pm »
Found it. Thanks  ;D
« Last Edit: July 12, 2008, 05:09:36 pm by SarCaSTiC »
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Offline Lance

  • Full Member
  • ***
  • Posts: 129
    • View Profile
Re: JavaOP Logon Sequence Modification (Update, please check!)
« Reply #3 on: July 15, 2008, 08:36:53 pm »
How do I register the packets that I am going to receive? If the packet starts with 0x1 do I
Code: [Select]
register.registerIncomingPacketPlugin(this, 1, null);
?

Because it's not working ;;
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Offline Lance

  • Full Member
  • ***
  • Posts: 129
    • View Profile
Re: JavaOP Logon Sequence Modification (Update, please check!)
« Reply #4 on: July 16, 2008, 12:05:22 pm »
Ah.  Somewhere in BNetPacket class or Buffer class, the buffer has FF added to it and something else before the actual data is placed in the buffer according to some comments in the code but I cannot find where it's done so I can remove the block of code. Anyone know where it is?
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Offline Lance

  • Full Member
  • ***
  • Posts: 129
    • View Profile
Re: JavaOP Logon Sequence Modification (Update, please check!)
« Reply #5 on: July 16, 2008, 07:21:51 pm »
help ;;
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Offline Lance

  • Full Member
  • ***
  • Posts: 129
    • View Profile
Re: JavaOP Logon Sequence Modification (Update, please check!)
« Reply #6 on: July 16, 2008, 09:26:09 pm »
Ron saved the day  ;D
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Offline Joe

  • B&
  • Moderator
  • Hero Member
  • *****
  • Posts: 10319
  • In Soviet Russia, text read you!
    • View Profile
    • Github
Re: JavaOP Logon Sequence Modification
« Reply #7 on: July 22, 2008, 07:27:31 am »
For the record, that's the difference between a Buffer and a BNetBuffer. BNetBuffer does the 0xFF, packet ID, and packet length, whereas Buffer is raw.

I think I wrote a BnlsBuffer too, with the same concept.
I'd personally do as Joe suggests

You might be right about that, Joe.