Thread: [Newbie] Help with add-on!

So I'm not really the one organizing and coding this add-on for gaming servers in a clan I'm in. (cod2, cod4, etc.)

The one coding the Mac version of the add-on is doing it in Java.
I'm trying to test out this, close to final, version of the add-on, but I get an error that is yet to be resolved. I need fast help or any help would be appreciated!

Mac OS X 10.7.3 Java SE 6

Error:

Error : java.io.FileNotFoundException: null/.jffaddon/debug/debug.log (No such file or directory)

I Hit OK* and Window reappears x3

Then: The java JAR file "Addon_Client.jar" could not be launched window.

ScreenShot: http://uploads.justforfun-gaming.com...52_24%20PM.png

Please help me .

doing it in Java

Can't be. If they were really doing it in Java, you wouldn't get that error message. To get a File path that starts with "null/", they must have concatenated String literals and that's just not Java. Suggest to the author they employ the constructors available in the java.io.File class for making File paths.

Alternatively - I don't know Mac OS X, but have heard it might be based on BSD so it should have Unix like file paths? Try creating a directory named "null" in the applications current working directory (that might be your home), with a sub-directory .jffaddon, then one called debug. Since the code is lamely attempting to open that string literal path, it might even just work!

The app name is Addon_client.jar Opens with jar launcher. I also know that the way it is set up is that the updater to the master server is the same way as how say minecraft uses their update system.

Sorry when I say "Not Java" I'm not being very helpful. It has of course been compiled with the Java compiler and is running with the Java RE. It's just crap code - concatenating Strings to make file paths is bad Java. Concatenating Strings to make file paths is a very common thing for bad Java programmers to do.

My suggestion - to create that path starting with a directory called "null" in the application's working directory - would probably get you past that error message. If they've created a file path that way, they may well have included more non-portable code that will be as hard or harder for you to kludge your way around. It's not your fault it doesn't work - it's badly written. What you really need to do is to complain to the author.

I see mention of a 'MAC[sic] version" here:
Addon Client MAC v1.09
- is that the file you downloaded?