Wrapper doesn't always find robots in team JARs

[Cu3PO42]

I downloaded all robots from LiteRumble (as of yesterday) and tested the wrapper on them. The wrapper did not produce any robots for the following JARs:

abc.ShadowTeam_3.83
bvh.team.Valkiries_1.0
cb.fire.FirestarterTeam_2.0
cx.mini.DemoniacNimrods_0.50
ethdsy.MalackaTeam_1.2
florent.XSeries.Xmen_0.9
gh.mini.GrubbmGroup_0.4
kawigi.micro.ArmyOfShiz_1.1
kawigi.sbf.TidalWave_0.8
kc.twins.GeminiTeam_2.1
kinsen.twin.SelcouthTeam_1.1
l337.L337Team_1.3.3.7
mn.CombatTeam_3.25.0
mn.nano.perceptual.ImpactTeam_1.3.0
mn.nano.perceptual.ImpactTwins_1.3.0
mn.SuperSittingDuckTeam_1.0.2
mn.SuperSittingDuckTwins_1.0.2
ms.AresHaikuTeam_0.3
myl.micro.TroodonPack_1.10
pedersen.ImWithDroidTeam_1.3
pedersen.ImWithStupidTeam_1.3

These are all teams with non-zero rating in LiteRumble, so I was expecting them to work. And some teams are working and producing their members.

It seems to me that the broken teams do not have .properties files for their robots, only .team files. I imagine that supporting them correctly might come down to the same work as is required for #4.

[flemming-n-larsen]

@Cu3PO42 Thank you for testing out the Robocode Bridge. Expect a lot of flaws, and it is good to get them listed.

I have not added team support to the bridge yet AFAIK?
But this is definitely something that must go into the bridge. 😊👍

[Cu3PO42]

The implementation of the legacy Robocode API does have a TeamRobot class, but I haven't verified whether it will work given that the wrapper is created correctly. I suppose we'll see once #4 is resolved.