User talk:CrazyBassoonist
Redirect page
- [View source↑]
- [History↑]
You cannot post new threads to this discussion page because it has been protected from new threads, or you do not currently have permission to edit.
Contents
Thread title | Replies | Last modified |
---|---|---|
Welcome back :) | 2 | 21:47, 5 May 2012 |
micro/nano melee rumble | 1 | 03:58, 28 April 2012 |
supersample bots | 3 | 01:50, 6 September 2011 |
Man, this is great to see that you have changed Capulet. Hopefully this means you got a little interest in robocode again. Sorry my whole system crashed today but i will bring my contribution server asap back online and so we can see how it works :).
take care
Thanks! It was only a minor change(I switched one variable from .72 to .5), but I do plan to keep trying to make improvements as you've been hard at work beating me; congratulations by the way! It takes most people much longer to take one of the thrones. I'm downloading the roborumble pack right now (I had an older version) and once that's finished I'll run some battles to try to relieve some of the strain.
Yes it was indeed a lot of work to make wallaby running and i hope you enjoy the challenge. Thanks for appreciate my work. I'm well excited to see a new version of capulet and i'm sure you will come with something that blow my mind :). I have some idears how to improve wallaby, and there are some things i don't like. Mostly the engagement of stronger (more energy left) robots and wall hitting. Right now i have hugh problems with my computer so it will take a while to fix this. But after this i'm back at the game. Till then take care.
Man, you give me hard times :). I finally thought i have something new to conquer Capulet but it turned out you allready had the same idear. My last version (wallaby 1.9) did very well and i was quite excited about this, but then showed Mercutio as major threat up in the ranking table. And it turned out you have the same movement concept. The main idear was to combine the previous antigrav and the oscillation to something compact and still hold the close combat idear. I was hopeing to give you something exciting but well, you know it already.
One question would be how to decide if the bot is good enought for the competition. I test my new bots against 9 other bots from every part of the rumble (i mean 9x5 not only 9), with a couple of 1000 runs. After this i check some special cases (closecombat - smaller battlefield, and endgame- just the best 4 of each field part). If i win with a certain percentage i put it on the rumble. But unfortunatly is this kind of check not working very well. I'm always surprised how bad/good it worked out. So the question is, what would be a good benchmark check to deside if the bot is worth the rumble. I hope i can interest you in a little discussion.
btw. sorry for my bad english take care
I've never found a sure-fire way to know how a melee bot will do before it is released; I think there's a certain degree of randomness to melee scores as each individual battle has its own unique combination of bots that affects score outcome differently. That said, in order to determine if my robots are fit for the rumble I usually do basically what you do(long battles against 9 other bots that have been randomly selected from the different melee fields) except that instead of worrying about percentages I just check and see how it does in comparison to the bots I want it to beat. For example, I released Capulet when I noticed it was consistently beating other good micro's such as HawkOnFire and Shiz when they were paired together. I think being able to consistently bots that are good is an indicator that a bot will be good, as PL score almost always tends to exactly follow APS scores in melee fields.--CrazyBassoonist 02:58, 28 April 2012 (UTC)
I added the supersample bots in the rumble. Feel free to move the packages to somewhere else. I couldn't upload them to the Robocode Repository.
I am not able to run battles with SuperCrazy, keeps telling me it can't find that bot. It is present however, but with capitals in the packagename.
Delete the jar you have of it. In all his wisdom MN added a new version with exactly the same version string, and the RR is not case sensitive but the files are. So meaning you need to either lowercase the jar name or delete it.
Removed the new version...