Thread history

Fragment of a discussion from Talk:Gilgalad
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

Hi all. Apparently all we need to do is to report bugs to developers :) I did so and Fnl fixed it within a day.

I suggest everyone to upgrade to 1.9.2.2 and kindly ask Rednaxela to tune rumble server to accept client with this version and above.

Beaming (talk)00:24, 4 September 2014

It would be Skilgannon that runs the rumble server, not I. ;)

Rednaxela (talk)14:16, 4 September 2014

Shame on me, I keep doing this mistake over and over :(

Beaming (talk)16:24, 4 September 2014

No worries =) The rumble is updated, and only accepting contributions from 1.9.2.2

Skilgannon (talk)18:18, 4 September 2014

Beaming, it seems your new client is still uploading megabots to the minirumble :-/

Edit: never mind, it now seems to be removing them. Maybe they were left over from the old install?

Edit2: it seems you have two clients running, one is removing and one adding.

Skilgannon (talk)08:19, 5 September 2014

Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.

I do not get it: microrumble and nanorumble seems to be fine with either of the clients, but minirumble is populated with megabots. Any idea what is going on?

As fat as I see after some tests, it is not a particular client issue. At start up, either of the clients cleans the mess, i.e. removes bogus entries. But then as it runs, it reintroduces them.

Also, both clients complain:

Could not load properties file: ./roborumble/files/codesize1v1.txt

I will report it to Fnl again.

Beaming (talk)13:41, 5 September 2014