Castle Story is a promising idea. It is castle building game where you will be placed in control of these small yellow, minion-like fellows called "Bricktons." The building mechanics are interesting, though not the easiest to grasp as soon as you reach a certain point of understanding you will be building with ease, if you dont mind placing each bick individually. There appears to be issues with deleting placed items and qued blueprints. Each action is seperated into a task group where you can easily assign workers to certain tasks. There are also some minor issues with the AI, sometimes they sit around staring at walls or refuse orders as if they are having a minor stroke, but they usually recover in several seconds.
Now for the reason you came: Do I think you should buy this game?
Yes and No.
Im going to cover the "No" first only because it is the easiest to cover. If you scroll down you will see a wide variety of reviews, you have negative reviews and more negative reviews. If you read through them you'll notice that most of them are saying things such as: "Its too buggy" "The building system is bad" "Game developement is too slow" These are the 3 big points that people are using to scare others away from the game, so lets take a look at them!
1. "Its too buggy" It can be buggy at times, but honestly in my about 14 hours of gameplay (I dont understand why it says I only have 1 hour of gameplay -.-) I've had only a few crashes or stability issues. And recently those issues have been becoming rarer. Basically, you can play the game without having it crash too much, but it will most likely crash on you at least once. On the AI issues, the Bricktons do have some issues but if they arent building what you want them to build then the most common reason is they cannot build it.
2. "The Building system is bad" The building system has issues, I agree, but not enough to say: "STAY AWAY!" Its hard to delete things, manual placement can become annoying, and certain mechanics are not fully explained in-game. I would suggest watching a video on YouTube explaining the basics, I'm sure there is one out there!
3. "Game Development is to slow" I always laugh when I see this one, but honestly its not funny, its sad. Lets look at a few facts:
this is Sauropod's first project, so they would have been learning a LOT of new things about workflow and management of content and community.
They are not a large corporation, as far as I can see there are about 13 members who are currently working on the project. Have a look at their website and you'll see that they have a roadmap of all the features that are currently deployed and what they would like to put into the game.
A ton of game processes are frameworks/behind the scenes mechanics that you will not see if you briefly log on and fiddle with a few things and then log off. These are patches that make the game stable and make way for new content.
Now for the "Yes" side. It will be quick, I promise.
You get to build a castle, brick by brick. There are very few restrictions to building with the bricks as long as you understand basic physics and have a creative mind. The game feels good to play, the theme of the game is fantastic and the art meshes together well. Even the music fits with the game.
Buy the game if you are interested in supporting an indy Dev team on their first project, love to build casltes, or love cartoony graphics.
Don't buy the game if you are looking for a finished/polished product of 5 years from a major studio, or can't be bothered to understand some basic building mechanics. (Please look up a video explaining the controls.)
There are only three truths of Indy developement: there will be bugs, the developement will take time, and you will lose save files.