JavaOp 2.1.1 released! (Formerly beta 44)

[Joe]

My goal with this final release is to polish the bot inside and out, so that it'll be able to be used hassle-free until JavaOp3 comes out.

javaop2_pub - This package has been removed from the source tree.
javaop2 - This package is now the build target for all plugins. I don't know why there were two in the first place, but it's fixed now. javaop2 - util.Statstring - New class for statstring parsing. Can currently parse client IDs, as well as wins for StarCraft and WarCraft II, and clan names for WarCraft III.
javaop2 - constants.PacketConstants - Gave names to a ton of unknown packets. Still need to re-do []packetConstants.

BNetLogin - versioning.BNLSWrapper - Updated the list of BNLS servers. Current list: alendar.no-ip.org, jbls.org, jbls.idiat.com, distant.no-ip.org, ribose.no-ip.org, phix.no-ip.org
BNetLogin - versioning.BNLSWrapper - Rewrote getVersionByte and getVersionCheck to be much more readable, and use a more solid method of dealing with broken servers. Now, the server will be removed from the list and the function will recurse. Also, this gives a bit less error output.
BNetLogin - cdkey.War3KeyDecode - Verified that new 26-character keys work correctly with Diablo II and WarCraft II. It's been like this from the start, but I finally verified it
BNetLogin - cdkey.CDKeyDecode - This class is now used only to construct the other decoders. Numeric decoding moved to its own class.
BNetLogin - cdkey.NumericKeyDecode - New class based off of CDKeyDecode. BNetLogin - The Warden packet won't show up as unhandled anymore:
[22:28:21.958] ERROR: [BNET] Ignoring Warden challenge -- Disconnection in two minutes.

SwingGui - gui.ChannelList - A user's clan is now listed if they're on WC3.


Also, the login output has changed. Several of the redundant lines have been removed, and [BNLS] and [BNET] tags have been added, Stealthbot style:
[17:43:34.489] INFO: [BNLS] Server set to alendar.no-ip.org
[17:43:34.551] INFO: [BNET] Looking up useast.battle.net..
[17:43:35.401] INFO: [BNET] Got 1 addresses. Using: useast.battle.net/63.240.202.121
[17:43:35.405] INFO: [BNET] Connecting..
[17:43:36.613] INFO: [BNET] Connected to /63.240.202.121:6112
[17:43:36.626] INFO: [BNLS] Server set to alendar.no-ip.org
[17:43:36.653] INFO: [BNET] Switched to binary chat protocol.
[17:43:40.009] INFO: [BNET] Authorization info sent, waiting for reply.
[17:43:44.565] INFO: [BNET] CDKey and Version check sent.
[17:43:46.053] INFO: [BNET] CDKey and Version check successful.  Attempting to log in.
[17:43:47.687] INFO: [BNET] Logon successful! Entering chat.


DOWNLOADS:
JavaOp2.zip is all the JAR files, which as always include the source code. (1.2MB)
JavaOp2 Source.zip is the source files, directly swiped from my Eclipse workspace after a clean operation. (1.0MB)

[Camel]

You should prepend com.javaop. to all your package names, and use a manifest to instruct the bot on how to load plugins. Currently, you're exploiting an implementation quirk of JVMs where ClassLoaders have scope. If you were to run JavaOp in a (theoretical) JVM that kept all classes in a globally visible scope, your plugins would clash for sharing the same class names.

[Joe]

I'm not sure, but I think that'd require a ground-up re-write for the most part. I feel that beta 44 will be the final beta of JavaOp2, and I'm trying to clean up all the code to the point that it's copypasta-ready for JavaOp3.

[Chavo]

A ground-up rewrite to do some refactoring? lol...

[iago]

A ground-up rewrite to do some refactoring? lol...

I believe he's suggesting a change to the core way the bot works -- it would break compatibility with every plugin. It'd be a *ton* of re-writing.

Maybe not ground-up, but pretty close!

[Joe]

A ground-up rewrite to do some refactoring? lol...

I believe he's suggesting a change to the core way the bot works -- it would break compatibility with every plugin. It'd be a *ton* of re-writing.

Maybe not ground-up, but pretty close!

Ground up, minus the few servings of copypasta I mentioned earlier.

[Explicit]

You should include the date for any changes/updates made to the bot when you edit your post. You know, to keep changes clear. Or alternatively, just paste the changelog if you're keeping one.

Keep it up, Joe.

[Newby]

JavaOp3? lol.

How about COp? Let's write a bot in C! I even have a cool slogan:

COp -- Policing your channel since 2009

[Joe]

I thought of Cop and realized it'd be a really lame name. That, and I don't know enough C. That's an awesome slogan though, I'll keep it in mind.

[rabbit]

JavaOp3? lol.

How about COp? Let's write a bot in C! I even have a cool slogan:

COp -- Policing your channel since 2009

I'd do it.

[Newby]

I'd be down to give it a shot. C or C++.

[Camel]

A ground-up rewrite to do some refactoring? lol...

I believe he's suggesting a change to the core way the bot works -- it would break compatibility with every plugin. It'd be a *ton* of re-writing.

Maybe not ground-up, but pretty close!

The refactoring is trivial (at least it is with Eclipse), and modifying the plugin loader to get the plugin's main class name from a manifest would take fewer than 5 lines of code. Nothing would need to be re-written.

[tazo]

Where is the download link for this? 

[Newby]

Where is the download link for this? 

Joe attached them to the post, which means only x86 members at the moment can download them.

Hopefully someone uploads them somewhere.

[iago]

Or fixes the permissions on the forum..