Thread history
Viewing a history listing
| Time | User | Activity | Comment |
|---|---|---|---|
| 22:54, 23 June 2013 | MN (talk | contribs) | New reply created | (Reply to Custom client bug) |
| 21:40, 23 June 2013 | Sheldor (talk | contribs) | Comment text edited | (minor edit) |
| 21:34, 23 June 2013 | Sheldor (talk | contribs) | New reply created | (Reply to Custom client bug) |
| 18:20, 23 June 2013 | Skilgannon (talk | contribs) | New reply created | (Reply to Custom client bug) |
| 18:11, 23 June 2013 | MN (talk | contribs) | Comment text edited | |
| 18:11, 23 June 2013 | MN (talk | contribs) | New reply created | (Reply to Custom client bug) |
| 18:50, 22 June 2013 | Skilgannon (talk | contribs) | New thread created |
Just to let you know, your client is uploading bots with codesize 250 (UnterBot, Spiral, xbots), to the nanorumble, when only 249 and less should be there.
To make sure:
- nanobots are 0 to 249.
- microbots are 250 to 749.
- minibots are 750 to 1499.
- megabots are 1500+.
Technically speaking, the roborumble weight classes have no minimum thresholds, only maximum thresholds. Thus, each rumble contains bots not only under its own weight limit, but also bots under the weight limits of other rumbles with a smaller maximum threshold. For example, just because a bot with a codesize of 249 bytes is a nanobot, it is no less a microbot than a bot with a codesize of 749 bytes. This is how the weight classes are structured: nano < 250 < micro < 750 < mini < 1500 < mega < positive infinity. Note that we use < and not <=, which is why we don't allow bots with a codesize of 250 bytes into the nanorumble.
