Saturday, November 22, 2014

Dragon Souls Prologue Status Report #1


     Unicorn Training released a week ago (Get it here!) and another project is already underway! It's full steam ahead as I try to make another game before app stores close for the Holiday frenzy. This is also the beginning of my new blogging schedule where I only post twice a week (Tuesdays and Fridays). I want to do Status Reports on Tuesdays so I can show weekend sales (which I assume are more interesting) and I'll do weekly posts on Friday showing the most interesting developments on whatever my current project is. This report will stand in place for this Tuesday's so don't expect any updates until this upcoming Friday.

Here's week one of Dragon Souls Prologue and a new Yotes Games!
Check out Unicorn Training sales data below!

Friday, November 21, 2014

Next Project: Dragon Souls Prologue (Arcade Hack n' Slash)

Dusty old doc from before Unicorn Training...
    It's finally time to talk about this thing. This game I've been trying to make since I first learned C++ in high school. Back then it was called Dragon's Flux, but now... Dragon Souls. Trademarked. Actually, I'm just holding onto the trademark since it isn't set in stone unless I provide proof of use in commerce within the next 4 months. It was a really good name that describes the theme perfectly and before Yotes Games was even a thing I saved up to buy the name "Dragon Souls" as the name of my own video game series.

     Sadly, like Unicorn Quest, I'm not able to make this huge RPG adventure just yet. Especially with school in the way. Instead I'll be pseudo-introducing the game's protagonist and world rules. I say "pseudo" because unlike with Unicorn Training it's going to be very unrelated to the actual game series in terms of gameplay. This is a fast-paced action title with one mode and one rule: Survive.

Thursday, November 20, 2014

Wrapping Up Unicorn Training


     Even a week after launch it's still not over. I severely underestimated the amount of testing needed for a game this complex. Bug fixes have been flying up all week at the drop of a hat as I hear about a bug from someone at least 3 times a day.

    Each time I think I'm finally done, but something else pops up as soon as I get ready to start my next project (the ever stacking amount of schoolwork doesn't help either). If something pops up I have o fix it because I don't want to leave a broken project behind. I want this game to have a long sales tail so it needs to be considered good in the long run.

     In terms of publishing experience, I finally have a concrete list of useful app stores to upload to. I also made a set of screenshot resolution templates for all of them. The artwork this time around was pretty good, so the next project should be a hit in that department. It's playtesting that needs to be kicked up a notch the next time I make an RPG.

     I also need to design a new control scheme, which brings me to my next project. I'm trying to make a small game within 4 weeks that uses a grid-based movement system that should feel much more solid than Unicorn Training's wonky collision boxes and movement.

    If I finally clear out the last of the game's bugs I can get started on that.

Get the (hopefully) bug-free Unicorn Training on Google Play!

Wednesday, November 19, 2014

Unicorn Training Weekend Sales


     It's an early status report but I'm sure some of you are as interested as I am in seeing how well Unicorn Training did on its opening weekend. It's doing better than I expected and my inner flame burns brighter than ever knowing that I have a real chance at being a successful indie developer! I don't see me making enough for a Macbook just yet, but I can expect my first ever payment from Google to come in next month!

Catch some rankings and numbers to satisfy your curiosity below the break.

Tuesday, November 18, 2014

Press Kit Trouble (It'll Have to Wait)


     I took a look at Pixel Prospector's list of indie dev press kits and starting thinking of ways to organize my game stuff in a professional way as practice for when I try to get big-time game journalists' attention. I thought that using the presskit() program would be as easy to use as Blogger has been for running this website, but it turns out to be more complicated than that and may even cost some money to run over the years. It's basically not something to be handled in the middle of a school week and I'll have to put it off until I have time to look into making a great game press kit.

     Making something nearly as nice as Shovel Knight's on a budget of zero is harder than I thought it would be.

Monday, November 17, 2014

Bugs... Bugs Everywhere...


     The release of Unicorn Training came with the expected nervous waiting for something to go wrong. In this case, many things. Being that I've never made a game this complicated, I had exponentially more bugs post-launch than I'm used to (with games like DragCore). I had some shaky internet access all weekend so there were lots of moments where I wondered what could go wrong next. The feeling disappears when I upload a new patch, allowing me to rest easy with the feeling of having a game that works. Too bad it's not permanent because I know there are some things wrong with the game that can't be changed due to the way certain systems were designed.

Sunday, November 16, 2014

Join Yotes Games on Google Groups For Early Access!


     I was inspired by this Gamasutra article to get serious about using Google Groups for public testing. It may not be useful at the moment but having a playtest group / forum ready to go will benefit me in the long run. My upcoming game will be pretty community dependent as I try to make a competitive turn-based RPG. I'll need hundreds of Alpha and Beta testers to get it just right. Having tons of people involved in testing will help out marketing wise too as people spread the word.

     If I ever release a public demo or give out early access codes, it's going to be to people in one of these groups. Yotes Games Exclusive will be for the few I choose to help me find things like game breaking bugs or play through spoiler filled story moments that I don't want the public to see. Yotes Games Playtest will be wide open for anyone to find, share, and post to. This is where I can get feedback on balancing and what people like, dislike, or get confused about. This would be the stable build I push onto YouTubers who want to play an early version of the game.

If you want access to public playtest builds of my future android games, participate in exclusive download code giveaways, or post on a forum that I will read regularly: