The Problem
Ideally, if we can afford it, we should all be supporting the development of the games we play. But if you’re anything like me, you’ve gotten a little sick of the predictable cycle of
The "Banking" Method
So, let’s do an example. Let’s say I want to support Dr. Armana, Sexual Therapist. A fantastic game. If you haven’t played it, go do so. Some of the best writing ever. I decide that I would support this game at a rate of $5/month, and I would expect an update every 4 months. After 8 months, I’d kind of give up. So our parameters are set.
So RomanHume releases an update, and the clock starts. I put $5 away. I do the same thing a month from now. If he releases an update in two months (that’s too quick, I know), I donate $10, and the clock starts over. If he releases an update in 4 months, I donate $20. When the 5th month rolls around, I just hang on to the money. Not adding anymore. If he exceed 8 months, I spend the $20 on a Pizza or something.
When I donate, I include a donation message that says
Thanks for the update! I’ll be back to donate more when you release your next update!
What Does This Do?
Well, by not donating until an update is released, the developer is motivated to release. Because they know that they’re not getting paid until they do, and they’re potentially getting paid a lot when they do so.
By not letting the “bank” grow beyond (step 1*step 2) the developer is motivated to keep a regular schedule. The longer he goes between quality updates, the more he starts to lose money.
By including step 4, you money is never completely wasted. It will still suck if you donate to a project that just gets dropped completely; but at least you’re not in a situation where you spend $50-$100 without ever getting an update.
Why It's Admittedly Not a Perfect System
When a developer only gets paid on release day, it motivates them to push out updates, even if that means rushing something. Obviously that's not ideal.
That said, most of these games are listed as being in "beta" stages. That's supposed to mean that it's in a testing phase. It's not that hard to put up update/patch/change logs including a "known issues" section. They could even release simple bug-fix patches between full updates. Honestly, I think it would foster a stronger sense of trust between developer and user, if it was more obvious that progress was being made.
Ideally, if we can afford it, we should all be supporting the development of the games we play. But if you’re anything like me, you’ve gotten a little sick of the predictable cycle of
- Developer begins new game. It shows lots of promise, and he’s excited about working on it.
- You donate and the updates come regularly for six months
- The updates slow to a crawl
- Th developer announces “he’s taking a break for ‘health reasons’” or just disappears all together.
The "Banking" Method
- Establish how much you think is a fair monthly rate to support a developer
- Establish what you think is a reasonable expectation for delivery of updates. This can be a static time period, but I suggest varying it depending on the complexity of the game.
- Establish how long a developer can go between updates before you think “OK, either this guy is gone or this project is just a scam.”
- Every month, set aside the amount you decided in step 1, up to the amount of time established in step 2
- When the developer updates, donate the money you set aside, and let them know you’ll donate again the next time they release an update.
- If the developer exceeds the length established in step 3, just take the money back. Go buy yourself something nice. If you want, you can give them another chance by re-starting the clock when they release next.
So, let’s do an example. Let’s say I want to support Dr. Armana, Sexual Therapist. A fantastic game. If you haven’t played it, go do so. Some of the best writing ever. I decide that I would support this game at a rate of $5/month, and I would expect an update every 4 months. After 8 months, I’d kind of give up. So our parameters are set.
So RomanHume releases an update, and the clock starts. I put $5 away. I do the same thing a month from now. If he releases an update in two months (that’s too quick, I know), I donate $10, and the clock starts over. If he releases an update in 4 months, I donate $20. When the 5th month rolls around, I just hang on to the money. Not adding anymore. If he exceed 8 months, I spend the $20 on a Pizza or something.
When I donate, I include a donation message that says
Thanks for the update! I’ll be back to donate more when you release your next update!
What Does This Do?
Well, by not donating until an update is released, the developer is motivated to release. Because they know that they’re not getting paid until they do, and they’re potentially getting paid a lot when they do so.
By not letting the “bank” grow beyond (step 1*step 2) the developer is motivated to keep a regular schedule. The longer he goes between quality updates, the more he starts to lose money.
By including step 4, you money is never completely wasted. It will still suck if you donate to a project that just gets dropped completely; but at least you’re not in a situation where you spend $50-$100 without ever getting an update.
Why It's Admittedly Not a Perfect System
When a developer only gets paid on release day, it motivates them to push out updates, even if that means rushing something. Obviously that's not ideal.
That said, most of these games are listed as being in "beta" stages. That's supposed to mean that it's in a testing phase. It's not that hard to put up update/patch/change logs including a "known issues" section. They could even release simple bug-fix patches between full updates. Honestly, I think it would foster a stronger sense of trust between developer and user, if it was more obvious that progress was being made.
Last edited: