Blogs

The Game Crafter has completely revamped the checkout process to make it smaller, faster, and simpler. Just 2 simple steps. Start by selecting a shipping address. Finish by verifying your order and choosing a payment option.

It looks similar, but less cluttered. More importantly, average checkout times are 300% faster, with less typing and fewer clicks. We’ve also updated the entire site to be speedier with payments. Everything from paying for BOFs to buying crafter points is faster and less cluttered. Enjoy!

The Sprue Challenge has officially drawn to a close, and our judge, Jason Glover, has chosen a winner: Reign Makers. Jason also said that it was an incredibly tough challenge to judge, and that LEADERS of _______ was the runner up.

For a long time there has been a "disliking" of my solitary scenario for "Tradewars - Homeworld" (TWHW). First of all, the scenario is hard to play until you figure out how to beat it - and then it simply becomes a matter of time until you win the scenario.

I don't like it.

And so I began searching for AI mechanics (for another reason altogether). This had to do with the "United Trade Cartel" scenario for the Privateer expansion. I wanted a level of AI that made it that an AI player could play against the player - and have some form of AI that manages the scenario.

Well amazingly we WON the GoDaddy Auction for the domain name http://www.crystalheroes.com.

We are very happy about this and this is the reason for this blog entry: Legendary Souls no more... Our Android game will be entitled "Crystal Heroes"!

So far our team is comprised of one Director and a Solution Architect. I am the end-user in the big picture and will also help with programming on the server side of things.

In my second play test I had a great experience, a group of guys played my game while I watched and took their criticism and discussed different options. The list grew larger. And larger. And larger. It was great that there were lots of things that will (hopefully) make my game better, but how do I implement this in the next playtest? Do I make all the changes at once and see which ones work and which ones don't? That seems like it would be a huge time eater, as each test has taken 3 hours and the end is not in sight, though that's also because of learning curve.