The "Portland Indie Game Squad" (PIGSquad) out of Portland Oregon has been around a few years before I joined up.

I can't praise this group enough. They are a very diverse community and very sensitive and diversity conscious group. The are very self-critical to the fact and as long as they continue to try to improve their inclusive nature I believe they are going to remain welcoming. It is a safe place to be yourself and every skill level and interest.

The benefits of membership is great (you just show up btw, 90% of most battles are won by just showing up [1]) You get feedback, you get to peek at the process others are going through, play ideas and participate in the most extraordinary part of game design, the part where you get to get feedback.

The chance to get feedback at Art/Code night and the monthly meeting to engage in deeper discussions about our regions and global developments in game development are splendid. Could I get all this online? Probably, but it would take 5x the effort I bet. Nothing compares to the efficiency and the diversity of the input and the opportunity to help abounds. I feel like I take more than I give, some of these guys really know what's going on under the hood. But don't let that intimidate! You have got to start somewhere and for Portland that should be PIGSquad if your serious about making games.

So yeah... I <3 the oink out of PIGSquad.

[1] completely fabricated fact.

Not of my own but memory as a game mechanic. The article is interesting, in my opinion, but I am a bias fanboy.

The article does brings up an interesting point that Adams have espoused to embrace and that is it is a game with actionable memory. Its an idea that has fascinated me and I have played around designing with as early as Ultima III and other RPGs in its style where, for example, I would pick a cabbage from a farmers field, he might yell at me then and there because he witnessed it, but he would act like he never met me a if I ran off screen and came back. that always felt 'lifeless' and 'gamey' to me. I have often dreamed of games with better memory. A simple encounter with a recounted memory could really go a long way in helping games 'breath' and feel more alive and powerful. I've even gone so far as to create schema and algorithms to simulate degradation over time and strength of an individual memories. Which would generate weighted responses from "Hi there stranger!" to "long time no see!" and "Why are you still here?" Its a set of ideas I have carried with me for a LONG time and one I will work into my work at some point. This memory feature one of the many reasons I love Dwarf Fortress. The procedurally generated history probably has more impact on gameplay than one might suspect and I am only a player of Fortress Mode. I bet the "Stone Soup" like Adventure mode is a 1000x more interesting because of that memory...


















Crash Cart has released! I am sorry I would have announced it earlier. But really it has been amazing and painful to support this product. There was so much new infrastructure we knew stuff was gonna blow up under load, but not exactly sure where, and it did. But not a complete down and out for more than an hour here and there. We did OK, not great, but OK. Crash Cart has a large server component for such a simple game. We already have gigs of player activity recorded (ghost trails) that can be watched and raced. The account system, although we botched it for 7.6% of people signing up and our auto account system forced some folks to have to create accounts (we really did not want that to happen, but its the work around.) Offline play was kinda rough despite our massive focus on making sure it was possible. And it was but in real world you had to wait for the Apple framework to timeout, which apparently behaves vastly different in the lab environment. We learned a lot there! Still learning, and we are gearing up for the multiplayer competition aspects. Should be fun! We lost many a night's productivity racing.

The next patch fixing auto accounts and some issues in the game is waiting for approval at Apple.

Cheers! And let us know what you think too!

All right! I figured it was about time to update the world... (that and I fixed the broken user account database on the site... no account, no log in... not a bad security policy, but it meant I just couldn't post the simplest of updates. It took me several months to get the task prioritized enough to fix it! But here we are. I'm back... Did you miss me?

I have been very busy with my partners at Appsomniacs creating Crash Cart! A new physics based racing action puzzle game... What is that you say? Puzzle racing? for the latest explanation head on over to and check it out for the latest and greatest (caveat: there is little more than "Coming soon!" atm of penning.) The app is in review at Apple. Assuming we don't have to fix something major we are going launch it soon!

In general Crash Cart is inspired by the likes of various bike/hill climb games but littered with contraptions inspired by puzzle games like Incredible Machine (think Rube Goldberg machines that you drive/race through) and the along with crazy physics based crash antics very much inspired by Happy Wheels (the free version can be handed to to anyone in the family btw) should be a hoot to play. And as a bonus the game comes with a full featured track creator built in. We used the same creator to create the levels in the game and its open to verified users (via email) to post their creations to share and challenge others. It's the same tools we use to build tracks. I don't think we will ever make another game where the user can't influence content. If there is a way we will make it happen.

The first version is free to play, you can play community unrated tracks for free or support the game by buying in app purchases to speed up coin acquisition. There are ads in the initial version and we will offer some alternative ways to tailor the ad experience and earn free coins. We have a lot of plans for this game if it takes off. Consider them stretch goals. What started out as an exploration of infrastructure to advance our Doodle Army series has turned into a very special game to us and we hope everyone finds something about it to love, whether it's the rag doll crash antics, racing friends, or making new tracks to challenge the community. We can't wait to see what the Crash Cart Nation comes up with!

The official site: (it is free btw, they lives off donations)


Best outsider article I have read to date:


A good game developer-centric article:


There is no manual really... just a lot of discovery... however you choose in game or out.


Here is the bit about inclusion in MOMA

Where to start... "Cocos2d-x by Example Beginners Guide" is a good great book! Turns out one of my Appsomniacs partners has bought this book and also enjoyed its knowledge (votes+=2). Even have cut my teeth and shipped on iOS, Android and Windows 8. The Windows 8 was such a hack job I could never get it cleaned up to do a push request (I think, I should just try, at least put it in my branch. Please nag at me if I don't... It may be a bridge too many not subtle changes. Anyway, I digress, the rest of this about this great book that might help a lot of people on their Cocos2d-x journeys.


1) The first thing that popped out at me when I cracked the spine on this book was the large quantity of and the technical diversity of the contributors. I was impressed with their bio/resumes and the book certainly was better for it.

2) Hang on tight. The gas pedal is binary. The book gets you up and running rather quickly. Almost too quick in some respects, but later chapters make up for that hand holding fast start in ten fold. I was worried at first a lot of bits were glossed over. Do not worry about this stuff. Great details will be given in droves, and when not a good entry point to references often sufficed.

