1. 22 Dec, 2011 1 commit
  2. 20 Dec, 2011 2 commits
    • Sam Moore's avatar
      [RULE CHANGE] *Changed rule for Bombs*, tweaking vixen agent · f74c2985
      Sam Moore authored
      Previously, contact with a Bomb destroyed the Bomb even if the attacker was not a miner.
      Now, the only way to destroy a Bomb (ever) is to attack it with a miner.
      Yes, this means that if the enemy Flag is surrounded by Bombs and and AI has lost all its miners, it is impossible to win.
      This reflects the rules of the original game. My version is now identical to the original game.
      My original rule was intended to decrease the emphasis placed on Bombs and Miners.
      Having played a few games, I think the traditional Bomb rule is more interesting, even if it makes things harder for the AI.
      If there are any problems with this change, please email [email protected]
      I will be happy to revert to the previous rules if there is demand. This also goes for the change to equivelant ranks combat (earlier commit today).
      Updated vixen agent's scoring to take into account the change.
      Yet to update asmodeus's scoring.
      The AI's seem to have a much harder time now that they have to take out Bombs
      Games often result in draws, because the Miners are easy targets and get killed whilst seeking out Bombs.
      The AI should probably defend certain pieces with stronger piece combinations nearby. But this is all getting rather complex for a "sample" :P
      TODO: Implement victory condition when opponent has no mobile pieces
      	(Currently play continues until the player with mobile pieces ends up attacking Bombs because it has nothing else to do
      		at which point the game is a draw because neither player has mobile pieces)
    • Sam Moore's avatar
      Small changes to several things · 345d8b1f
      Sam Moore authored
      Changed combat outcomes for equivelant ranks:
      Up until now, victor was randomly chosen
      Changed so that result is always "BOTHDIE"
      Updated manual page for manager
      Added section on unbuffered stdin/stdout
      Modified sample agents to take into account MULTIPLIER
      There is no way for a human player to move the scout multiple spaces yet.
      Sample agents still play each other fine, but since none of them actually move scouts multiple spaces,
      this doesn't prove the new code works.
      TODO: Test properly (add scout movement to asmodeus and see if everything still works?)
      Updated webpage.
      Added section on unbuffered stdin/stdout
      Added some other pointless waffle. Mmmm waffle.
      Make simulate.py keep track of the round number properly.
      I'm sure this is simple to do, but I can't be bothered right now.
  3. 08 Dec, 2011 3 commits
    • Sam Moore's avatar
      The /home was not necessary · 88fc5a96
      Sam Moore authored
    • Sam Moore's avatar
      Changed the directory structure. · e3b15cd5
      Sam Moore authored
    • Sam Moore's avatar
      Modified manager program, updated website · 17a20de4
      Sam Moore authored
      Major changes: Added simple GUI for human players
      Setup phase doesn't use GUI yet (uses a default if -g enabled).
      Click in the general region of where you want to select/move pieces.
      Modified Board::Draw to allow for showing of already revealed pieces,
      but not all pieces. Used to make human player GUI nicer (hides AI pieces).
      Modified -t switch to allow for "infinite" stall_time
      (wait for user to press enter)
      Changed website. Removed protocol description and linked to manual.txt.
      Added screenshot to make things slightly more exciting.
      Updated manual.txt
      Minor changes to simulate.py (output)
      Fix segmentation fault found in manager program
      It occurs just before exit. Memory error in the cleanup process?
      Still have to bring myself to take the time to finish setting up that vm...
      Need to talk to a non-hostile wheel member about security. I don't want my vm to take out our network or something.
      Preferably I don't even want the vm to be compromised, regardless of the rest of ucc.
      So much I don't know about servers/linux...
      Need to stop staying up past midnight...
  4. 07 Dec, 2011 1 commit
  5. 03 Dec, 2011 2 commits
    • Sam Moore's avatar
      More adding of pointless crap to manager · b563784f
      Sam Moore authored
      -f option to allow replaying of games output to files with -o
      -m option to enforce max number of turns (default 5000) before a DRAW is called
      -p to print a colourful representation of the board to stdout
      Yes. I now have both graphics AND pretty coloured terminal escape codes.
      Why did I do this??????????????
    • 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...
  6. 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
  7. 30 Nov, 2011 1 commit
    • Sam Moore's avatar
      Modified Turn Response Protocol, added handling for SIGPIPE, changed placeholder images · 2ab27eb6
      Sam Moore authored
      The "outcome" of a move is now listed as:
      Where ATTACKER_RANK and DEFENDER_RANK will be present if TYPE is one of: KILLS, DIES, BOTHDIE, and indicate the ranks of the pieces involved.
      This involved adding a class MovementResult, which stores the ranks of pieces in addition to an enum, replacing the enum Board::MovementResult
      The sample agent "forfax" was causing broken pipes, which caused the manager program to exit.
      I added a handler for SIGPIPE in manager/main.cpp to ensure that the manager program reports a DEFAULT victory to the other AI, and exits gracefully.
      However, I still don't know WHY forfax causes broken pipes, but hopefully its a problem with forfax and not with the manager program.
      I edited the images used by the graphical display to show the ordered ranks of the pieces, rather than some obscure characters.
      Unfortunately I have just realised that the enum used for Piece::Type stores ranks in the wrong order.
      In the actual game, LOWER numbers are better, in my enum, HIGHER numbers are better.
      To make things more confusing, I made the printed ATTACKER_RANK and DEFENDER_RANK correspond to the traditional numbering, not the enum numbering...
  8. 29 Nov, 2011 1 commit