what to do with about printing to much?

Jump to navigation Jump to search
Revision as of 19 November 2013 at 18:48.
The highlighted comment was created in this revision.

what to do with about printing to much?

I am trying to print quite a lot while I am debugging my bot. But I see

SYSTEM: This robot is printing too much between actions.  Output stopped until next action.

I would like to see the whole output. Is there a way to force robocode to print everything, something analogous to debug mode where all graphics events are plotted.

    Beaming (talk)16:55, 19 November 2013

    One option would be to write to a file instead of printing debug output, particularly if you adjust the per-bot disk quota in the config file.

      Rednaxela (talk)17:26, 19 November 2013

      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
             
             
             

            Not sure if it's useful, but a secondary suggestion is to try debugging graphics. Some info that takes a lot of text is very simple and clear in graphical form.

              Voidious (talk)17:37, 19 November 2013

              I am slowly drifting in the direction of graphics debug. But it certainly harder to do right compared to simple text output.

                Beaming (talk)17:56, 19 November 2013