• About
  • Gallery of Images
  • Archives
  • Categories
  •   Playtesting a card based game

    6/02/11 - 13:10

    As mentioned before, my primary thrust of game work has been with Project: CARDS.  The wiki itself is filling itself up with ideas and concepts, and things most definitely are taking shape.  The idea with Project: CARDS is that there is a battle field, you and an opponent traverse while casting spells at each other in the form of cards which take the form of a real spell ( i.e. a giant fire ball ) or a creature ( i.e. a Daemon Mole of Doom ).

    Both Inko and I contributed to a theoretical combat system, and constructed a pool of 20 cards representing spells and monsters.  All very well, but what is the point of creating a combat system unless it is fun?  So I decided it would be a good idea to actually roleplay a battle.  A new section of the wiki was created, and Inko and I randomly assigned ourselves a shuffled deck, and started to play a game.  Each turn was updated on the wiki, with the following template :

    • <whoevers> turn
    • A map to show castings/movement/damage
    • Our entire deck, with the ones in our hand in bold, an X to show a card that had been cast that turn
    • Current mana levels
    • Our thoughts and overall thoughts andstrategy for that turn and future turns

    The map we played on was quite small – we wanted to get into battle without spending ages getting ready.  The combat was vicious but fast – the mechanics as we played seemed to work really well – with the exception of manually updating a png of combat – every turn was quick.  The mechanics themselves are pretty simple, but really do work well.  As we had both written the combat mechanics, we both knew what was going on.  But even though we both thought the combat rules were pretty tight – it turned out there were quite a few things that we hadn’t thought of during the planning phase.  We used the talk page of the battle test to discuss and ask questions and agree on things when these issues cropped up.

    This play test was an awesome idea.  It raised a number of issues, as well as helped us cement the vision we both have of the game.  We both now have a much greater idea of how the game will play as well as starting to get an idea of balance.  It turns out our initial system of randomly making cards and costs wasn’t the best way to design the decks 🙂  We have identified some key attributes of the cards which will need to be thought about quite carefully before the next play test.

    So, to anyone else out there designing a card/board type game, let this be a heads up, playtest often and early!

    Oh, and the winner of the first playtest?  Inko – he melted my face off with a fire spell as I hid behind my large monsters.  D’oh!

    How I imagine I lost

    My face! My beautiful face!

    Not actually part of the playtesting procedure, but thought it would be nice to commemorate the first ever battle.

    lamentconfig
    Share

      The End Of SpaceOreMiner

    31/01/11 - 22:11

    Na, only joking 🙂  Bet that got you worried 🙂

    With the installation of the Galactic News Network, I’m putting SpaceOreMiner to the side for a while.  I’m quite happy where it is, though actually just want to tweak the graphs a little on the stats page ( always more coming ! hehe ).  Though I am sure I will be returning to SpaceOreMiner in the near future, I am focusing my efforts on a different project.

    A couple of weeks ago, a friend of mine, Inko, approached me with an idea of forming a small team and developing something together.  After much conversation back and forth, we roughed out an idea of a game we would both enjoy developing together.  I’ll be posting here, and on the blog we created for the new game : Project: CARDS.  More info and details will be coming soon.

    lamentconfig
    Share

      Sneaky Spam

    29/01/11 - 15:37

    Yesterday, I got a surprisingly clever bit of spam in my comment section.  So I thought I would blog about it just to help fellow bloggers realise about it.  The comment itself looked like this :

    Hi, I left you a DOFOLLOW backlink on my website. This isnt a spam message, i actually did leave you a backlink on my site. If you check the top of the page you will see “Sites we like” and there will be a link to this site. Would you be kind enough to leave me a backlink? If so my website is CENSORED please use the anchor text “CENSORED” for the link and add it to a post or as a widget. Then please send me a email at CENSORED@CENSORED – If you want me to change your links anchor text let me know. Thanks

    On clicking this link it took me to a page containing a “Sites we like” section, with the only link on it being mine, along with a browser based game under it.  Oh wow, I’m the only site they like, lucky me!  So, I decide to open the page in a different browser, because something didn’t feel right.  Lo and behold, there is an empty “Sites we like” section.

    Sneaky fecks.  Basically, when you follow a link, your browser sends a bit of information to the link saying what page sent you.  This is known as an http referrer.  So this person had a script that if it detected an http referrer, it would automatically construct a link back – to fall the visitor into think there is a link back.  Absolute rubbish when it comes to link exchange or SEO – it is a sneaky trick to try and get one way links.

    I’ve left the site details and things out of the above, but other than that the comment is word for word – so please feel free to check your own comments for back-handed comments similar to this.  If you do find a site that claims to link to yours – go visit it in a different browser, going directly to the page rather than heading back to it – this way if they have been super sneaky and used a cookie to store the originating site ( which would have been a simple thing to do, so no idea why the lame site didn’t do it ) then you will see that there is no back link.

    That is all for now folks 🙂

    lamentconfig
    Share

      A great use of bombs :)

    20/01/11 - 23:53

    It looks like Eric really loves the bombs 🙂

    Bombs Away!

    Bombs Away!

    lamentconfig
    Share

      Eeeeep, bugs ahoy!

    18/01/11 - 17:46

    Though I am not blogging much during this period, I’m checking my email daily, along with the game stats, and removing vasts amount of spam that come in each day.  Keeping all the updates updated, and so forth.

    Utter horror filled me when I attempted to log in today.  Instead of my normal wordpress login screen, I was greeted with a rather scary looking set of error messages :

    Warning: Cannot modify header information - headers already sent by (output started at 
    /path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in 
    /path/greenslimegames.com/blog/wp-login.php on line 337
    
    Warning: Cannot modify header information - headers already sent by (output started at 
    /path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in 
    /path/greenslimegames.com/blog/wp-login.php on line 349
    
    Warning: Cannot modify header information - headers already sent by (output started at 
    /path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in 
    /path/greenslimegames.com/blog/wp-includes/pluggable.php on line 690
    
    Warning: Cannot modify header information - headers already sent by (output started at 
    /path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in 
    /path/greenslimegames.com/blog/wp-includes/pluggable.php on line 691
    
    Warning: Cannot modify header information - headers already sent by (output started at 
    /path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in 
    /path/greenslimegames.com/blog/wp-includes/pluggable.php on line 692
    
    Warning: Cannot modify header information - headers already sent by (output started at 
    /path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in 
    /path/greenslimegames.com/blog/wp-includes/pluggable.php on line 890

    Terror filled my heart – had my blog been hacked?  Had I started blogging about how certain pills had increased the size of  my manhood by many inches, along with giving me a six pack and made me able to automatically date every girl on facebook?

    I checked the front page of the site, and thankfully, I saw no posts like that.  Unable to log in, I went to the next best thing – I loaded up my FTP client and opened the offending file ( services.php ).  To my great relief, I saw the problem.  For some strange reson, upgrading the addtoany plugin to version .9.9.7.3 caused a tab followed by a \n to appear on line one of this file.  PHP sent this tab and newline to the browser, which meant it couldn’t send cookie info first.  Which caused everything to fall on it’s head.

    Quickly deleting this, and making sure that <? appeared on the first line solved the problem, and I could log in post.  Let this be a lesson to everyone who uses the automatic update features of wordpress – make sure you check everything works properly before signing off for the night.  The login screen being down isn’t the world’s biggest problem.  But what if it had been something the prevented my front page from being accessed?

    UPDATE : After a quick google, I found the problem was resolved very quickly by the addtoany team.  LINK

    lamentconfig
    Share