Right now there's a huge sale going on at Steam, with many games (including AI War) being on large discount. In a recent comment thread over at Rock, Paper Shotgun, some people were wondering how these sorts of sales affect the profits made by indie developers. I commented there, but thought I'd also turn this into a blog post.
Like Jonathan Blow, I can also confirm that the percentage cut is the same with these sorts of deals, with Steam and elsewhere. Digital distributors take a percentage of net profits, so discounts are taken off before that. So, in the case of Steam, that would meant that then the developer/publisher would make less on discounted sales, but so does Steam. However, the loss on any individual sale is generally greatly offset by the huge influx of sales in general that these sort of discounts bring.
With any digital distributor, having a sale on a given game is going to increase its sales volume 10x or more in my experience with AI War. Sometimes as much as 50x, depending on the day. For AI War, one of these sales can make us several month's worth of income from a distributor in a single week. That's why you see this sort of thing so commonly, and why it is becoming even more commonplace. I think that these sorts of sales tend to incite people to buy who might otherwise not, so it's not even really seeming to cut into longer-term sales at all. On the contrary, on the wake of any given sale, I tend to see a ripple effect of higher sales volume even for a week or so after the game returns to full price.
I assume that's people trying the demo while it's on sale, then not buying it in time, then deciding they like it well enough to buy it at full price. Or something along those lines, anyway -- those discounts are essentially marketing costs, is one way you could look at it, given the increase in visibility these sorts of sales bring.
Anyway, in my opinion there's no reason you should feel guilty at all for partaking of buying a game on discount, you're still helping the developer/publisher. If you really want the max money to go to them, you can always wait and buy it at full price, I guess, but I'm always happy to see new customers no matter when they buy it; if I wasn't cool with the discounted price, I wouldn't sell it at that discount, you know?
Wednesday, December 23, 2009
Thursday, December 10, 2009
Encapsulated Businesses For Indie Development
Justin Vincent recently wrote a blog post about what he calls the Venture Matrix, which is basically a way to create a huge company out of a lot of little companies-- or, alternatively/additionally to make it easier to launch successful startup companies. It's a long article, and it starts out with a lot of semi-tangential discussion about centralized necessities, but if you look down at the heading The Birth of Companies and on, there are some really novel ideas there; or rather, he's cleverly applied some best practices from good programming to real world business, and that in itself is quite novel.
The article is well worth a read, and it flows well with a lot of things I have been thinking about recently. I've always worked for small businesses, but often I've had very large businesses as key clients, and so I've had an opportunity to see it from both ends. I much prefer being in a small company because of the autonomy and room for creativity that provides (and the increased possibility of returns if the business does very well), but there's a key aspect often missing from small companies: security. That in itself can be a good thing, because it can prompt the business to be proactive where larger companies might be lethargic. But...
The Inevitable Challenge Of Traditional Small Businesses
On the other hand, lack of funding can lead to lack of certain expertises among available staff. In the past I've been in a company where we had excellent programming staff and support staff, but sales staff that couldn't sell the product, and a very novice marketing staff. That business actually did okay based on word of mouth alone, because clients liked our product and told other clients, but how much better might things have gone if we'd had really excellent sales and marketing staff to match our excellent product?
Or, to cite another example, I once did some contract work for a small company that had developed the world's smallest (at the time) cell phone motherboard. It was about half the size of anything else on the market, back when cell phones were much larger; the possibility of such a motherboard was staggering, because it would have allowed for phones the size of today's devices about 3 years before those actually hit stores. Unfortunately, the company was completely unsuccessful in selling their work because they didn't have the needed expertise on the business development end of things.
I love Justin Vincent's talk about encapsulation in his article, because that's exactly what is needed for companies like these. A lot of startups are product-focused, and they know how to make a product that is really unique and useful inside some niche. But unless they just happen to be lucky enough to have staff who are really ace at sales, marketing, and business development, that great idea is likely to languish in obscurity or at least not reach its full potential.
AI War, for example, has done extremely well for an indie game and is still seeing a significantly growing playerbase every month, but marketing has always been a huge challenge for us. And none of the success we have seen would have been possible without all our digital distribution partners, and our upcoming retail partners. It's still quite a challenge to launch a product even in the digital marketplace, and I had to essentially work two jobs for years and luck into the right partnerships in order to make it happen.
My Ideal Approach For Indie Development
I have been thinking for the last few months about how the ideal setup for indie development would work. In other words, how to maximize output from indie developers, maximize revenue for them and their partners, and in general serve the gaming consumers the best by getting them the widest possible variety of truly quality titles at reasonable prices. Here's the ecosystem I imagine:
Indie Development Company: This obviously already exists, but currently the indie developer has to do most everything -- game development, support, funding themselves, marketing, business development, and so on. In my imagined environment, the indie development company would mainly be responsible for game development and technical support/patches (basically what AAA game development companies are responsible for).
Digital and Retail Distributors: These companies also clearly already exist, and I think that they by and large serve their function admirably. The challenge for most indie developers, however, is actually getting the notice of these distributors. The challenge for these distributors is that they get so many totally crap submissions that it is hard to evaluate what is good and what is not. This is very similar to the book publishing industry, incidentally, which leads us to...
Indie Game Agents: These currently do not exist, not in the sense of the book publishing world. Certain well-connected individuals can act as agents, and in fact there are regional sales agents for retail, but they don't act as quite the career partner and liaison that you see with book author agents. More to the point, most indie developers don't even know these agents exist, and/or don't have any way to contact them. It basically requires having the right network connections, and a track record of existing success in the digital market. If you're unheard-of, then forget about it at present. So, the theoretical agents would be:
1) Available for submissions from all indies (acting as talent scouts), as with book publishing agents.
2) In exchange for an ongoing commission (10% to 15% of what the indie developer earns) but no upfront fees, will handle coordination of marketing, sales, business development, and so forth in both the digital and retail spaces. They would basically be the indie developer's business guide, advocate to business associates, and so on. Again, like book publishing agents.
3) These agents would be known and trusted by the distributors based on their past successes in finding diamonds in the rough that went on to be successful, and so if your game were to catch the eye of an agent that would be a sure-in to digital distribution at the least. These agents would be the valuable filters to the distribution pipeline, and the net effect in the short term would be to get more quality titles through. Fact is, a lot of indie developers themselves are not persistent enough or good enough at describing their work to catch the interest of distributors who have so much else to do. Right now, to get even digital distribution deals, you have to catch someone's eye at just the right time.
Advertising/Marketing Agencies: These certainly exist, but these are vendors, not partners, in almost every case. They perform a service for a fee for anyone who can pay the fee, and then their work is done. They have no stake in the success of the product (they don't even have to like the product, let alone fully understand it), and they are inaccessible to anyone who can't afford the upfront costs. In the ideal model for the indie market, these agencies would be full partners on an individual game's public image, coordinated by the game agent.
In other words, they would handle the details of advertising and marketing, as overseen by the game agent (who would also be responsible for selecting a good advertising/marketing agency), and they would not see any return on their work except a percentage of sales revenue. This could be anywhere from 5% to 10% of what the game makes in total. This is akin to having a talented in-house advertising/marketing staff, since they have a vested interest in making the products they represent quantifiably more successful.
Investment Partners: The last big problem for indies is funding. Creating a game takes quite a long while to do, and this requires money for staff salaries, contractor pay, health insurance, licensing of development tools, possibly office space (for those that aren't virtual offices), and so on. Really polished indie games are likely to cost anywhere from $200,000.00 USD to $400,000.00 USD (or more) if the staff isn't being paid a pittance upfront in hopes of later return. The idea of the investment partners is that they would be contacted by the game agent, or directly by the indie developer in a few cases, and they would provide upfront funding for projects that can demonstrate their worth.
That doesn't necessarily mean a detailed and rigid design document, given that part of the strength of an indie developer is their ability to innovate and use iterative design techniques. Rather, it's a matter of proving out the team and their ability to execute and refine solid ideas. That could be based on past products (spare-time, second-job type affairs), or based on a prototype. Some of the products an investment partner picks up will flop, as is the case with any such market, but the idea is that the investment partner is structured in such a way that even if 9 out of 10 indie projects they take on do not make a positive return, they as a company still see a positive return based on the 1 out of 10 that is a much larger success.
With the advertising/marketing partners and game agents in place, the likelihood of success only goes up. Additionally, for the savvy investment partner that invests only in indie developers with a history of past success (whether that means commercially-speaking, or in terms of potentially marketable ideas brought to fruition, or whatever the criteria is), the return is likely to be much higher. I could see several tiers of investment partners forming, with higher-percentage-taking investors that might prefer higher-risk investments, and lower-percentage-taking investors that only the "premium" indie developers with mega-hits under their belts could have access to. Arcen would likely be slotted with an investment partner somewhere in the middle of that spectrum, for instance.
What Would This Sort Of Indie Development Approach Really Change?
It would provide a way for indie developers to start small and stay small, which has many advantages as noted in Justin Vincent's article. I am dismayed that so many indie developers basically create a pet project as a way to then launch into the larger industry. Indie development shouldn't just be about launching yourself into AAA development. I started indie, and I want to finish indie, if at all possible.
What does indie really mean, anyway? It does mean smaller projects (not multi-million dollars), but also projects with a lot more creativity -- and therefore risk. It means having freedom to experiment, and less structure to the start of the development process. There is less known up front, and more discovered as you go. With expert developers, you'll get products that would never come about any other way. If you take Jonathan Blow, give him some money and some time, then stay out of his way, you can trust he'll come out with something amazing that he'd never create if he was working at someplace like EA.
Is it possible to be an expert indie developer? You bet. This subject probably deserves a post all of its own, but for now let it suffice to say that there are examples all around the industry. Even just purely from an ROI standpoint for investors and partners, I think that's something worthwhile to cultivate in a more structured way from the business side of things (let alone all of the larger creative benefits to the industry as a whole). The goal is to give the indie development business more structure and security, have encapsulated partners who are better at handling the things that your average indie developer is poor at, and then just let the indie developers do their work.
The investors and partners will of course want to keep an eye on the developers, especially the not-yet-fully-proven ones, to make sure they don't go off on a crazy tangent -- but otherwise they need to just trust that the developers are doing what they need to do to make an innovative product that people will want to buy. If a developer doesn't deliver, which occasionally one won't (these are humans we're talking about), then that developer will likely have an extremely hard time of ever getting significant funding again. So the onus is still on them to deliver a very solid product.
In the end, you wind up with a team of companies that are all focusing on what they are best at, working together to create, deliver, and market products that are superior to what one of the companies could ever have hoped to achieve alone. In terms of percentages, each might have to take a lower amount than they might otherwise prefer (this especially applies to the indie developers themselves), but given the increase this is likely to have on sales volume, the actual amount of revenue received by each party would generally be higher in the end. All of the businesses I just described in my imagined indie ecosystem should be able to be profitable, even quite profitable, if they do their respective jobs well.
And that's still with a $20 or less price point for the games, which is good for consumers. Also good for consumers: if indie developers have the time and money they need to be secure and just focus on creating amazing products, you'll see better products. That's a win for everyone.
The article is well worth a read, and it flows well with a lot of things I have been thinking about recently. I've always worked for small businesses, but often I've had very large businesses as key clients, and so I've had an opportunity to see it from both ends. I much prefer being in a small company because of the autonomy and room for creativity that provides (and the increased possibility of returns if the business does very well), but there's a key aspect often missing from small companies: security. That in itself can be a good thing, because it can prompt the business to be proactive where larger companies might be lethargic. But...
The Inevitable Challenge Of Traditional Small Businesses
On the other hand, lack of funding can lead to lack of certain expertises among available staff. In the past I've been in a company where we had excellent programming staff and support staff, but sales staff that couldn't sell the product, and a very novice marketing staff. That business actually did okay based on word of mouth alone, because clients liked our product and told other clients, but how much better might things have gone if we'd had really excellent sales and marketing staff to match our excellent product?
Or, to cite another example, I once did some contract work for a small company that had developed the world's smallest (at the time) cell phone motherboard. It was about half the size of anything else on the market, back when cell phones were much larger; the possibility of such a motherboard was staggering, because it would have allowed for phones the size of today's devices about 3 years before those actually hit stores. Unfortunately, the company was completely unsuccessful in selling their work because they didn't have the needed expertise on the business development end of things.
I love Justin Vincent's talk about encapsulation in his article, because that's exactly what is needed for companies like these. A lot of startups are product-focused, and they know how to make a product that is really unique and useful inside some niche. But unless they just happen to be lucky enough to have staff who are really ace at sales, marketing, and business development, that great idea is likely to languish in obscurity or at least not reach its full potential.
AI War, for example, has done extremely well for an indie game and is still seeing a significantly growing playerbase every month, but marketing has always been a huge challenge for us. And none of the success we have seen would have been possible without all our digital distribution partners, and our upcoming retail partners. It's still quite a challenge to launch a product even in the digital marketplace, and I had to essentially work two jobs for years and luck into the right partnerships in order to make it happen.
My Ideal Approach For Indie Development
I have been thinking for the last few months about how the ideal setup for indie development would work. In other words, how to maximize output from indie developers, maximize revenue for them and their partners, and in general serve the gaming consumers the best by getting them the widest possible variety of truly quality titles at reasonable prices. Here's the ecosystem I imagine:
Indie Development Company: This obviously already exists, but currently the indie developer has to do most everything -- game development, support, funding themselves, marketing, business development, and so on. In my imagined environment, the indie development company would mainly be responsible for game development and technical support/patches (basically what AAA game development companies are responsible for).
Digital and Retail Distributors: These companies also clearly already exist, and I think that they by and large serve their function admirably. The challenge for most indie developers, however, is actually getting the notice of these distributors. The challenge for these distributors is that they get so many totally crap submissions that it is hard to evaluate what is good and what is not. This is very similar to the book publishing industry, incidentally, which leads us to...
Indie Game Agents: These currently do not exist, not in the sense of the book publishing world. Certain well-connected individuals can act as agents, and in fact there are regional sales agents for retail, but they don't act as quite the career partner and liaison that you see with book author agents. More to the point, most indie developers don't even know these agents exist, and/or don't have any way to contact them. It basically requires having the right network connections, and a track record of existing success in the digital market. If you're unheard-of, then forget about it at present. So, the theoretical agents would be:
1) Available for submissions from all indies (acting as talent scouts), as with book publishing agents.
2) In exchange for an ongoing commission (10% to 15% of what the indie developer earns) but no upfront fees, will handle coordination of marketing, sales, business development, and so forth in both the digital and retail spaces. They would basically be the indie developer's business guide, advocate to business associates, and so on. Again, like book publishing agents.
3) These agents would be known and trusted by the distributors based on their past successes in finding diamonds in the rough that went on to be successful, and so if your game were to catch the eye of an agent that would be a sure-in to digital distribution at the least. These agents would be the valuable filters to the distribution pipeline, and the net effect in the short term would be to get more quality titles through. Fact is, a lot of indie developers themselves are not persistent enough or good enough at describing their work to catch the interest of distributors who have so much else to do. Right now, to get even digital distribution deals, you have to catch someone's eye at just the right time.
Advertising/Marketing Agencies: These certainly exist, but these are vendors, not partners, in almost every case. They perform a service for a fee for anyone who can pay the fee, and then their work is done. They have no stake in the success of the product (they don't even have to like the product, let alone fully understand it), and they are inaccessible to anyone who can't afford the upfront costs. In the ideal model for the indie market, these agencies would be full partners on an individual game's public image, coordinated by the game agent.
In other words, they would handle the details of advertising and marketing, as overseen by the game agent (who would also be responsible for selecting a good advertising/marketing agency), and they would not see any return on their work except a percentage of sales revenue. This could be anywhere from 5% to 10% of what the game makes in total. This is akin to having a talented in-house advertising/marketing staff, since they have a vested interest in making the products they represent quantifiably more successful.
Investment Partners: The last big problem for indies is funding. Creating a game takes quite a long while to do, and this requires money for staff salaries, contractor pay, health insurance, licensing of development tools, possibly office space (for those that aren't virtual offices), and so on. Really polished indie games are likely to cost anywhere from $200,000.00 USD to $400,000.00 USD (or more) if the staff isn't being paid a pittance upfront in hopes of later return. The idea of the investment partners is that they would be contacted by the game agent, or directly by the indie developer in a few cases, and they would provide upfront funding for projects that can demonstrate their worth.
That doesn't necessarily mean a detailed and rigid design document, given that part of the strength of an indie developer is their ability to innovate and use iterative design techniques. Rather, it's a matter of proving out the team and their ability to execute and refine solid ideas. That could be based on past products (spare-time, second-job type affairs), or based on a prototype. Some of the products an investment partner picks up will flop, as is the case with any such market, but the idea is that the investment partner is structured in such a way that even if 9 out of 10 indie projects they take on do not make a positive return, they as a company still see a positive return based on the 1 out of 10 that is a much larger success.
With the advertising/marketing partners and game agents in place, the likelihood of success only goes up. Additionally, for the savvy investment partner that invests only in indie developers with a history of past success (whether that means commercially-speaking, or in terms of potentially marketable ideas brought to fruition, or whatever the criteria is), the return is likely to be much higher. I could see several tiers of investment partners forming, with higher-percentage-taking investors that might prefer higher-risk investments, and lower-percentage-taking investors that only the "premium" indie developers with mega-hits under their belts could have access to. Arcen would likely be slotted with an investment partner somewhere in the middle of that spectrum, for instance.
What Would This Sort Of Indie Development Approach Really Change?
It would provide a way for indie developers to start small and stay small, which has many advantages as noted in Justin Vincent's article. I am dismayed that so many indie developers basically create a pet project as a way to then launch into the larger industry. Indie development shouldn't just be about launching yourself into AAA development. I started indie, and I want to finish indie, if at all possible.
What does indie really mean, anyway? It does mean smaller projects (not multi-million dollars), but also projects with a lot more creativity -- and therefore risk. It means having freedom to experiment, and less structure to the start of the development process. There is less known up front, and more discovered as you go. With expert developers, you'll get products that would never come about any other way. If you take Jonathan Blow, give him some money and some time, then stay out of his way, you can trust he'll come out with something amazing that he'd never create if he was working at someplace like EA.
Is it possible to be an expert indie developer? You bet. This subject probably deserves a post all of its own, but for now let it suffice to say that there are examples all around the industry. Even just purely from an ROI standpoint for investors and partners, I think that's something worthwhile to cultivate in a more structured way from the business side of things (let alone all of the larger creative benefits to the industry as a whole). The goal is to give the indie development business more structure and security, have encapsulated partners who are better at handling the things that your average indie developer is poor at, and then just let the indie developers do their work.
The investors and partners will of course want to keep an eye on the developers, especially the not-yet-fully-proven ones, to make sure they don't go off on a crazy tangent -- but otherwise they need to just trust that the developers are doing what they need to do to make an innovative product that people will want to buy. If a developer doesn't deliver, which occasionally one won't (these are humans we're talking about), then that developer will likely have an extremely hard time of ever getting significant funding again. So the onus is still on them to deliver a very solid product.
In the end, you wind up with a team of companies that are all focusing on what they are best at, working together to create, deliver, and market products that are superior to what one of the companies could ever have hoped to achieve alone. In terms of percentages, each might have to take a lower amount than they might otherwise prefer (this especially applies to the indie developers themselves), but given the increase this is likely to have on sales volume, the actual amount of revenue received by each party would generally be higher in the end. All of the businesses I just described in my imagined indie ecosystem should be able to be profitable, even quite profitable, if they do their respective jobs well.
And that's still with a $20 or less price point for the games, which is good for consumers. Also good for consumers: if indie developers have the time and money they need to be secure and just focus on creating amazing products, you'll see better products. That's a win for everyone.
Wednesday, December 9, 2009
Design Mostly Right: Co-Op In New Super Mario Bros. Wii
This post is a response to the co-op review of New Super Mario Bros. Wii on Co-Optimus. I'm a longtime fan of co-optimus, and so I found it interesting that they gave NSMBW a 2.5/5 on their co-op review, and a 4.5/5 overall. I've had the game for a few days now, and have made it through the first six worlds playing co-op with my wife. Here are my thoughts, from a design standpoint (make sure you read the co-optimus review first):
I see the points in the co-optimus review, and as a game designer I would certainly never have made the players collide with one another in a platformer about precision timing. It's like having extreme friendly fire turned on all the time.
However, that said, for lack of the "perfect" mode of co-op in a Mario game, this is certainly quite wonderful and my wife and I really enjoy it. The bubble has been used to great effect, usually as a last-ditch "save yourself" effect when one player gets too far ahead of the other, or one is about to fall off, or whatever.
The interesting thing is that I feel like the "always having friendly fire on" requires and encourages more cooperation for true success. You can go in and fight and bicker through levels, but you'll never succeed on the harder ones that way. The only way to really succeed is to pay close attention to what your teammates are doing.
Now, granted, I've only played this with two players (not 1, 3, or 4), and I imagine that with 3-4 players this would be a nightmare. But with 2 it's great. One of the most enjoyable Mario games I've played in a long time (and I've played them all), and a lot of that is because it is so hardcore-oriented along with having co-op in it.
For those who were hoping for a co-op experience that would allow for players of wildly different skill levels to play together (which would have been ideal by far), I can see why this scored a 2.5/5. For myself and my wife, this has been a 4.5/5 experience or higher, because of the co-op and the game experience in general. If the co-op had been a bit better, this would have been a 5/5, definitely.
One comment about the mushrooms being the secondary items coming out of question blocks. From my experience, that is not actually true. If all of the players are small, then yes, that's what happens. Normally in single player you would just get a single mushroom, so the extra powerup is sort of a bonus. But if there are a mix of big-or-better players and small players, you will get one good powerup per non-small player, and one mushroom per small player. If everyone is non-small, you just get good powerups. Seems sensible to me.
This game is not perfect, and part of me can really understand why co-optimus gave it a 2.5/5, but I hope that doesn't turn people away from the game who might otherwise enjoy it. It's quite good in co-op, under the right circumstances. It's that caveat there that's the cause of all the trouble.
And that, in a nutshell, is the case for getting feedback from players early and often. It could so easily have been all but perfect as a game. As it stands, I still love it, but not everyone will.
I see the points in the co-optimus review, and as a game designer I would certainly never have made the players collide with one another in a platformer about precision timing. It's like having extreme friendly fire turned on all the time.
However, that said, for lack of the "perfect" mode of co-op in a Mario game, this is certainly quite wonderful and my wife and I really enjoy it. The bubble has been used to great effect, usually as a last-ditch "save yourself" effect when one player gets too far ahead of the other, or one is about to fall off, or whatever.
The interesting thing is that I feel like the "always having friendly fire on" requires and encourages more cooperation for true success. You can go in and fight and bicker through levels, but you'll never succeed on the harder ones that way. The only way to really succeed is to pay close attention to what your teammates are doing.
Now, granted, I've only played this with two players (not 1, 3, or 4), and I imagine that with 3-4 players this would be a nightmare. But with 2 it's great. One of the most enjoyable Mario games I've played in a long time (and I've played them all), and a lot of that is because it is so hardcore-oriented along with having co-op in it.
For those who were hoping for a co-op experience that would allow for players of wildly different skill levels to play together (which would have been ideal by far), I can see why this scored a 2.5/5. For myself and my wife, this has been a 4.5/5 experience or higher, because of the co-op and the game experience in general. If the co-op had been a bit better, this would have been a 5/5, definitely.
One comment about the mushrooms being the secondary items coming out of question blocks. From my experience, that is not actually true. If all of the players are small, then yes, that's what happens. Normally in single player you would just get a single mushroom, so the extra powerup is sort of a bonus. But if there are a mix of big-or-better players and small players, you will get one good powerup per non-small player, and one mushroom per small player. If everyone is non-small, you just get good powerups. Seems sensible to me.
This game is not perfect, and part of me can really understand why co-optimus gave it a 2.5/5, but I hope that doesn't turn people away from the game who might otherwise enjoy it. It's quite good in co-op, under the right circumstances. It's that caveat there that's the cause of all the trouble.
And that, in a nutshell, is the case for getting feedback from players early and often. It could so easily have been all but perfect as a game. As it stands, I still love it, but not everyone will.
Tuesday, December 1, 2009
Indie XMas, And The Start Of A New Adventure
First off, let me plug the Indie Games Xmas 2009 Calendar. This was something originally proposed over on the excellent GameProducer blog, which we at Arcen quickly knew we wanted to be a part of. The idea is that this is an Advent Calendar wherein every day a new indie game, trailer, or similar is released. As it turns out, the first day (today) is revealing AI War. Be sure to check back every day of the month for more updates on lots of great indie games, however; the idea is to promote some great gems you might not otherwise have heard of during a season where the AAA games typically steal the spotlight.
In other news, coincidentally this is also my first day working fulltime for Arcen Games. Up until now I've also been holding down a day job as the CTO of a SaaS software company, but since our 2.0 release and release on Steam, Arcen is now doing well enough to support myself and our composer fulltime in addition to our artist, who has been fulltime since August.
My posts tend to be lengthy, but for this momentous (to me) post, I'm going to keep it quite brief. I've been at my past company for over 8 years, and I'll really miss the people and the clients there -- it's been a great time there, and I'm a bit bummed to no longer be part of that great team. Of course, it was my own choice to leave, and at the same time as I am a bit sad about leaving my last post, I couldn't be happier or more excited about moving into fulltime game development. There's lots of exciting stuff brewing for Arcen in 2010, so I'll be sure to post about that as they come up!
And, you know, I'll post some more on game development topics before too long, too! It's just been a very busy month.
In other news, coincidentally this is also my first day working fulltime for Arcen Games. Up until now I've also been holding down a day job as the CTO of a SaaS software company, but since our 2.0 release and release on Steam, Arcen is now doing well enough to support myself and our composer fulltime in addition to our artist, who has been fulltime since August.
My posts tend to be lengthy, but for this momentous (to me) post, I'm going to keep it quite brief. I've been at my past company for over 8 years, and I'll really miss the people and the clients there -- it's been a great time there, and I'm a bit bummed to no longer be part of that great team. Of course, it was my own choice to leave, and at the same time as I am a bit sad about leaving my last post, I couldn't be happier or more excited about moving into fulltime game development. There's lots of exciting stuff brewing for Arcen in 2010, so I'll be sure to post about that as they come up!
And, you know, I'll post some more on game development topics before too long, too! It's just been a very busy month.