1. 06 Dec, 2011 1 commit
    • Sam Moore's avatar
      Wrote python script to simulate a round · fe470c01
      Sam Moore authored
      simulate.py identifies agents, pits them against each other, and keeps track of scores using files.
      Needs the "info" files in AI directories to determine what file to execute.
      Spent a lot of time learning/failing at setting up vm on clownfish, called mufasa.
      Will finish setting up vm later.
  2. 03 Dec, 2011 1 commit
    • Sam Moore's avatar
      Revamped manager program and added manual page · 4a3c0478
      Sam Moore authored
      Seperated controllers into AI and human controllers, which inherit from the same base class
      Using "human" as an argument instead of an AI program will allow human player. However, the human player has to use the CLI.
      I have tried playing a few games, and it is incredibly annoying using the CLI (especially when each turn was printed to stdout - now suppressed).
      Usually I accidentally enter the wrong coordinates, or spend 30 seconds trying to work out the coordinates of a piece.
      Then when I switch the focus, the SDL window goes blank, and I don't know what the hell is going on.
      In conclusion: Should probably add GUI for human players!
      Created Game class to manage playing the game, rather than hacking everything into main.cpp
      Added argument switches for timeouts, graphics, output file, help, allowing illegal moves, revealing colours etc
      Added result lines (output who actually wins... amazing!) The massive spamming output that used to be printed is suppressed (enable with -o stdout/file).
      Created manual.txt which is the manual page for stratego (the manager program).
      stratego --help will display the page (using "less" - should probably fix for systems without "less").
      Changed tokens used for pieces from alphabet characters to digits for the ranked pieces, 's' for the Spy, 'B' for Bombs and 'F' for the Flag.
      This makes things clearer. The Spy would be "10", except thats 2 characters, which is a bit awkward!
      Didn't change the order of the enum, because thats just asking for trouble and besides, it works.
      Changed stratego to output the characters for the piece, instead of an integer rank (except for Flag, Bomb and Spy, no difference).
      Need to handle situations where a player has lost all their mobile pieces. Do they lose?
      Currently they will be forced to make an illegal move, and the other player wins by "default".
      Found mistake in forfax move score calculation that lead to moves having negative scores,
      and hence occasionally an illegal move would be chosen as more valuable than legal moves.
      Probably fixed. Illegal moves now score -1, so should NEVER be made! Ironically the change seemed to decrease forfax's performance against dummy.
      Forfax still seems to make really stupid moves, and I can't see why. Occasionally it does something smart
      (attacks Marshal with Spy just after the Marshal reveals itself), but I'm not sure how often these are coincidences.
      Even with the devaluing of moves that don't end in combat, Forfax still gets into long cycles of repeated paths with no purpose.
      And Forfax NEVER attacks Bombs or the Flag... even if thats all the enemy has, and even if the attacking piece would be a miner.
      Updated web page. Considering replacing Protocol Description as is with that written for manual.txt, which I feel is clearer.
      Need to make next git commit message shorter...
  3. 02 Dec, 2011 1 commit
    • Sam Moore's avatar
      Fixed "forfax" sample AI · 53a66690
      Sam Moore authored
      Forfax now plays a fairly mediocre game of Stratego
      He usually beats the dummy AI. Usually. After a while.
      Sometimes he gets stuck in a loop where he repeats the same moves over and over again.
      Sometimes he attempts to move bombs or the flag (???)
      He also never actually captures the flag; he just destroys all the enemy pieces before going into a loop.
      This is probably due to the movement value being very low for moving over pieces that are likely to be bombs
      And when all mobile pieces are destroyed, the remainder are seen to be likely to be bombs.
      The segfault was caused by much stupidity involving a for loop in Board::ForgetPiece and the continue statement
      Changed to a while loop to fix.
      Since Forfax works (Although it plays pretty badly) I will probably move onto other things for a while.
  4. 01 Dec, 2011 1 commit
    • Sam Moore's avatar
      Mostly messing with "forfax" AI · 041c37d1
      Sam Moore authored
      It would be nice to have an AI that doesn't segfault.
      Currently segfault caused by Board::ForgetPiece.
      valgrind outputs a lot of wierd crap about std::vector and uninitialised values
      Uninitialised values created by std::vector::push_back()
      All I am pushing is a simple pointer (Piece*), so I don't know WHY uninitialised values happen...
      The std::list used in MakeMove is somehow using the same memory as the std::vectors of the board, which is causing invalid reads
      Stupid, stupid stdlib.
      I think that once that is fixed, forfax is pretty much done. I'd like to see how well it plays, but... segfaults.
      I also fixed dummy to take into account the modified turn protocol which prints piece ranks. dummy just reads them and ignores them.
      I plan to make the manager program more useful
      	- Enable human players
      	- Add command line arguments for things like timeouts, graphics on/off etc
      	- Read a game from a file (so that games can be viewed after they are run)
      I need to go through the manager program carefully and make sure that the way AI programs quit actually works
      Ideally the AI program has a short period to exit gracefully before it is killed
      I think for some reason the AI program always just gets killed.
      At some point I need to setup a VM for this. I should probably do that.
      I also might change minor things like the tokens (from random characters to digits + a few characters) and the internal ordering of the enum Piece::Type