I recently answered a short barrage of questions by some non-technical folks researching the business feasibility of board game conversion. Since I gave them these answers freely, I thought I would also post them here. This is all based on my own personal experience, so feel free to exercise skepticism and I absolutely welcome your thoughts or differing opinions in the comments below.
1. What resources estimates and how much time do you feel is needed to do a strategy board game conversion to digital?
The answers for this question are as varied as the answers to the question “how much time is needed to do a mobile game?” In my experience, if you’re paying your programmer(s) what they’re worth (which is not a given in the gaming industry), you’re probably looking at a budget somewhere between 30k and 120k. Less is certainly possible with an experienced team, maybe with a code base they’re reusing, but it would raise a red flag for me. (I get a lot of potential clients who come to me with 2-5k, and I politely tell them that we can possibly make a prototype without graphics for that much.)
2. If using Unity as a gaming language, what do you think is involved in porting to another platform say from iOS to Android or vice-versa?
I am familiar with unity, but no expert. (So take this with a grain of salt.) My feeling is that android is more work, what with supporting all the different screen sizes and hardware/processor idiosyncrasies, so if you’ve already done that work, porting to iOS should not be that much more difficult. (Depending on the project, of course.) Going from iOS to android on the other hand could take longer, especially for complex games. (It’s going to depend on how many screens or “scenes” you’ve got to prepare in unity.)
3. Are you aware of what the maintenance/support costs would/could be, if so what do you believe is involved?
This is a great question! Not something a lot of clients think to ask. It’s easy to throw something in the App Store and forget about it, which is exactly what everyone else will do too.
There are obviously diminishing returns though, so I recommend planning a release with at least one maintenance update about a week or so after the initial lunch, and maybe evaluate then whether it’s worth doing another “feature” update a couple of weeks to a month later, also with a follow up maintenance update if your budget can stand it. If the game is still doing well at that point, it’s a good idea to plan to spend some time and push out littler updates as frequently as you can, more for marketing purposes than for any development related reason. All of this will require developer involvement, but it’s the person crafting marketing and messaging that should be spending the most time after launch. I generally think this is underestimated, and can easily be a full-time task.
4. Do you have an idea of hosting (storage/bandwidth) costs?
This is only relevant if you are hosting your own server for some reason. The game should have a website, which is another often overlooked marketing piece, but it will cost far more to create that than to maintain/host it. (Hosting fees shouldn’t run more than $20/ month, or you’re probably getting ripped off somewhere. I pay $5/month + $10/domain, but that comes with doing mostly my own support.)
If you ARE hosting your own backend multiplayer server, you can think of it as another domain name. (It definitely cost you more up-front to develop, so make sure your dev is including that in their estimates.) And unless the game is super successful, most hosting plans should include enough bandwidth. If you get to the point where you are paying ala cart for bandwidth, it still shouldn’t be more than a handful of dollars unless you’re at an extreme end of the spectrum, which is a problem you wish you will have.
5. What’s your thoughts on the digitization of family board games, and what may happen, and when?
Well, “family board games” is a term that might mean a bunch of different things, but here are some initial off the cuff thoughts:
a) it’s already happening to some degree, see Monopoly, Scrabble, Jenga.
b) The family market is much larger than the hobby market, but much tougher to crack. Quality is going to be a very important consideration, as is ease of use and first-run experience, including tutorials and teaching.
c) It’s possible that the aforementioned digital game examples are mostly getting played by board game hobbyists, rather than the general populous you’d expect to be playing a family game, which would be hard to prove either way unless you are the publisher of one of those games.
d) In general, (this is advice I like to give to anybody thinking about physical game conversion), the advantage that board game conversions have over their fully-digital counterparts is that there is already a population that knows about that game and to a lesser extent how to play that game. So the bigger that group, the bigger your advantage. How successful your board game conversion will be is very much influenced or enhanced by how successful a game you are choosing to convert.
6. Are you familiar with Steam, and would you recommend porting or building for that platform?
If you want to target desktops (OSX, Windows, or Linux), then I would highly recommend building working with Steam. I cannot make a recommendation about whether those platforms are viable for board game conversions in particular. Steam is a bit like Apple’s App Store and Game Center rolled into one, but cross platform for desktop games. There is an API that you as a developer can write to, and implement Steam achievements and various other social offerings.
7. Do you feel the effort to port from say Android/iOS phones requires more work to port to Tablet versions as well, or not?
Generally there is a portion of every project devoted to UI work. The amount of time spent will be different for every project, but generally I think it’s a higher percentage of the project for games than other application types. Let’s say, for a game, 50% of the development effort was put toward UI work. If you had only developed for one screen size at that point, you might have to re-do or at least re-touch much of that work. If you plan from the beginning of the project for multiple screen sizes, you can save yourself a lot of pain in “porting” to a different screen size, but it is still more work, no doubt about that.
8. What about PC/Browser porting, are you noticing or see the need/demand or value in doing that, and if so are you familiar with the effort in that case let’s say after a mobile version has been completed?
I do see this happen from time to time, though not with a lot of board game conversions. My concern would be monetization, since the folks who play web-based games are used to getting their games for free, and you have to have a very large active userbase (in the hundreds of thousands, from what I understand, although I’m no expert) to make money with advertising alone.
9. How many people do you believe is needed to convert and maintain a board game digital conversion, and what roles?
For a “full featured” conversion, I see the following needs:
– Artist/graphic designer
– Sound Effects person and Musician (often can be the same person)
– Some kind of project manager or person making feature decisions
– A person (or team!) in charge of marketing
I have worked on a lots of projects where there were a couple of developers who split duties. This includes several apps with Tysen Streib, who would expertly craft the AI and game logic, while I handled all the rest of the application, including ultimately integration of his code into the project.
Another optional role I’ve found myself filling briefly at the start of smaller projects is that of UX designer. It is always nice to have a blueprint to work from, and good wireframes can really speed up development as well as help keep your team on the same page if there are multiple developers.
The mix and makeup of all of these roles will be different on every team, no doubt. There are certainly some indie developers who tackle all of these tasks for every project! I’ve found that keeping scope small is always a good thing, work toward manageable milestones, and you’re less likely to be surprised by how long something takes you to complete.
Below you can find my slides from the presentation I gave at last night’s IGDA Twin Cities meeting.
I think the presentation went okay, but I should have realized ahead of time how boring a topic spreadsheets can be. I saved the demos for the end of the talk, and by the time I got to them, I was really feeling the boredom radiating from all corners of the room. Anyway, I hope these slides are helpful to someone.
While preparing for the talk, I came across an interesting article about the history (origin) of spreadsheets called A Spreadsheet Way of Knowledge.
Yesterday, my friend Lloyd linked me to Chessrunner (reddit thread), a web-based, chess-inspired endless runner in which you start with only a king, which you have to move forward on an endless chessboard. As you move, you can capture enemy pieces and make them your own. It’s an inspired idea, and one that apparently only took developer/creator Juha Kiili a weekend to implement (in Unity). There has been plenty of positive commentary on Reddit, and hopefully he’ll flush out the idea and (ideally, IMO), bring it to iOS.
Chessrunner’s “timer” mechanic (making it an action puzzle game) is pretty cool in that the gameboard is both expanded (from the top) and shrunk (at the bottom) one square at a time. The opposing colored pieces take one move after every one of your moves. They will ALWAYS capture your king if you give them opportunity, but they are not smart enough to trap you (yet), so surviving is really all about seeing all the attack lines. And that’s why this game really does a good job (IMO) of feeling like something you do while playing chess.
Have I been remiss?
I’ve written before about various chess-inspired puzzle games. (And of course I hope anybody reading this already knows about ActionChess, which was my first app in the app store.) But I realized when I started writing about Chessrunner that there was no way to find those game mentions! (Now there is a Puzzle Chess Games category.) And furthermore, there are several other chess puzzle type games that I’ve played over the last few years that have not (yet) been mentioned here. So I wrote up some mini-reviews:
Pawn’d (available for $1 on iOS, or in Lite form for free) is a chess & match-3 matchup. I had a very similar design idea for this style of game as a game mode for ActionChess, but I never really put any time into it.
Pawn’d takes the concept in a lot of different directions at once, and looks great while doing it. There are three main game modes, each designed around how the game ends, and each with two more difficult variations called “Blitz” and “Master”. Additionally, there are two introductory modes that have neither variation, one called “Practice’d” (play to a certain # of matches), and another called “Clock’d” (play to a time limit). Each of the modes has its own leaderboards, making something like 22 leaderboards in the whole app. There are also a ton of achievements. Basically, if you like this concept, you can keep playing it for a LONG time without running out of things to do.
This game, possibly more than any of the other ones listed here, is decidedly worth playing, and I’ll cop to getting sucked back into it while writing this.
Chess Tower Defense
I’m fond of telling the story about how, when asked what he thought of ActionChess, my (then 8-year old) nephew Jake replied with “Could you make it a tower defense game?” I LOL’d. Well I think it was less than a year later that you could play Chess Tower Defense over on Kongregate.
It’s graphic design is quite spartan, but the concept is interesting nonetheless. You must survive waves of attacking “things”. (They are not pieces really.) The things don’t attack your pieces, but instead march methodically toward you (downward), passing right through your pawns. Your pawns (and other pieces) can attack them, in the standard directions, and if they don’t, each thing will remove one of your hearts when it gets past your back row. Between waves, you can reposition your pieces, and buy new ones. It’s an interesting concept, and one also worth spending some time playing, if only just to wrap your head around it, I think.
Knight Defense (for iPhone or iPad) appeared in the app store about another year or so later. As good as Knight Defense looks, it’s definitely less on the chess strategy end of the spectrum, and closer to the tower defense end. It’s all real-time, so there is no turn based aspect, and you can move your pieces all over the board at will during the game. In each of the squares your pieces could attack in a real game of chess, those pieces may damage enemy pieces. Like other tower defense games, Knight Defense is played in waves, during which enemies will appear at the top of the screen and move toward your king piece, wherever he might be on the gameboard. Though they are shaped like chess pieces, the enemies don’t move or attack like chess pieces, there just run into whichever of your pieces are in front of them, and “damage” them, eventually destroying them. Your pieces can be upgraded to do more damage at once, and to heal them once they’ve themselves been damaged. This is worth playing for chess fans, (especially so for those of you who already enjoy Tower Defense), but it’s not necessarily at the top of my list.
Cheesy Chess (free with ads for iOS) is not turn-based or action-puzzle at all. It’s more of a static puzzle game where the goal of each level is to get your king to the other side of a small chess board filled with pieces but for one square. In as much of the game as I’ve seen, there were no captures, only moving pieces around in a very cramped and crowded grid. This felt to me like a chess-themed version of Rush Hour (a sliding block game). Admittedly, I’ve played the least of this game. The mouse chess theme is super cute though, and it’s very well-made.
I was musing on game design this morning, and came to a conclusion that I already knew both intellectually and intuitively, but one that I’m not sure I’ve articulated to myself previously: Game design is a creative endeavor. (With all the subjectivity and painful process woes that plague all creative endeavors.)
I’ve always just made games that I myself wanted to play, avoiding the entire camp of game design that suggests your players should be influencing your design. That may sound like an arrogant position to take, but at first it was borne more out of laziness and ignorance than anything else. Until I attended my first GDC in 2012, I didn’t even really realize there were people whose job was game design, and I certainly didn’t realize there were books written on it or — more importantly — people thinking about it academically. It was that revelation, more than any other, that has kept me going back to GDC; I find immense value in immersing myself in game design topics opinions and thinking for a week, not to mention all the networking opportunities.
But anyway, aren’t I also a player? In my opinion, I’m a player whose wants and desires are seriously under-served. (That means my games are probably for a small segment of the market, and I’ve made peace with that. I’m not looking for commercial success… if it finds me, awesome.) I’m not going to cave to the pressure to make games for someone else. Because essentially I feel like that’s compromise. And I think compromise kills art. My vision is no more important than anyone else’s, but it’s also just as important as everyone else’s. And hey, I’m the one making it.
So is this all one big excuse for not accepting constructive feedback? Partly, yes. These thoughts all come in the wake of showing off a new (-ish) board game last night at a local game designer meetup. I haven’t talked about this game publicly before, and this whiny blog post is probably not the place to start, but it was not received well. (In spite of many — at least 10 — fairly successful playtests previously.) Mostly, the feedback last night consisted of ways to change the game entirely, ways to take it in some other direction. Essentially, the playtesters (game designers, but for one) didn’t enjoy the game, and spent a good fifteen minutes after their play trying to brainstorm ways to “fix” the design. Almost all the player suggestions last night involved tearing up the design and making something new out of the pieces. This is something I’ve already done with this particular design at least three, maybe four times so far, and I’m actually very happy with where it’s at right now, so that option is not really on the table.
It’s hard not to take this kind of feedback personally. (Made more difficult by at least one of the designers in question having a lot of problems keeping his feedback constructive.) The whole experience really threw me for a loop, and I spent this morning struggling against an impulse to just put the game away and not think about it for a while.
Perhaps I can salvage this piece by adding a few bullet points about giving constructive game design feedback.
- Be thoughtful — Generally speaking, think before you speak. As best you can, it’s a good idea to form complete thoughts before you speak them. If you’re offering up specific “fixes” for a perceived issue, make sure you articulate that issue before you offer up your solutions. Think about why something is a problem before you say it’s a problem. General “impressions” are generally not that useful, better to back them up with a “why” or a “how”.
- Be courteous — Nothing invalidates your feedback quicker (or makes it harder to hear) than an insulting statement. Make sure your feedback is about the game, and cannot be construed as a criticism of the designer. In general, if it’s not nice, try hard to think of a way to say it nicer.
- Context is everything — Ideally the game designer has asked for specific feedback points, but even if not, it’s probably worth asking some probing questions before getting into a torrent of specific criticisms. There are several “levels” at which you can talk about any game. Is the designer looking for feedback about the overall systems used in the game, or are they looking for feedback about specific components or balance issues?
- Be specific — “I did not like this.” is not, by itself, useful feedback. Generally speaking, the more detailed you can be about why you didn’t (or did!) like something the better. If the designer was paying attention, they probably already know whether you were enjoying the experience.
- Stay on topic — I’ve found that “after playtest discussion” can easily veer into a speculative realm of what-ifs and imaginary games that could exist. This is especially true with game designers. Try not to be the one leading the discussion away from the current game.
I’m backing up my iPhone in prep for a new device, and one of the things I did was spend ten minutes taking screenshots of every folder, just in case I need to restore things “manually” later. (Actually, I may decide to start “from scratch” on this new device, and I’ll use these images as reference if I need them.)
Anyway, nobody probably cares about my home screen, but I thought these screenshots of my “TetrisLike” folder were pretty cool. Enjoy!
I’ve been meaning to write a post for a while now with pull quotes from the two big Catchup reviews. (It’s kind of a shame I haven’t even mentioned them yet on here.)
But before I get to those, Catchup is free in the App Store today. I’m hoping for a big influx of new players who might then tell their friends about how great it is, and maybe some of those folks will purchase the app tomorrow, when it’s back to $2.99. So if you haven’t already, go download it now! (But if you’re reading this, my guess is you’ve already got it, so thanks for that.)
Anyway, Catchup’s first big review came from Pocket Tactics on the 14th of August, exactly a week after its release. It’s an absolutely stellar review, giving the game 5 out of 5 stars, and I’ll just let some of the quotes speak for themselves:
“Catchup is as elegant as a game can reasonably be, presented in a marvelously user-friendly way.”
“…it’s packed with all kinds of options, some of which are unprecedented in my experience.”
In another quote that I found quite amusing, the author, Kelsey Rinella, also manages to call Nick (the game’s designer) a yahoo, while still complimenting him:
“I am not amused that some yahoo can waltz in and make what I do look easy and sound like a caring, brilliant guy at the same time.”
Catchup’s second big review was from the iOS Game review behemoth Touch Arcade. It absolutely floored me to get a full review on the front page of Touch Arcade, and they gave it 4.5 out of 5 stars to boot. Here are a couple of quotes from author Shaun Musgrave’s review:
“If you’re even a little bit into strategy games, you need to get some Catchup all over your mobile device.”
“There are also a number of achievements set up through Game Center, some of them very cleverly devised to force you to play outside of your comfort zone. That’s my favorite type of achievement.”
The Touch Arcade review didn’t appear until August 22nd, slightly more than a week after the Pocket Tactics review. Another week after that, Catchup was back on Pocket Tactics (on the 29th) for their “Games of the month” for August. Here is another great quote from that:
“The greater the ratio of fidelity to a complex system to rules overhead, the better I tend to like a design. Catchup doesn’t even attempt to satisfy my strongest gaming craving, and yet I feel excitement every time I see the badge saying it’s my turn in a game. It’s like rediscovering excellent vanilla ice cream after years of trying all sorts of tarted-up frozen confections. It’s such pure gaming goodness, without dissonance or unpleasantness of any kind.”
Obviously, I’ve added some of the above to the app’s app store description. (Let me know if you have any opinions about the ones I chose!)
I will probably write another post at some point about stats, including download numbers, and what kind of impact these reviews had on those. But anecdotally, the Pocket Tactics review got us slightly more downloads on the day of the review, (I’m guessing because their readers are closer to our core demographic), but the TA review had a longer impact, for more days. Possibly we fell off the front page of PT faster.
Here are the release notes for Catchup version 1.0.1, which was approved and went live in the App Store sometime late last Saturday night (September 6th).
* added a setting to let you change who goes first in a vs AI game
* minor changes to text strings, mostly consistent capitalization of AI and Catchup (thanks go out to Martijn Althuizen for help with this work!)
* minor changes to Dutch localization
* relatively significant changes to the german translation
* fix for the “next game” button flashing after you take an async turn
* close the GameCenter UI if the app goes into the background
* misc additional minor bug fixes
Thanks again for playing Catchup!
After getting two emails almost simultaneously on Sunday morning, both letting me know their game over screens were reporting the wrong winner, I pre-pended the following message to the 1.0.1 release notes, and sat down to find the problem:
WARNING: this update actually causes inaccurate end-game win reporting on the game over screen. (The stats and leaderboard submission should still be correct.) This will be fixed in the next update.
And here are the release notes for version 1.0.2 that I submitted to apple on Sunday afternoon, (September 7th):
* fixed bug with incorrect winner name on game over screen (Sorry!)
* corrected title bar string on game screen
All of this illustrates one of the frustratingly difficult aspects of solo application development — regression testing. Or, for anyone unfamiliar with the term, testing existing functionality after a code change “to make sure everything still works”. Basically, it was my work on the new feature (letting the user pick whether or not they go first in an AI game) that broke the game over screen reporting. As bugs go, it’s fairly minor. (I don’t mean to belittle the frustration if you encounter it!) Nothing is crashing, and the win statistics are reported correctly, both to Game Center and the internal stats page. I definitely tested quite thoroughly playing against the AI before submitting 1.0.1, but I just plain didn’t think to check local multiplayer, and might have played through an async game, but I’m not 100% sure. Anyway, I clearly didn’t encounter the bug. (Or didn’t notice if I did.) The specifics are kinda funny: the wrong player name is reported as winning the game in async, but only to one of the players. (Which player depends on who actually won the game.) In the local multiplayer scenario, it basically always reported player 1 as winning.
I have plenty more features to work on for the next build I submit, but figured I should get this fix out there ASAP.
So today an interview I did over at tech.mn went live. It’s part of a Nerdery-sponsored “know this nerd” series, so I’ll forgive them for using the term “nerd” instead of “geek” (which I generally prefer).
In case that isn’t enough biographical writing for you, I have also been meaning to post some of my responses to a game-related user-group application I filled out about a month ago. I’m not going to go into details about what the application was for, but let it suffice to say that I spent a lot of time on the application, but ultimately wasn’t accepted. So I feel the need to post a mashup of my answers here to salvage something from the experience.
The first question from the application, and the spark for most of what was written below, was as follows: Describe your work as a game developer. Why did you start developing and what do you hope to do as a developer in the future?
My first game designs were all variations on board games that I was already playing. I played a lot of chess as a kid, and have always been interested in chess variants. I re-worked this paragraph about six times, remembering earlier and earlier game designs, and just now realized that I can probably pinpoint my very first game variant, and it was actually published! One of my grade-school friends and I played a lot of an abstract strategy game called Terrace. Terrace had a newsletter called Terrace Times that you could write-in and subscribe to. The newsletter published variants written by their readers, and you guessed it, my friend and I wrote in with a few of ours. If I remember correctly, we wrote up about four or five designs, and they published two of them. [I’m 90% sure that I still have the issue in storage somewhere! TODO: dig those up and post them here!]
Later, when we were both just about done with high school, that same friend and I got really into playing an early first-person shooter called Marathon, and we made maps for it that other people actually downloaded over the internet. (This was about 1994 or so, so that meant over dialup!)
Fast forward to 2006, I had been working as a backend web programmer for two or three years, and I realized that making my own video game was actually an achievable goal! It took me over six months working nights and weekends, but my first video game was called Go Tetris. It was the first and last thing I ever wrote in Flash, and is still playable online at go-tetris.com.
I’ve always had a ton of game ideas, and when my wife bought me an iPhone as a wedding gift (giving it to me early so I could take it on our honeymoon!), I knew from the second I started playing games on it that I wanted to make some. The SDK was announced the following year, and even though I’d never worked in a compiled language before, I started writing a game for it right away. That game took about half the time to make that it took me to make Go Tetris, and it came out in 2008, was called Action Chess, and like Go Tetris, combined two of my favorite game genres, chess variants, and action puzzle games. It made a meager $1000 in the App Store, but that was the first $1000 I ever earned in game development. [EDIT: I just remembered this is not quite true. I earned about $6 in ad revenue after Go Tetris was linked-to from the US Go Association’s website for a week.] Learning iOS development was a good career move, and about two years ago I was able to quit my day job to do iOS game development “full time” (one of my first contracts as a freelancer was working on a little abstract strategy game for Tasty Minstrel Games called For the Win).
In March of this year I was privileged to speak at Game Developer Conference in San Francisco about “Usability Lessons from Mobile Board Game Conversions”.
I keep a design journal where I write down all my game ideas, and I usually add one every week or two. I’d say they run about 40% physical (board) games, and 60% video games. On rare occasions I get really enamored with one of my ideas, and have to start working on it right away. I’ve got several prototypes like this that are pretty near completion. It’s standard practice for me to “sit on” a game that I feel is pretty close to finished because I don’t have enough time to give it the polish I think it deserves. Anyway, the point is that I can’t imagine NOT working on games. I’d definitely be doing it even if it hadn’t worked out for me to turn that into a career.
Here are a list of games I’ve worked on that were published in some way: http://chesstris.com/about/#bibliography
I’ll fully admit that most of my games are unlikely to be commercially successful. At any given time, I’m probably working on two or three games at once, and juggling a freelance project to pay the bills. (Sometimes those are games!) My fondest hope is that one of my projects does give me the kind of return that I can stop the freelance work entirely, and continue to make the games I most want to play, without compromise or constraint.
I had the pleasure of attending United Geeks of Gaming’s Game Designer Sessions event last night, and play testing the latest (third) iteration of a game whose working title has always been “workers”. I realized after a couple of games that the rules were a little “fuzzy”, seeing as how they’ve never been formally written down, and decided that some kind of documentation was in order… Hence this blog post. (Half rules formalization, half designer diary.)
Workers was initially conceived as a “born digital” board game with the central mechanic that there are a variable number of “resource pools” in the game, and every round each pool’s count of available resources is incremented by one. The name stems from it being a very light “worker placement” game, with the initial version allowing for only one action taken (worker placed) per turn. I’ll get into the various specific actions available when I go into details about each version of the game below.
The only other shared mechanic for all the versions of the game has been the turn / round mechanism. Each round a starting player is indicated, every player takes an action (or two) for their turn in clockwise order, and then the starting player indicator is passed to the next player (also in clockwise order).
The initial version of this game remains the only one for which there is a (completed) digital prototype. I completed a very quick and dirty app to “prove out” the game mechanics in an evening or two of work and subsequently sent it to some of my TestFlight users for feedback and testing. The prototype was “successful” in that it convinced me more work was needed, but ultimately had quite a few design flaws, which I’ll detail in a minute.
As you may or may not be able to understand from the screenshot, there are 5 available pools of resource (yes, a hard-coded number, even though I knew from the beginning that I wanted it to be variable), as well as hard-coded two-players (with their resource counts on either side of the screen). In the center are all the available actions, and under the main resource pools (which double as buttons for taking the corresponding collection actions) are action buttons for selling each combination of two resource. This version has a selling mechanic whereby you can sell pairs of different-colored resources for the value shown on each pair. Between rounds, not only do the number of resources in each “pool” increment, but the point values for selling each combination are also incremented every round. When a player took a selling action they automatically sold all possible combinations of the two resources for the point value shown. (So if they had 3 green and 2 blue, and took the green/blue selling action when it was worth 5 points, the would end up with 10 points and 1 remaining green resource.) After a sale action, the value for that combination is reset to zero.
Available actions (one per turn):
- collect all of one resource pool
- sell a combination of resources
The game lasted a set number of rounds. (15 here, although I experimented with different values.)
Reasons this version is a failure:
- Replayability: essentially this game played the same no matter how many times you played it. This was pretty boring and led to an…
- Optimal strategy: it turns out, the best way to play this game is to keep collecting resources, whatever pool has the most, until the last two or three rounds of the game, then sell for the highest possible point combination. Boring and stupid. I could possibly mitigate this by capping either point values for selling, or total number of resources, either per player or per pool. Ultimately I never implemented either, and instead moved on to working on…
The next version of the game was conceived to “solve” some of the design problems in the fist game by adding variability (via a game board), as well as removing the complex in-game scoring (the entire “selling” mechanic). I don’t remember whether removing in-game scoring was a goal in and of itself, or whether it was primarily meant to facilitate paper prototyping. I took this version to my first Game Designer Sessions meetup, (quite a number of months ago). The game was played at that time with decks of cards with different colored backs for each resource pool.
The “game board” consists of an empty grid at the beginning of the game. Grid dimensions (as well as “number of resource pools”, “starting player resources”, and “starting resources in each pool”) are meant to be variable for each game.
Scores weren’t known/calculated until the end of the game, when all the spots in the grid were filled with resources. I played with a couple of formulas for scoring (see below), but in general, I wanted the more groups and the larger the groups to have higher point values at the end.
Available actions (again, choose one):
- take a pool of resources
- play a single resource from your resources into the game board
- One issue became evident right away, and that was lack of incentive to be the player who plays onto the game grid. After one play test, the player who sat back and hoarded resources was the clear victor. If I remember right, I believe we played a second game after the first and changed the “play on the board” action to take the resource from the pool rather than from your hand. Additionally, you got to take one resource from the pool into your hand as part of that action. I came up with another possible solution on the fly last night.
The version I brought last night had basically one new mechanic: Every player started with a “x2″ (times two) card face-up in front of them. There were two ways you could use this card, but when you did, you turned it face-down, and those actions were no longer available to you. I also play tested this version of the game with colored cubes for resources, which I felt was more visible (at a glance) than had been the case with using decks of cards, and had the added benefit of keeping the game board size considerably smaller. (I drew the game board out as well as “spots” for 4 resource pools on a single sheet of graph paper.)
- take all of one pool of resources
- place a cube from your resources onto the game board
- use your “x2″ action to increase the subsequent pool increment by one additional cube per turn (this could stack if multiple players did it)
- use your “x2″ action to place a cube on top of a cube already on the game grid (increasing the size of that group by one without taking up a spot on the board)
We played a relatively quick game with 4 players, 4 resources, and a 4×4 grid, but less than halfway into the game I remembered the problem discovered in the playtesting of Workers II. I let the game play out, but suggested we play another game where you take two actions per turn, but your second action has to be a placement on the game board. One player left, so we played 3-players, 4-resources, on a 4×4 grid, but everyone started with one of each resource. I feel like this went pretty well, but still “needed something”.
Possible scoring mechanisms for multiple variable-sized groups:
- group-size times group-size added together
- group size added together times number of groups
- Fibonacci values for each group totaled, times number of groups
I have lots of ideas for Workers IV. I’ll post back here when I get a chance to try any of them out!
Catchup version 0.9.1 hit the app store earlier this week. Here are the notes that shipped with that version:
* russian localization
* german localization
* settings screen: delete local saved game when changing manual AI level
* fixed a bug with tutorial step 3 not getting displayed
* made popover text scrollable if necessary
* translated a few more strings for all localizations
new in 0.8.x
* traditional chinese localization
* added HSB sliders to color screen, cleaned up UI
* fixed crash in iOS 6
I have been learning a lot with this release, namely about how much extra work localization entails, but Game Center async code stuff also. In fixing a bug at the last minute related to determining whether a Game Center game was still valid (specifically, it goes through and checks all the players to make sure their “match outcome” isn’t set), I introduced another bug, this one making Game Center invitations completely fail, as the match outcome is in an “unknown” state for those, since the invited player hasn’t accepted it yet at that point. Apologies to all the folks who ran into this!
A few minutes ago I submitted build v.0.9.3 to fix this issue. The complete release notes are as follows:
This build fixes a really horrible bug with Game Center “invite” games ending as soon as they began. My apologies!!!
Thank you very much for playing Catchup!
* fixed “invite” games ending as soon as they are created
* number of “your turn” games is sometimes incorrect, (I need to reset all helper arrays when the UI opens)
* crashing bug when you delete an async game in which it is your turn, start a new one, then click next game after taking your turn (need to re-create all the arrays in the async helper)
* swapped positions of share and close on the game over screen.
* added a new “use english instead of XXX” button for non-english localizations
* lots of fixes for Dutch translation text, some english ones
* credit for Dutch translator in English localization
* dutch (nl) translation
* minor change to make one of the tutorial steps a bit more consistently worded
I did use the official form to request an “expedited review”. I have had good results with that in the past, but also know someone who had it “not work” recently, so we shall see.