RPGWatch Forums

RPGWatch Forums (http://www.rpgwatch.com/forums/index.php)
-   News Comments (http://www.rpgwatch.com/forums/forumdisplay.php?f=10)
-   -   Indie RPGs - 9 Common Mistakes that Indie Game Studios Should Avoid (http://www.rpgwatch.com/forums/showthread.php?t=18704)

Myrthos November 22nd, 2012 15:06

Indie RPGs - 9 Common Mistakes that Indie Game Studios Should Avoid
 
Gamasutra shares with us Ichiro Lambe's views (an indie developer) on 9 common mistakes that indie developers should avoid.
They are short and compact, so here are all of them:
Quote:

1. Starting too large

Lambe notes, dryly, admitting that he's fallen into some of the same traps with his indie titles: "People see games like World Of Warcraft or Call Of Duty: Modern Warfare and [believe] they can create an MMO in 9 months." Being overambitious with scoping is a classic indie failing. So why not pick a smaller game?
2. Creating that one perfect game

Lambe suggests that when you have a game in your heart that you simply must make, you can sometimes over-reach technically or conceptually, because the idea isn't scoped correctly.

His advice: "Step back and consider all the other games you might create" - but don't necessarily go for a grand slam first.
3. Manufacturing your game just to sell

Lambe cautioned that after he had success with a Palm Pilot title, he ended up making a large amount of other simple casual titles, and he believes his lack of passion rubbed off and ended up with lackluster results. It's only when you inject a certain amount of passion into the process that you may find a middle ground.
4. Thinking tactically vs. strategically

A lot of developers think of things tactically and individually - switching between game design, PR, and customer service in a very monolithic fashion. But if you think of your overall developer brand, you might want to do each task in a strategic brand-specific way - maybe by using videos to reply to text-based comments on a Rock Paper Shotgun article, as Dejobaan joyously did.
5. Failing to plan

It's easy, as an indie, to muddle along in a variety of inefficient ways. But when you get it together — as Dejobaan hopes they have with its upcoming Drunken Robot Pornography, where they talked to Steam early and got extensive Steam Workshop integration for item construction into the title — you'll save yourself a lot of headache down the road.

6. Going it solo

Although you certainly can go at it alone, you'll have nobody to bounce ideas off of. Even as a small studio, if you don't speak to other small independent game studios, Lambe cautioned: "You're missing out."

It turns out that your fellow indies do actually care about you, and they aren't competitive - they are happy to counsel and help and suggest.
7. Imaginary constraints

Lambe joked that many developers think, "'This is how we're supposed to make a game.'

"But let's do something different. There really are no constraints in the game industry, and you shouldn't be afraid of wacky concepts," something Dejobaan often shows with its odd game titles.

8. Ignoring relevant focus areas

A lot of developers simply say "I am creating a game to create a game". They don't worry about interfacing with journalists, they don't worry about PR, and as a result, things don't go well.

You can be creative on your own, but do have to think - at least a little bit - about what the outside world will be interested in, Lambe concludes.

9. Falling in love with your work

An important final rule is relatively simple: "Don't fall in love with it so deeply that you are ignorant about its faults."

Lambe gives the example of a game trailer that might have a 10 second animated 3D logo at the beginning, rather than actual gameplay. You can tell the person who made it was delighted by it, but they are, perhaps, lacking perspective. You need to ask your peers, and you need to show the game to the public through development, Lambe concludes. Only through this will you love your work, but not fall in love with it.
More information.

Thaurin November 22nd, 2012 15:06

These are pretty much the common mistakes many people make with any software development project, maybe even most work period. :) Still, good pointers.

Alrik Fassbauer November 22nd, 2012 20:44

Number 9 is a common mistake of authors, too.

Ihaterpg November 25th, 2012 13:22

Whiner players as there's more and more, here and elsewhere, would better read with care this. Multiple points target them directly.


All times are GMT +2. The time now is 00:32.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Copyright by RPGWatch