Jeff-Vogel

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Monday, 27 April 2009

Why Nobody Should Ever Change Anything, Ever.

Posted on 19:42 by Unknown
One of the biggest criticisms leveled at me over the years is that I only write the same game over and over again. This fills me with bitter, ironic laughter, because of one thing. Whenever I change anything, I get lots of angry E-mail asking me to change it back.

I've learned a lot running this business. Many lessons, most of them learned painfully. And I have gained no more aggravating bit of knowledge than this one:

There is no change you can make to your games, no matter how clearly obvious or beneficial, that will not anger some of your fans.

And a brief corollary:

If the change doesn't make someone angry, it didn't matter.

A Visual Example

My first game, Exile, released in January, 1995, looked something like this:













(Actually, Exile v1.0 had charming creature graphics drawn by my ex-wife and horrible button and interface graphics drawn by me. But it was about the same.)

Our newest game, Geneforge 5: Overthrow, looks like this:











As you can see, I have changed just about everything. Repeatedly. Graphics. Style. Interface. And the game system underneath. Everything has been redone, and, as I learned more, redone again. And while not all of the changes have been beneficial (and were then re-changed in later games), the process has been one of evolution toward betterness.

And every change earned me angry e-mails and lost customers. I've gotten more, "Why have you forsaken me? I am lost to you forever." E-mails from customers than I could ever count. It's a depressing thing to happen when you've been really busting your butt and your budget to bring about improvements. But you have to live with it. You just have to steel yourself and always remember this:

People hate change.

Case Studies From My Own Experience

Here are some hugely beneficial (and profitable) changes I made which earned me fury and lost customers.
  • Switch From A Flat View to a 3-D Isometric View - My first games were completely flat, as seen in the first illustration. I switched to a far, far nicer pseudo 3-D isometric view in 1998. It looks better, and it enables me to do more things with the game. (Like elevations.) But, over a decade later, I STILL get complaints about it. Lost souls, out in the wilderness, wanting me to return to a design I got completely fed up with in a previous century.
  • Switch From Hand-Drawn To Rendered Graphics - Oh, wow. There are a lot of people still angry about this change, made in Avernum 4 in 2005. My old graphics were hand-drawn instead of rendered, which made any sort of animation extremely painstaking and expensive. Using 3-D models to render creatures and terrain enables me to have a wider variety of much nicer icons without crushing my budget. But it changed the look of the games that people were used to, and a lot of customers never forgave me for it.
  • Removing the Need to Identify Magic Items - A smaller but highly instructive example. Once, when you got a magic item in one of my RPGs, you had to take it to a sage to get it identified. This was busy work, confused new players, diluted the excitement of collecting lewtz, and just wasn't fun. Dropping it was a total no-brainer. And yet people complained. Why? Oh, why?
  • Removed the Need to Carry Around Ammunition For Bows - This is a recent change, part of my desire to eliminate busywork. When you shoot a bow, you just shoot it. You don't need to shop for arrows. I can see why this would break immersion for people, but it seems a neutral change at worst. Not worth the angry complaints I've gotten.
Now the more contrary among you might be thinking, "Well, maybe people complain because your so-called improvements actually suck. How about that? Huh? Huh?" Not likely. Historically, when I made major augmentations to the engine, I've seen increases in sales. If the changes I made sucked, I would not still be in business. So give me the benefit of the doubt.

And I should point out one more thing. if someone doesn't like a change, well, you can't win an argument with a customer. If they don't like it, that's their right. They'll have to find their bliss somewhere else. It is your job to make sure that your changes bring in customers to replace the ones you lose.

So What Should I, a Game Developer, Do?

Forewarned is forearmed. You can't do anything about this phenomenon, but you should steel yourself for it so you don't suffer shock, self-doubt, and potentially catastrophic second guessing.

Be sure the changes you make are worthwhile. Be sure that your community of fans is warned about them, so that the culture shock is lessened. Be apologetic but firm to the people that complain about improvements. And be confident. Remember, evolution is necessary. Making the same people happy forever is a surefire route to stagnation and burnout.

One More Thing, For Those Who Are Angry At Me Changing Things

Despite what some people think, I am constitutionally incapable of writing the same game again and again. Writing more than three games without major changes in the engine or system or setting would drive me out of my mind. I need to change the system so that I can open up new design spaces. I need to change the graphics so I don't go loopy staring at the same icons day after day.

