Thread history

Fragment of a discussion from User talk:Beaming
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

Do we have a code sniplet anywhere for writing into a file?

Beaming (talk)17:57, 19 November 2013

Kind of a weird link, but PEZ recently posted all his bots to a GitHub repo so that's fresh in my mind. See the robot.getDataFile() stuff: [1]

Voidious (talk)18:06, 19 November 2013

Thanks, I will look at it.

Is there a way to see if bot run with GUI or through a rumble client? So one can disable all of the debugs during rumbling matches to save on CPU and quotas.

One more questions, why rumble client needs a display under x11 environment? It does not use gui so it should run just fine.

Beaming (talk)20:48, 19 November 2013

I don't think Robocode exposes anything about the environment (app vs control API, graphics or not). You can tell if graphical debugging is enabled, though, because onPaint() will be called. You could use that as your debug switch. I mainly use graphical debugging and log severe stuff to file.

As for X11, I don't know, I would guess it's due to using some java.awt code internally or something. I have run RoboRumble over a terminal quite a bit, but maybe my terminal has the X stuff setup. (Mac OS X Terminal connecting to Ubuntu.)

Voidious (talk)21:13, 19 November 2013

Unfortunately, RoboRunner seems to suffer from the same issue.

Set DISPLAY variable to something crazy and run RoboRunner you will see it crush as well.

Beaming (talk)06:13, 20 November 2013

I think it's Robocode itself causing the issue, not RoboRumble or RoboRunner.

Voidious (talk)19:42, 20 November 2013
 

Try adding the "-Djava.awt.headless=true" parameter to how you invoke Java. I believe that does the trick. I seem to recall once trying this in the past.

Rednaxela (talk)22:01, 20 November 2013