Talk:RoboRumble/Participants/Teams

Anyone have problem with ShadowTeam? My client always tole me that it can't find abc.Shadow 3.83. I now put ShadowTeam on my exclude list. » Nat | Talk » 12:56, 2 May 2009 (UTC)

I'm having lots of problems getting teamRumble to run many of the bots, is anyone else having frequent trouble with armyOfShiz,ShadowTeam and several others? Also, my team WonderlandTeam isn't appearing on the darkanuck server, anyone know what's wrong with team battles? --Tripphippy 19:27, 5 August 2009 (UTC)

I haven't run team rumble recently, but all of those used to work and they haven't changed version since, so if it's an issue, it's an issue with the version of Robocode I'd think. What kind of messages is roborumble giving? As far as WonderlandTeam not appearing, has your client ran it? Your client is the only one that's run team rumble so far this month. --Rednaxela 23:31, 5 August 2009 (UTC)

Also, your download link was wrong it appears, so other clients wouldn't have been able to run it anyway. --Rednaxela 23:55, 5 August 2009 (UTC)

Even after fixing the download link, WonderlandTeam still does not run, complaining of "Not able to read properties". Did you use Robocode to package that jar? If not, I suggest you do. --Rednaxela 23:59, 5 August 2009 (UTC)

I did package it using robocode. I have no idea why it says unable to read properties. I get several errors when I run teamRumble, I will save a log when I can get to my client later. --Tripphippy 14:05, 6 August 2009 (UTC)

I know the 1.7.1.x versions had a bug related to team jars not being unpacked properly. It's apparently fixed now, but I'm not sure when it was introduced. I've never had much success running the team rumble myself though so I can't offer much help. --Darkcanuck 14:35, 6 August 2009 (UTC)

Last night I successfully ran the team rumble. Every single bot worked except that WonderlandTeam could not be read. Since it's only WonderlandTeam failing, I'm doubtful this is the bug you saw in 1.7.1.x Darkcanuck. What version of robocode did you package WonderlandTeam with Tripphippy? Maybe it's possible the format got changed or that version has buggy packaging code? --Rednaxela 15:26, 6 August 2009 (UTC)

I packed the team using the most recent version that I downloaded yesterday. --Tripphippy 15:41, 6 August 2009 (UTC)

Robocode 1.7.1.3? Perhaps try with 1.6.1.4? When I get home I'll look at the jar of WonderlandTeam and see if I can see any oddities by hand. --Rednaxela 15:46, 6 August 2009 (UTC)

Removing bzdp.BoxCar 1.0,3702 since it cannot be downloaded, nor can an alternative download location be found by me. --Rednaxela 23:55, 5 August 2009 (UTC)

I'm working on rumble@home and it doesn't have any team rumble specification. Do anyone have a copy of that?

I entered my team into the tournament by adding jeremyreeder.collective.TwoProphets to this wiki, but it when I look at the results I'm not in the list. It's working for all of my individual robots, but why not for the Team and TwinDuel ones?

It could just be that nobody is running clients for Teams and TwinDuel. Could you try configuring a client (see RoboRumble/Starting With RoboRumble) and firing it up? I can test a TwinDuel client later tonight. I haven't run a TeamRumble client in a long time, seems like I always had issues...

I am running clients for all leagues. I remember seeing the client showing errors for TwoProphets.

I would advise JeremyReeder to run the clients himself after adding participants in the rumble, to check if everything is ok.

Both your TwinDuel teams seem to be running for me, so they should get results once my client uploads some. But there is a problem with DuoLedByDroid: the team references the development version of BlindMan, while BlindMan 1.0 is what's packaged in the JAR, so Robocode says Can't find robot: jeremyreeder.collective.BlindMan* and it's a 1v2 battle. If you want to see what I mean, unzip the JAR and look at DuoLedByDroid.team and BlindMan.properties - the * in the version number means development version.

What you probably expect to happen is you have your dev version team of dev version bots, and when you package the team, it first packages the bots to real versions and then packages the team. For some reason, the .team file in the JAR still points at the dev version, even tho it correctly packages the bot.properties file to use the same version as the team version you specified. This seems like a bug (unless anyone knows why it should work this way?).

TL;DR What you need to do is package the individual bots to real versions, then package a team with those versions and everything should work.