BATTLESPERBOT setting

Fragment of a discussion from Talk:RoboRumble/Contributing to RoboRumble
← Thread:Talk:RoboRumble/Contributing to RoboRumble/BATTLESPERBOT setting/reply

Jump to navigation Jump to search

Surely you can set this variable as large as possible, since most bots already had way more battles than this value. And there could be a pull request to robocode to change the default settings.

You do not have permission to edit this page, for the following reasons:

The action you have requested is limited to users in the group: Users.
You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

That's what I figured but I didn't want to be the person who screwed up the results and forced them to be recalculated from scratch so figured I'd check with those who know better than I do. Looks to me like a default of 100k wouldn't be unreasonable for melee. Not sure about duels, maybe 30k?

Return to Thread:Talk:RoboRumble/Contributing to RoboRumble/BATTLESPERBOT setting/reply (2).

I think the best is to dynamically adjsut the value based on current battles per bot, e.g. 80% * pct1 of battles per bot. In the meanwhile, you can safely set this value lower than the second lowest battle counts.

If I recall correctly, even if all bots have more than BATTLESPERBOT battles, bots with less battles get some priority. An other priority is 'old' battles (where f.e. the last battle is from 2020) even if those bots have a lot of battles. Also if I recall correctly, in melee there is some protection to prevent battles between only 'new' bots, I think only 1 new bot per battle and the rest quite randomly. Setting the BATTLESPERBOT higher does not influence this. Ofcourse bots with incomplete battles always get the highest priority.

GrubbmGait (talk)‎

Retrieved from "http://robowiki.net/wiki/Thread:Talk:RoboRumble/Contributing_to_RoboRumble/BATTLESPERBOT_setting/reply#BATTLESPERBOT_setting_7010"