Robocode Editor/Compiler troubles?

Fragment of a discussion from User talk:Sheldor
Jump to navigation Jump to search

I finally figured it out!

I had been copying the .jar files directly into the robots folder, when I should have been using the Import Downloaded Robot tool. I guess the tool tells Robocode to treat bots differently from just .jar files.

Would this be something of interest to fnl or any of the other Robocode developers?

Sheldor (talk)20:05, 27 May 2013

Nice! If you can reproduce it, I'd definitely report it. I can't imagine it's intentional those two operations would take different code paths. I've only ever copied JARs into the robots directory.

Voidious (talk)20:08, 27 May 2013

Oh, I thought this was some other option to add the robot to the repository/cache, but that's actually just the option for extracting the JAR to source files. So you have to extract every JAR for every robot to not get these errors?

Voidious (talk)20:14, 27 May 2013

I think you are confusing the Import downloaded robot tool with the Extract downloaded robot for editing tool.

Anyway, yeah, it seems I'll have to import each robot individually from now on.

Sheldor (talk)20:24, 27 May 2013

Ahh, you're right of course. I thought those were both options, but I launched Robocode and only saw the one and thought it had just been renamed. But "Extract..." is only offered in the Editor.

Voidious (talk)20:26, 27 May 2013

Is it giving you trouble with the compiler when you just copy in the .jars? Because if so, that is very strange...

I've always just copied the .jars, but then I don't use the built in editor, I use jGrasp.

Skilgannon (talk)20:09, 27 May 2013

Actually, I don't think it has anything to do with the compiler. That was just an early hypothesis I had because every time I compiled, it said it was "Updating classpath: [...]\robots," and it got all the errors.

Sheldor (talk)20:21, 27 May 2013