Sign in to follow this  
dtg108

Does This Way of Making a Game Work?

Recommended Posts

dtg108    394
First of all, moderators: if this is in the wrong place, please, move it. While I don't consider myself "new" to this site anymore, I still don't know exactly where this should go.

Now to the good stuff. My team and I are making a 3D zombie apocalypse simulator MMO soon to be available for Mac and PC. I won't go into detail about this, as this isn't what I'm asking about. Anyway, my programmer is building a system for Unity 3D, kind of like an engine inside of an engine. This is what our game mechanics are based on. We've been working on 3D models, so we would have them ready when our system is complete. However, in my whole game development life (about a year), I've always used one rule: Focus on gameplay, then 3D models. So, in my case, would 3D modeling and then doing gameplay work? Does anybody else work like this? Thanks for any answers!
Dakota.

Share this post


Link to post
Share on other sites
Luau Design DF    231
1. What do you mean by and engine inside the engine?
2. Mostly maybe you should do 3D but only static stuff and not animations and stuff that might need to be changed yet.
3. MMO seriously? That's not a "soon to be released" kind of stuff. Why not just 8/16/32 online players instead?

Share this post


Link to post
Share on other sites
dtg108    394
1. Our game is made inside of Unity 3D engine, but a system is being made to add to that.
2. Thanks.
3. If you knew how our game works, you would know why it needs to be an MMO. You can read my dev journal if you like.

Share this post


Link to post
Share on other sites
Tom Sloper    16062
I'm with redthegreen. First decide what the gameplay is. Then make the models needed for the gameplay. Making the models first might result in having to go back and change some and/or add some and/or delete some.

Share this post


Link to post
Share on other sites
Ashaman73    13715
[quote name='dtg108' timestamp='1353383518' post='5002567']
so is it safe to start the models?
[/quote]
Yes, you can start with the models. It is certain that there are some zombies running around, that you will have a some street sign etc.

Just be aware, that if you start with art which is gameplay relevant (e.g. the layout of a level, some special zombies etc.) , then you will most likely need to adjust it later on. The danger of reworking art or of disposing it completely is higher if the gameplay is not fix yet.

Share this post


Link to post
Share on other sites
solipcoder    300
Start with basic models. Static models should be pretty safe (buildings, props, etc.), animated ones are very likely to require changes, even something as simple as a walk animation might have to be redone if you later on decide that it is too slow or too fast, especially if you don't have any gameplay yet (and it sounded like you haven't decided the pace of the game from what I understood).

I also recommend figuring out what style you want, because that alone will require changes to models without even taking gameplay aspects into account.

Share this post


Link to post
Share on other sites
Sandman    2210
[quote name='dtg108' timestamp='1353375089' post='5002529']
Anyway, my programmer is building a system for Unity 3D, kind of like an engine inside of an engine.
[/quote]

This rings a few alarm bells.

There is a problem that a lot of programmers have, where they feel the need to work on such 'systems' and 'wrappers' and 'useful engine tools' and generally making the code 'perfect' rather than getting on with the task of actually making the game.

While there may be some value to some of this work, most of the time you end up in an endless cycle of refining the 'engine' stuff, refactoring it to make it nicer and nicer, and adding more and more awesome features, and you never actually[i] write the game. [/i]Trust me, I've fallen into this trap myself before.

I would try to encourage your programmer to drop the 'engine in an engine' angle - it's pointless, you already have an engine, it's called Unity - and get on with writing some gameplay. It doesn't matter if the code is ugly, what matters is that you can get the game into a playable state as soon as possible. You can always refine the code later, once you know you've got a product worth finishing - and once you know at last what features you actually [i]need[/i].

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this