Messages

46

JavaOp Board / Re: greets/idles

« on: February 16, 2010, 02:41:30 pm »

In regards to #2, this can be accomplished by changing the delay in the simple events processor if I remember correctly.

47

JavaOp Board / Re: CD-Key Exception

« on: February 15, 2010, 06:58:12 pm »

Is the b43 BnetLogin plugin archived somewhere? iago had a link up for b43 but it's dead now

48

JavaOp Board / Re: CD-Key Exception

« on: February 15, 2010, 12:39:00 pm »

That resolves the key length issue but not the product value one

Thanks

49

JavaOp Board / Re: CD-Key Exception

« on: February 14, 2010, 10:57:45 am »

We are waiting on our maintainer for the fix

I was feeling lucky so I imported the javaop2, bnetlogin, channel list, and swing gui packages from the svn and exported them. From there, I imported the CommandLineConfiguration jar from 2.1.2 and refactored some of the util class names (to comply with the new class names in 2.1.3), and jar'ed that too. Next, I ran the cmdlineconfigure jar, set up a bot with only the three previously mentioned plugins, saved my bnetlogin settings, reloaded the bot, and tried to connect. The bot is still a little rough around the edges because it is in development, but the problem from the old BnetLogin plugin persists... Take a look:



Nothing funny with the stack trace except for this:

Code: [Select]

Exception in Metacity for theme "Nodoka": Variable "mini_icon_width" not defined
But I am positive it has nothing to do with the BnetLogin problem.

50

JavaOp Board / Re: CD-Key Exception

« on: February 10, 2010, 01:02:25 pm »

By the way, why are the "server", "port", and "connect automatically" settings not in the BNetLogin plugin? Without the BNetLogin plugin, they are useless.

51

JavaOp Board / Re: CD-Key Exception

« on: February 09, 2010, 09:27:44 pm »

Yes

52

JavaOp Board / Re: CD-Key Exception

« on: February 09, 2010, 06:28:50 pm »

I got lazy and downloaded the latest javaop2 and bnetlogin projects and undid the renaming then exported the bnetlogin jar. I am not getting the 24-character key error anymore but I am getting this:

Code: [Select]

... JUNK ...

[18:18:36.482] INFO: [BNET] Calculated. Sending version check..
[18:18:36.580] Login Exception:
[18:18:36.593] exceptions.LoginException: [BNET] Wrong product value for your CD Key
[18:18:36.595] packets.SidAuthCheck.checkIncoming(SidAuthCheck.java:153)
[18:18:36.595] PluginMain.processedPacket(PluginMain.java:268)
[18:18:36.610] pluginmanagers.PluginRegistration.processedIncomingPacket(PluginRegistration.java:698)
[18:18:36.617] bot.PacketThread.run(PacketThread.java:173)


53

JavaOp Board / Re: CD-Key Exception

« on: February 09, 2010, 02:47:42 am »

I am looking inside BNetLogin.jar and I see Alpha24Decode.class. I guess this plugin wont work!  

54

JavaOp Board / Re: CD-Key Exception

« on: February 09, 2010, 02:37:16 am »

No; both the WAR3 and W3XP keys are 26 characters. 

55

JavaOp Board / CD-Key Exception

« on: February 03, 2010, 10:38:09 pm »

Just updated to 2.1.2 (with the new BNetLogin.jar), tried to connect (W3XP) and got the following error:

Code: [Select]

CRITICAL: [BNET] Caught exception while validating CD-Keys: exceptions.LoginException: CDKey is not 24 characters!

Thanks for the help

56

iago's forum / Re: Wild rice chowder with fresh coconut and mushrooms

« on: December 19, 2009, 12:45:35 pm »

:<

57

Botdev / Re: [JAVA, W3XP, W3GS] Host Counter Decoding

« on: December 17, 2009, 08:30:00 pm »

(byte)Integer.parseInt should be in every way equivalent to Byte.parseByte...

No; parseByte() will throw an NFE if the number is too big, but the cast will simply truncate the high 24 bits. This is probably where the problem lies, since he said parseByte() doesn't work, when that's clearly what he should be using.

I guess I knew that, but I didn't think it was relevant.  Of course, by "in every way", I meant for there to be an implied "in this context...".

I went with the method you posted and everything has been good so far

58

Botdev / Re: [JAVA, W3XP, W3GS] Host Counter Decoding

« on: December 08, 2009, 11:18:55 pm »

That still seems weird... why are you indexing the way you are?  If you want to turn consecutive pairs into bytes, then you should be addressing hostCounter[2*i] and hostCounter[2*i+1].  With your code, if you have digits:

12345678

Your pairs are going to be:

(2,1), (3, 2), (5, 3), (7, 4)

I assume you want:

(1,2), (3,4), (5,6), (7,8)

(the digits within the pairs being reversed is a trivial variation, of course).  You'll get exactly that if you index with 2*i and 2*i+1

It seems that the way you're turning the concatenated digits into a string is a bit off.  The digits aren't going to form something in base-16.  It's going to be in decimal (which is syntactically legal for base-16, but it's semantically decimal).  Also, Byte.parseByte exists.  Why not just use it instead of Integer.parseInt and cast to byte?

I am trying to get (2, 1) (4, 3) (6, 5) (8, 7)

I am using Integer.parseInt because I cannot get it to work using Byte.parseByte as previously shown

59

Botdev / Re: [JAVA, W3XP, W3GS] Host Counter Decoding

« on: December 08, 2009, 08:47:58 pm »

In the code you gave, you lose 3 of the last digits.  You only index 0 - 4, and you repeat the characters in indexes 1-3.

Yeah, I changed it so its a bit like the example you posted:

Code: [Select]

byte[] processedHostCounter = new byte[4];
for(int i = 0; i < 4; i++) {
processedHostCounter[i] = (byte)Integer.parseInt(new String(new byte[] { hostCounter[2 * i + (i == 0 ? 1 : 0)], hostCounter[i] }), 16);
}

and the packet logs look good now

60

Botdev / Re: [JAVA, W3XP, W3GS] Host Counter Decoding

« on: December 07, 2009, 06:10:44 pm »

IIRC this value doesn't even have to be correct..

I thought the same until I started getting W3GS_REJECTJOIN from some hosts. Not having the problem any more