Thread history

From Talk:RoboRumble/Participants/Teams
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
17:09, 17 March 2012 Voidious (talk | contribs) New reply created (Reply to Why isn't my team playing?)
19:29, 14 March 2012 MN (talk | contribs) New reply created (Reply to Why isn't my team playing?)
17:30, 14 March 2012 Voidious (talk | contribs) New reply created (Reply to Why isn't my team playing?)
17:20, 14 March 2012 JeremyReeder (talk | contribs) New thread created  

Why isn't my team playing?

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?

JeremyReeder17:20, 14 March 2012

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...

Voidious17:30, 14 March 2012

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.

MN19:29, 14 March 2012
 

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.

Voidious17:09, 17 March 2012