Hi,<br><br>I've had a go at making a robot battle game in Haskell (a robocode clone), I was using Yampa for both the robots and the game logic - however using Yampa for the game logic presented a number of problems, mostly in ensuring every single piece of data "emitted" from the game logic portion was evaluated.
<br><br>I had a fair amount of work done, and it was shaping up nicely, but it needed simplification, trying to add in too many extras such as physical simulation of collisions etc. turned it into a bit of a monster when the core design needed some work!
<br><br><a href="http://saulzar.orcon.net.nz/robots2.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://saulzar.orcon.net.nz/robots2.jpg</a><br><br>I'd definitely like to give it another go, this time without Yampa for game logic - though it seems fantastic for the user robot code, perhaps it needn't be compulsory - interested users could always use Yampa if they desired.
<br><br><br><br>Oliver Batchelor<br><br><br><div><span class="gmail_quote">On 7/16/07, <b class="gmail_sendername">apfelmus</b> <<a href="mailto:apfelmus@quantentunnel.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
apfelmus@quantentunnel.de</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hugh Perkins wrote:<br>> Had an idea: a real shootout game for Haskell.<br>><br>> scripts "fight" in an arena for a second or so, and the results are
<br>> published to the website<br><br>Sounds great :)<br><br>There are lots of "robot battle" games out there, like<br><br> <a href="http://realtimebattle.sourceforge.net/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://realtimebattle.sourceforge.net/
</a><br> <a href="http://robocode.sourceforge.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://robocode.sourceforge.net</a><br><br>but none in Haskell, of course. I think there's a classic predecessor to
<br>those but I don't know exactly.<br><br>> Each turn is represented by a function something like:
<br>><br>> doturn :: String -> [[GridValue]] -> (Action,String)<br><br>The explicit state can be dispensed with by introducing a stream type<br><br> data Robot = Robot (BattleField -> (Action, Robot)<br><br>
type BattleField = [[GridValue]]<br><br>This way, the program is entirely free in how to choose its state<br>representation. You can turn any doturn - based program into a<br>stream-based one<br><br> toRobot :: String -> (BattleField -> String -> (Action,String))
<br> -> Robot<br> toRobot s doturn = Robot $ \arena -><br> let (action, s') = doturn bf s in (action, toRobot s' doturn)<br><br>The drawback is that it's no longer possible to save a snapshot of each
<br>program's state to disk and resume the fight later.<br><br>Regards,<br>apfelmus<br><br>_______________________________________________<br>Haskell-Cafe mailing list<br><a href="mailto:Haskell-Cafe@haskell.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Haskell-Cafe@haskell.org
</a><br><a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br></blockquote></div>
<br>