There are some people out there who claim they would be honestly happy if I just rewrote Exile, again and again, year after year. But I can't do that. Nobody can. You should always be looking for ways to evolve your work. It'll keep you from going crazy.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in advice, back in the day, design, indie, tldr | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Some Morbid Reading For Your Day
    As the years passed, I have seen a lot of Indie developers rocket past me, just because they are more talented and courageous than I am. Stu...
  • Katawa Shoujo, Sex Stuff in Games, and Choosing What You Are Allowed To See
    What I expected: Weirdo smut. What I got: A little box full of therapy. This is one of those blog posts it's really hard to hit the Publ...
  • The Joy and Despair of Writing These Stupid Games.
    Please, Charlie Bucket, save me from this hell of my own devising! I've been in 80-hour-week crunch for 15 months! "We are the musi...
  • A New Article on IGN RPG Vault.
    My latest View From the Bottom article, the first in a long time, is now up on IGN RPG Vault. It's called "We're All Charity Ca...
  • Why We Need Video Game Critics, Even If the Whole Topic Is Boring
    Video games need more of this ... We've reached the point where video games have a huge place in our culture, and yet most of them are ....
  • Marketing, Dumb Luck, and the Popping of the Indie Bubble.
    This article is kind of depressing, so here is a puppy hugging a kitten. Sigh. I hate writing articles like this. Even if I’m right (and I r...
  • "Whom" Is Dumb.
    This will be one of those blog posts where I go and court controversy. No, it won't be about software piracy. Something worse. I'm g...
  • More Arguing About Women In Video Games. But This Time the Women Can Beat You Up.
    Frankly, I want my avatar to look more like this ... The argument about how women should be portrayed in video games rages inexplicably on. ...
  • We Finally Released Avadon 2.
    Keeping the single-player, turn-based, story-heavy flame alive. After two years of development, we have finally released our first all-new g...
  • Mass Effect 3 Review: The Good Stuff
    Since I write so much in this space about fantasy role-playing games in general and Bioware stuff in particular, I feel kind of lame for say...

Categories

  • 10000 hours
  • addiction
  • adolescent power fantasy
  • advice
  • android
  • apple
  • avadon
  • avernum
  • back in the day
  • bees
  • bioware
  • blatant pr
  • books
  • boring
  • both artsy AND fartsy
  • braid
  • business stuff
  • cowardice
  • criticism
  • death
  • design
  • destroying my employability in the game industry
  • developer diary
  • diablo
  • dragon age
  • drm
  • dry boring stuff
  • dungeons and dragons
  • ego-massage
  • entertaining atrocities
  • everyone will hate this
  • fad
  • fart
  • flamebait
  • flumph
  • games
  • geneforge
  • gold rush
  • grand theft auto
  • grumpy gamer
  • guitar hero
  • high-functioning alcoholics
  • humble bundle
  • humor
  • i act like i am smart
  • i am a parent if you can believe that
  • i am completely freaking out
  • i am very old
  • i hate art
  • i suck at pr
  • i've wasted my life
  • indie
  • internet hate machine
  • interview
  • introduction
  • introvision
  • ipad
  • iphone
  • jetpacks
  • l2pn00b
  • linking to things i like
  • loser
  • losing lots of money
  • mass effect
  • microsoft
  • minecraft
  • mourning
  • movie
  • nerd
  • nerdjoy
  • nerdrage
  • nethergate
  • nobel prize in awesomeness
  • not about games
  • not wrong to expect to be paid for your work
  • omigodomigodomigod
  • penny arcade
  • physical activity
  • piracy
  • ponies
  • pricing
  • pubic hair and semen
  • queen of fun
  • ranting
  • review
  • rock band
  • rpgs
  • saints row
  • sale
  • sales
  • sales figures
  • shameless self-promotion
  • shareware
  • skyrim
  • something for the ladies
  • spiderweb software
  • squid
  • ssssssss BOOM
  • star trek
  • steam
  • still alive
  • stories are for losers and squares
  • tasty meat
  • tech support
  • teh casualz
  • testing
  • that guy
  • the culture war
  • think of the children
  • tldr
  • travel journal
  • union
  • VEGAS
  • view from the bottom
  • watchmen
  • what cruddy graphics
  • whistling past graveyard
  • whomwhomwhom
  • why did my computer just melt
  • work i didn't get paid for
  • world of goo
  • xbox
  • you made my virtual pet starve you jerk
  • zombies

Blog Archive

  • ►  2013 (18)
    • ►  December (2)
    • ►  November (4)
    • ►  October (6)
    • ►  September (6)
  • ►  2012 (23)
    • ►  October (2)
    • ►  September (3)
    • ►  August (3)
    • ►  July (2)
    • ►  June (1)
    • ►  May (4)
    • ►  April (2)
    • ►  March (1)
    • ►  February (3)
    • ►  January (2)
  • ►  2011 (34)
    • ►  December (3)
    • ►  November (2)
    • ►  October (3)
    • ►  September (1)
    • ►  August (5)
    • ►  July (1)
    • ►  June (4)
    • ►  May (3)
    • ►  April (3)
    • ►  March (5)
    • ►  February (2)
    • ►  January (2)
  • ►  2010 (39)
    • ►  December (2)
    • ►  November (3)
    • ►  October (1)
    • ►  September (4)
    • ►  August (3)
    • ►  July (4)
    • ►  June (3)
    • ►  May (5)
    • ►  April (3)
    • ►  March (4)
    • ►  February (3)
    • ►  January (4)
  • ▼  2009 (53)
    • ►  December (4)
    • ►  November (3)
    • ►  October (6)
    • ►  September (4)
    • ►  August (4)
    • ►  July (4)
    • ►  June (5)
    • ►  May (7)
    • ▼  April (8)
      • Some Morbid Reading For Your Day
      • Why Nobody Should Ever Change Anything, Ever.
      • Indie Games Should Cost More, Pt. 2, The Expensening!
      • More Evidence Of Overwhelming Piracy
      • Interview Flamebait!
      • Indie Games Should Cost More, Pt. 1
      • Why Rock Band Is Better Than Actual Music
      • Couple More Quick iPhone Thoughts
    • ►  March (8)
Powered by Blogger.

About Me

Unknown
View my complete profile