-
And about IGameModeProxy, that is meant to be part of broader Robot API, provided by extension author. But I prefer to have very stable Robot API, mostly because it's difficult to desing it correctly and backward/forward compatible way. But I would not like to kill the idea of IGameModeProxy.
2010-01-04 20:17:27 UTC in Robocode
-
Josh, I think that what you do is very useful, because we need to try it anyway.
The difficulty with this is not coding, but design, so your effort is not wasted in any case.
What will be the final form, we don't know yet. I believe that both of you are still finding the ideas and building the prototypes. So it doesn't hurt to have several different (competing) approaches. Later we pick...
2010-01-04 20:10:58 UTC in Robocode
-
At first look, good stuff. My initial thoght is if we really want that. Battle class is real core, it defines lifecycle and sends all events. I can imagine that people could extend the class, override something and inject it back. But I'm worried about consistency of different extensions with rest of ecosystem.
My proposal for you is, try to refactor Battle and make it extensible with hooks...
2010-01-03 21:02:41 UTC in Robocode
-
pavelsavara added cmdrdats to the Robocode project.
2010-01-03 20:48:17 UTC in Robocode
-
Oh, crap. I'm leading you to the complex stuff. But for now we just need demo your skills. Because all described below would better to work on in svn. Let's focus on codesize integration you mentioned earlier, shall wee ?.
2010-01-03 11:56:41 UTC in Robocode
-
Good.
Now consider this: we need extensible BattleView for displaying new objects. Not too difficult. But the display is driven by stream of *Snapshot events. We need extend those. They serialize to xml for replay functionality. Extensible again.
And now this: the commands and status is sent in form of message between robot and battle. See ExecCommand and ExecResults classes. This is...
2010-01-03 11:51:10 UTC in Robocode
-
For changing battle rules, you are thinking right direction. But you would need to think also about communicating the new objects/actions to robot. The Robot API. Extensible way. What you say ?.
2010-01-02 22:57:30 UTC in Robocode
-
pavelsavara committed revision 3246 to the Robocode SVN repository, changing 111 files.
2010-01-01 02:06:03 UTC in Robocode
-
pavelsavara committed revision 3243 to the Robocode SVN repository, changing 2 files.
2009-12-31 00:13:38 UTC in Robocode
-
pavelsavara committed revision 3241 to the Robocode SVN repository, changing 37 files.
2009-12-30 23:21:36 UTC in Robocode