3) I actually appreciated the section (within chapter 2) that was a primer on as well as described why the C++ was arranged the way it was (e.g., what conventions were from the Objective C world and reminders of things you need to remember to do when in C++ (i.e., proper memory management because ARC is not available.)) My favorite quote so far "... relax, and let the framework work for you."

4) The learn by example part struck me as well done. It could always cover more. I was wanton for more after 6 games. Maybe combining this and the ideas found in the iPhone Cookbook you could get even more mileage. Frankly, after you tackle this books examples. I did one a weekend (~4 hours in 1-2 sessions usually) you will be pretty well versed. The games are varied enough and the topics within cover a lot of ground. I will always want more!

5) Chapter 10 is gold for anyone coming from iOS and wanting to break into Android and really use the greatness of what Cocos2d-x brings to the table (IMO anyway.) You are presented a nice 'uncluttered' step by step walk through (albeit the compile sections was 20 steps, but they were important 'no fluff' steps! I am pleased they linked their sources on this one too. Our team put this stuff together by piecing together Android NDK posts and trial and error last year (of course we never thought to share because we never thought we did it right to begin with... it compiled... and ran, so we shipped it anyway...) I think the chapter here would have saved us much time and pain. Luckily you now have this resource to leverage. My only wish was that a little more time was spent on the tricks you have to go through to get as clean as code as possible (not special casing every piece of logic with pre-compiler directives, etc. for each platform.) Maybe a little treatise on design patterns would have been helpful here too. But I guess all of that is really beyond the scope of the book (i.e., a lifetime could be spent learning how to write well designed cross platform C++ code. If anyone knows of a good book let me know!

6) I want to mention the index. It was a basic run of the mill index. Don't get me wrong it was a good and proper index. But I can not help but note this book chapters were laid out similarly to the iPhone book "Creating Games with Cocos2d for iPhone 2", which had a brilliant index (I bet someone hated it... those darn trolls convinced them not to do it this way!) In the iPhone book most chapters covered an entire game by example much as this book did too. The iPhone version's index had a breakdown of a game chapter by game name as a sub index of concepts within it. I absolutely loved that and I dearly missed it in this one. The index is fine as it is, but having tasted the other books additional index by chapter concepts I found myself longing for it as this new book was also a perfect candidate for that format as well. But it is no reason to not get this book if the subject interests you. File this under 'I have to find something to complain about in a review' comments.


I do think beginning, but versed, C++ developers could pick this up and succeed if they try. If you have Objective C down C++ is not really that hard to grok also (and the parts you don't use won't likely come into play as nearly as often as you might think.) Advanced users probably won't get a lot out of it, but if you are street learned on Cocos2d like I have been (and still am learning in many respects) it wouldn't hurt to have gone over this material once. 

Thank for sticking out my wall of text this far. I am pretty sure there is an achievement for having made it this far. ;) 

I was reminded the other day of "where to start" with an idea regarding game design and conceptualizing out your game. I was remembering a great bit of information on the topic that was instrumental to me at the time I was getting my feet off the ground...

Ian Schreiber, besides being a pretty nice guy in general, shared some pretty deep thoughts and analysis on game design in a very grand 'global' experiment a while ago in which I only partially participated in. I always regretted having to choose the path I did that took me away from it at the time, but revisiting the material has been invaluable over the years.


I really like this book co-authored by Ian Schreiber and Brenda Brathwaite (soon after Garner, now Romero): 

