What do you think about a GigaMeleeRumble?

Lets take the best 30 or 50 bots of MeleeRumble and put them into a Giga category. The same thing already exists for 1vs1, why not in melee too? :) What do you think about it?

I am all for it. But we need Rednaxela on board to set rules for it. And more people donating CPU cycles.

The rules are the same as meleerumble, except participants list url.

I can contribute battles until it stabilizes.

but we need a server, which will keep track of ranking and a client config. I presume that server part is where we need Rednaxela help.

Sorry Beaming, you got the wrong guy ;-)

Skilgannon runs the current incarnation of the rumble server. (Of course anyone else could run a separate copy if they wanted to, as the code is out there)

(Speaking of which, the rumble server currently requires a client version that isn't downloadable from sourceforge anymore it seems. Maybe it would be a good time to be updating the allowed rumble client versions?)

Ups. Sorry to point wrongly to you.

Indeed, we need Skilgannon, in particularly to upgrade allowed client version. I think quite a few new comers were looking for the old client, but it is not that trivial to find the old version.

I think the old client requirement, is one of the reason why so few contribute to the rumble.

Skilgannon code is free, but now we have client with built in pointer to the official server. It would be nice to just extend the official client.

beaming where did you find 1.8.2.0

I had it from the original time. I was too lazy to upgrade, and it turn out to be a right thing.

I know that f4 find it somewhere recently via power of google. But if we really desperate I can attach 1.8.2 somewhere to a wiki page.

Yeah, a server accepted other versions OR a place where 1.8.2 can be downloaded is desperately needed. Then I can start contributing again, and that is the first step to start developing again ;-)

http://www.filewatcher.com/m/robocode-1.8.2.0-setup.jar.5267442-0.html

Nice link. We could also ask FNL to put it back in the sourceforge server. It has 1.8.0.0, 1.9.0.0, but doesn't have the 2 rumble versions in between.

All you need to do is create a new config file, similar to meleerumble.txt but with a different filename, and a different config name. Then you need to make another .bat or .sh file similar to meleerumble.bat/sh to use this new config file. The server will automatically create the new rumble when you start submitting battles. I'm guessing you will want to create a new wiki participants page.

As per the LiteRumble page, you can download a pre-configured client here. I also suggest you populate your robots directory with the bots from here.

The reason I'm not enabling newer clients to submit battles is because there was a minor rule change which will adjust scores (bonuses weren't included in the total score in certain versions, which happened to be what was most current when I initially populated the rumble data). If we want to switch to new clients we also need to wipe all of the rumble data and start from scratch.

Wouldn't it be the perfect time to switch clients now? Since the bugs are now gone, and I also saw that some bots like Fractal for example get always disabled. So every new bot will have 100% vs Fractal and the older bots will only have a normal score against it.

Regarding switching to a newer client and wiping the rumble data... I suppose the question is how many of us are willing to contribute to get the scores back to stable state.

For the main rumble I think it'll take in the ballpark of 2156000 battles to get back to the stable point (~2000 battles per participant). At a rate of 1 battle per second it would take 25 days to get back to the stable point. I imagine we could do better than 1 battle per second if a decent number of us chipped in (remember, the bulk of the robots are very simple/fast).

I am also supporting the switch.

I can contribute battles until the rumble stabilizes. 4 to 8 clients.

Also, I have a custom rumble client here which is smarter than the official client.

Extra features: - Detection of server queue overloads and upload throttling. - Separate process/threads for uploads, shared between all local clients. (avoids idle CPU time in uploads. HUGE speed increase in melee) - Shared battle generator/priority battles management. (minimizes repeated battles between clients) - Communication between clients using RMI (TCP/IP), integrating clients spread over a low latency local network. - Generates battles in melee using both bots from priority battles. - Parallel download of bots JARs. - Shared local repository of bots JARs, with automatic copying between clients.

Tested for over an year. Seems very stable.

I can upload the source somewhere if you want.