Rsalesc at 00:14, 5 September 2017

2017-09-05T00:14:26Z

Rsalesc: Reply to Client java version

2017-09-05T00:13:06Z

New page

Are we actually talking about time-per-turn problem? I supposed, given the age of Robocode and Roborumble, that this is a well discussed topic and that every possible decision to make the system work fair enough while providing the "contributing" feature was already made. It seems that what we are talking about here is a bug. I know every environment is not equal, but even with the very little time I have on Robocode I could conclude a robot should work under the assumption that at least a reasonable quota of its turn time will be respected (even if in reality it's not eventually). If that quota is not being respected even after like, 10 battles, in a machine that is OK, and the results are absurd like the results [[Beaming]] reported, there must be a bug somewhere, even if it's on [[Beaming]]'s side, and IMO it's worth it to discuss it and, maybe, to find it, since it may explain some other weird behavior in the future.

← Older revision		Revision as of 00:14, 5 September 2017
Line 1:		Line 1:
−	Are we actually talking about time-per-turn problem? I supposed, given the age of Robocode and Roborumble, that this is a well discussed topic and that every possible decision to make the system work fair enough while providing the "contributing" feature was already made. It seems that what we are talking about here is a bug. I know every environment is not equal, but even with the very little time I have on Robocode I could conclude a robot should work under the assumption that at least a reasonable quota of its turn time will be respected (even if in reality it's not eventually). If that quota is not being respected even after like, 10 battles, in a machine that is OK, and the results are absurd like the results [[Beaming]] reported, there must be a bug somewhere, even if it's on [[Beaming]]'s side, and IMO it's worth it to discuss it and, maybe, to find it, since it may explain some other weird behavior in the future.	+	Are we actually talking about time-per-turn problem? I supposed, given the age of Robocode and Roborumble, that this is a well discussed topic and that every possible decision to make the system work fair enough while providing the "contributing" feature was already made. It seems that what we are talking about here is a bug. I know every environment is not equal, but even with the very little time I have on Robocode I could conclude a robot should work under the assumption that at least a reasonable quota of its turn time will be respected (even if in reality it's not eventually). If that quota is not being respected even after like, 10 battles, in a machine that is OK, and the results are absurd like the results [[User:Beaming\|Beaming]] reported, there must be a bug somewhere, even if it's on [[User:Beaming\|Beaming]]'s side, and IMO it's worth it to discuss it and, maybe, to find it, since it may explain some other weird behavior in the future.

Thread:Talk:RoboRumble/Client java version/reply (31) - Revision history

Rsalesc at 00:14, 5 September 2017

Rsalesc: Reply to Client java version