It all takes a step back from the computer a bit (and that is a good thing sometimes!), but I haven't found a single thing that didn't translate in some fashion. And the techniques on troubleshooting and verifying mechanic, although laborious, I have found worth it.

There are certainly a lot out there. But these two sources have a common voice by Ian and I like his attitude (and Brathwaite has pretty epic contributions to the industry as well and deserves more than a foot note here, but this about Ian.) Someone who manages a production schedule might go insane, but you end with a quality product given the emphasis on testing and evaluation.

Here is your entry point that is as good as any of the best entry points I have stumbled across in my searches yet.

You are welcome.

Well the news is local if you live in Kitsap County in Washington State, in ye olde United States of America (no to be confused with DC!)


As a stalker of me you should know I love me some Dwarf Fortress! I envy Bay 12 in many ways. Being able to work on your life's work is pretty darn cool. I always fear that some day something awful requiring a lot of resources from Tarn and Zach Adams will cause them to be pressured to 'sell out'. I don't think I would mind. Actually all they have to do is ask and I bet thousands upon thousands of us would simply open our hearted wallets and help them through the dilemma.

Nuf said on that.





I just upgraded Xcode to v4.6 (yah yah it took me long enough, we have been VERY busy all over the place.) BUT I am not ready to update all my devices to the latest iOS version (6.1 at the time of this entry) I always forget that I need to go get the previous SDK's. By far the easiest method is to simply use xcode to install them.


From the menu choose Xcode->Preferences and the Downloads tab. I just installed everything since we support all the way back to v4.3, actually we have v3.2 support in most of our games. I think that will change this time around. With Apple's mandate to support, among many things, iOS 6 and the new iPhone screen size (to include updates...) we can't update our older titles with adverts for our new stuff... its a 1st world dev problem... The writing was on the wall last year for a lot of this. We really slacked off on updating. I promise you we will get to it! According to analytics this will screw a couple people who play with older devices... Typically less than three in a month... I hope they forgive us! (I am sorry!!! I really am!!! Apple made me do it! Tongue out )


For now I wait to test the Doodle Army client against my recent server changes...

I have been making great strides in reading through a book on cocos2d (for iPhone) and although I have yet to go cover to cover (I keep jumping around!) I want to get a quick review out for them of the parts I did get a chance to study.

Let me just open with how refreshing it was to pick up a book you are ready for skill wise. I have a few games I worked on in the App Store and I have some [street] experience with cocos2d and this book is a nice fit. So I dive in. You might not want to use this book to start learning cocos2d. And if you read warnings, prefaces, and intros you better pick up on that from the books description real early and IF you still got this not knowing a thing about cocos2d 1) I applaud your tenacity 2) I shame you for not doing some up front due diligence... You have failed yourself. But this post is not about you, BUT if this matches what you did then hang onto the book and go check out Ray Wenderlich's intro tutorials for that (I can't leave you with nothing, this is where I started my education btw. I owe Ray a couple dinners now... I'll settle that account someday.)


So back to the BOOK! As I said I tend to read a book cover to cover, that is my preference. Schedules, releases, bugs, family are just going to let that happen this quarter. But I have been in and out of the text every down moment I had. Which is telling, considering I chose soaking up some tech text versus firing up some Minecraft. I must admit I jumped around a lot! There are some parts that build on one another. Luckily in every case I encountered there is a reference back to the moment I should be building on. Depending on your experience level you might not need that though.


A little side note on finding a specific 'thing' using the TOC (table of contents) or the index...  Since Each chapter is covers a fairly familiar game 'type' unto itself the TOC does not lend itself for specific message lookup. If you are looking for a specific CC message you will want to start in the index. What I did find interesting was each chapters game had a detailed index, so you could scan that and get a *REAL* good idea what each chapter holds. I think that is the primary way since the TOC through me a loop initially. I appreciate the cute names and the text is fun like from time to time. If your not in a mood for that you need to steel yourself for those moments. Work through it! I did. So can you! ;)


This a great concept book with enough concrete examples to get your own code moving in the right direction (including reasoning for the choice of convention in several places, which if was your only awareness of the way something was done *cough* *cough* you [I] would never have known otherwise.) I learned something new (old) from this book I missed in my grueling on-the-street training... For that I give the book high marks. Your mileage may vary, but I appreciate the alternate takes on approaches. I feel stronger because of it. Knowing they exist. 


So the best thing for me in the book... I wish the book was out when we figured out how to do Bluetooth that would have saved us some serious pain in the making of Doodle Army 2. You kids don't know how good you have it! Now get off my lawn! (and you might want to go check out this book!)


The price is not bad at all either! Check it out.


CodeWorx Studios

Welcome! Satisfaction *not* guaranteed. Mileage may vary.