Thread history

From User talk:Beaming
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
15:50, 31 July 2018 Beaming (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
15:29, 31 July 2018 Xor (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
16:51, 28 July 2018 Beaming (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
15:37, 27 July 2018 Xor (talk | contribs) Comment text edited (got it)
15:36, 27 July 2018 Xor (talk | contribs) Comment text edited  
15:35, 27 July 2018 Xor (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
01:27, 18 October 2017 Beaming (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
01:16, 18 October 2017 GrubbmGait (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
00:59, 18 October 2017 Beaming (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
23:14, 17 October 2017 MultiplyByZer0 (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
23:12, 17 October 2017 Rsalesc (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
23:01, 17 October 2017 Cb (talk | contribs) New reply created (Reply to Bots starting position randomizing is not working)
22:33, 17 October 2017 Beaming (talk | contribs) New thread created  

Bots starting position randomizing is not working

Guys,

Can you double check it for me. I just notice that 1on1 rounds seem to have the same bot starting location. I.e. in 35 rounds battle, every round start (at least bot positions) are identical.

I see it in robocode-1.9.2.5

Beaming (talk)‎22:33, 17 October 2017

I don't know about RoboRumble but in RoboCode I see the randomizing works.

Cb (talk)‎23:01, 17 October 2017
 

Random here.

Rsalesc (talk)‎23:12, 17 October 2017
 

I see randomized start positions working in Robocode. Watch some rounds between Tracker and SittingDuck; you will see it.

MultiplyByZer0 (talk)‎23:14, 17 October 2017

I defenetly have one instance of GUI, where every round start seems to be the same. The other seems to be fine.

Looks like robocode's random number generator get stuck.

Beaming (talk)‎00:59, 18 October 2017
 

All random here also. Stupid question (but just to be safe): No fixed position set in the properties ?

GrubbmGait (talk)‎01:16, 18 October 2017

Bingo! It apparently was set somehow for one of the bots.

But I cannot even find how to setup it in the GUI. I spotted it in the config after your hint.

Looks like I was right, robocode opens some secret to people with more than 10 years of experience :)

Beaming (talk)‎01:27, 18 October 2017

I've looked into the newest robocode source code, but couldn't find where the robot start position settings are — except for the tests used by robocode itself. Could you still remember what config it was to fix start positions?


Edit: got it, it just hides behind some direct access instead of accessors.

the config is "robocode.battle.initialPositions".

Thanks for mentioning that feature anyway!

Xor (talk)‎15:35, 27 July 2018

It is good that you find it. I already forgot what it was. Strange thing I did not remember to set it up, so some bug triggered it back then.

Beaming (talk)‎16:51, 28 July 2018

However, it doesn't work when set in robocode.properties.

And from source code I know that this config is valid only in battle files.

And with a bug of robocode, once you open intro.battle, then the first bot's initial position will be fixed as long as another battle file is not opened. Neither "New Battle" nor "Restart" works.

So did yours appear in robocode.properties?

Xor (talk)‎15:29, 31 July 2018
Show 1 reply
 
 
 
 
 
Retrieved from "http://robowiki.net/wiki/Thread:User_talk:Beaming/Bots_starting_position_randomizing_is_not_working#Bots_starting_position__randomizing_is_not_working_6331"