Advertisement

Ongoing development after release model

Started by April 10, 2007 12:39 PM
9 comments, last by Tom Sloper 17 years, 7 months ago
Does anyone know what the correct term for this is? As far as I understand it, beta implies that no more major features will be added, and even a commercial beta version is usually free, right? We plan on releasing our game initially (direct download only, indy developer etc) with a limited feature set, but still polished and functional. Basically we will add multiplayer support (the game is designed to be primarily multiplayer, though the single player version will still be fun!) and a lot more content after release, and want to make this clear from the outset. Is calling it a final version but promising these additional features in the near future the best way to go about it? Or is there some other terminology anyone can think of? Thanks, Brendan
The terminology varies slightly across industries. Here is a link with more info on the generally accepted terms:

http://en.wikipedia.org/wiki/Software_release ( Clicky )


> Is calling it a final version but promising these additional
> features in the near future the best way to go about it? Or
> is there some other terminology anyone can think of?

Those are simply future releases. You can call them "patches" or "upgrades". You can apply whatever numbering scheme you prefer to identify them. Here is what is generally adopted:

http://en.wikipedia.org/wiki/Version_numbering ( Clicky ).

-cb
Advertisement
Brendan wrote:

>As far as I understand it, beta implies that no more major features will be added,

It does imply that, but that's not the entirety of what "beta" means. See the Game Biz Glossary at http://www.sloperama.com/advice/lesson28.htm (not clicky - cutty and pastey).

>and even a commercial beta version is usually free, right?

The phrase "commercial beta" does not imply "free." I know that's not exactly what you asked. A publisher might release a free beta version of its software in order to get the public's help with the QA process.

>We plan on releasing our game initially (direct download only, indy developer etc) with a limited feature set, but still polished and functional.

THAT is called a "demo version."

>Basically we will add multiplayer support (the game is designed to be primarily multiplayer, though the single player version will still be fun!) and a lot more content after release, and want to make this clear from the outset.

Still "demo."

>Is calling it a final version but promising these additional features in the near future the best way to go about it? Or is there some other terminology anyone can think of?
>Does anyone know what the correct term for this is?

I'd go with "demo." (Note: take my advice with a grain of salt. According to some, I can't be encouraging at all, to anyone I post a reply for.)

-- Tom Sloper -- sloperama.com

MMORPGs do this all the time. Just release it and provide an auto-updater.
Sorry I didn't make myself clear - when I said release, I meant releasing both a playable demo and a full version.

These aren't features we're leaving out because we don't want people to have them. We're just releasing the game early because it's already going to be a complete and polished product with enough single player content to justify the cost, but we need some income to fund further development.

Thanks for the advice on naming conventions, I'll look it up and make a decision. I think in the end it might just come down to promising further development and a patch no. like you suggest.
Brendan wrote:

>These aren't features we're leaving out because we don't want people to have them. ... we need some income to fund further development.

Yes. We understood that. "Demo" might still be appropriate - if you're giving it away, with hopes of getting a funding partner.

>We're just releasing the game early because it's already going to be a complete and polished product with enough single player content to justify the cost

Cost to whom? Now I don't understand. You're selling the demo to the end users? I really need to learn how to read minds! (^_^)

-- Tom Sloper -- sloperama.com

Advertisement
Just sell it as-is, and say it includes a free upgrade to the Multiplayer version?
> Yes. We understood that. "Demo" might still be appropriate - if you're giving it away, with hopes of getting a funding partner.

We're not giving it away, we're selling it. Therefore "Demo" is not appropriate. We're not hoping to get funding, just to make enough money from sales to continue development ourselves.

> Cost to whom? Now I don't understand. You're selling the demo to the end users? I really need to learn how to read minds! (^_^)

Cost to the end-user. It's not a demo... it's an excellent product by the shoddy standards of modern games, even in the state we will release it at. Plus we won't be asking too much (£15).

Admittedly it was a stupid and pointless question, and I understand that you assume we are incompetent teenagers with nothing but a dream, as is so common in this forum. But that is not the case! In fact we've (the royal we, not me personally...) been developing our proprietary 3d graphics/physics engine for 10 years now and I quit a $60k/yr job to come and work on this project. Oh how ye shall see, unbeliever! :)

Brendan wrote:

>We're not giving it away, we're selling it. Therefore "Demo" is not appropriate.

This would be so much easier if I could just read minds. (^_^)

>We're not hoping to get funding, just to make enough money from sales to continue development ourselves.

I C

>Admittedly it was a stupid and pointless question,

It was NOT.

>and I understand that you assume we are incompetent teenagers

If you are talking to me (Tom Sloper), all I can say is ... NO, I did not assume any such thing. I'm sorry if I gave that impression. I thought I was being perfectly helpful and polite...? And not condescending...?

>Oh how ye shall see, unbeliever! :)

Who, me? :(

-- Tom Sloper -- sloperama.com

Tom: Sorry mate I owe you an apology for that. You took the time to respond and offer advice, and I misinterpreted your response and was perhaps even a little rude. Re-reading it I realise how similar to a demo my original description sounded! I would have probably said something similar, I'm just so used to being confronted with unfounded skepticism when asking basic questions that I rarely bother anymore... :)

This topic is closed to new replies.

Advertisement