I'm a hobbyist game designer and animator and I've been working hard with many partners to try and get this project started but it always seems to grind to a halt. I need some feedback/opinions on the project to determine the issue. I've got assets which include an untextured, rigged and roughly animated character. Which I posted below.

This is a competitive, 3D arcade styled, third person, free for all combat game that is based on a small barren spherical world. The winning condition is to unifying all units in a match using a "Domination list" mechanic. With each kill a player creates a link and highlights the enemy on their domination list. This link disables the ability to do damage between the player, the enemy (now linked) and any other units/players highlighted on the player's "domination list" . If a player is already on a list the kills they make will add to the list they are a part of as well as highlight the kill on their own list. If a player is killed all the links on their own list are split up amongst the units/players lists disbanding any units/players with no kills of their own.

The player's actions tab (a custom GUI interface hotkeys 1-0) will enable the player to drag and drop items, earned skills and up to 5 linked players from their "Domination/action list" to the tab. A player's tactical team of 5 will expand quickly once those 5 players earn their own links/kills. This makes the main player tactical team into an operational group. The main player issues objectives and support attempting to use the teams to the best of their abilities. A operational player's view pulls back to enable easier field command however objectives are best issued from the interactive holographic mini-map representation of the entire spherical world. The last step of this hierarchy is if one of the players in that operational group becomes an operational leader turning the main player into a strategic commander. This commander issues strategic goals for the groups to build objectives towards attempting to move these masses of players into the right area at the right time. The commanders view will pull back more and reveal more of the map, making defensive command easier in addition to the mini-map.

As the player earns more links, they will also earn more skills and items. Many of the skills will allow the player to issue weapons and other items to their subordinates as incentives to follow orders but other skills will act as buffs and abilities like building basic tactical defenses like barbwire, trenches and sandbag walls, etc. Some skills will compliment command while others are more combat focused. A player will have the option to ignore command entirely and focus entirely on combat if they choose.

The final touches to the game could include character transformation skills that allow an operational leader to turn into a support vehicle or a strategic commander into a bunker. Lastly an end of match survival meta game could test the "winning" player and the unified army against endless waves of deadlier enemies, creating a brag worthy survival time.[/quote]



If you've made it this far then I applaud you and thank you for reading it. If you have any questions or constructive feedback I'd love to hear it. I've got some decent feedback already but I'm still very open to suggestions on how to get this project off the ground. This is my third edit and update. Keep the feedback coming!

Ashaman, its always an issue of a dedicated team (mostly a lack of programing) I suppose but I've wondered if that's because the design is flawed (not worth building). I was wondering if there are design issues (based on the brief) that are glaringly obvious to all but myself. I've made some editing changes to the brief description but which aspects feel overly vague, I want to be sure the design is clear.

This is a competitive, arcade styled, third person, sci-fi, free for all that is based on a small barren spherical world.

If I were to do this project, I guess the first thing to consider would what engine I want to use for this. Unity 3D? Or maybe Torque? Then, I'll build a very basic bare bones demo. Once I have a basic demo out, I'll go from there.

Good luck! Sounds like it will be a fun game.

Ashaman73, I'd have to agree about being able to tackle the visuals. It is however, useful to be able to test if the visuals are worth creating in the first place, and without programming this is harder to achieve. The visuals in the game are just as open ended at this point as the design mechanics and very dependent on the limits a programmer can recognize.

Legendre, I've been following the Unity community with interest and I'd love to build a basic demo and go from there but again its a matter of a dedicated team. I get the impression that achieving that team is really where my focus should be at this point. Does it make sense to put up an advert for a programmer here? Are these designs worth starting a Kickstarter account and offer pay?

Edited the doc, changed some wording and rephrased many parts. Hope for more feedback.

Legendre, I've been following the Unity community with interest and I'd love to build a basic demo and go from there but again its a matter of a dedicated team. I get the impression that achieving that team is really where my focus should be at this point. Does it make sense to put up an advert for a programmer here? Are these designs worth starting a Kickstarter account and offer pay?

I am not exactly sure how you intend to form a team, so please forgive me if I make any wrong assumptions. Also, take my "advice" with a grain of salt because they are solely based on personal experience running my own projects. In my humble opinion, I think there are two big issues:

1) Is this project too ambitious?

(3rd person) Shooter = networking and latency issues. 3D Engine = probably the toughest medium for game development. MMO = the more concurrent players you have, the more difficult it is to make.

Shooter + 3D Engine + MMO + all the features in your description = Probably way too hard for indie. (don't think there are many unfunded indie 3D MMO shooters)

Perhaps you can try to greatly scale down your vision to the point where it is realistic for a 1-2 man team to make in 2-3 months. Releasing a scaled down version has several benefits: It shows people that you are serious, and can lead a project from start to end. It shows people how fun the core mechanics are: lots of designers out there claiming that their design is fun, but you can actually demonstrate yours. It gives you a starting foundation to build the rest of your game, perhaps even winning you some fans or funding.

2) Are you trying to form a team of unpaid volunteers?

I have seen this happen over and over again: a team of volunteers get together to make a game ( e.g. fan remakes of old abandonware), after a few months, people get too busy with real life and starts leaving. Then, the project gets abandoned.

Unless you can continue coding by yourself after everyone left, you might end up constantly putting your project on hold indefinitely while you look for the next volunteer team.

Have you thought about making it a top down shooter in Adobe Flash? Flash actionscript is super easy to learn and work with, I think you should be able to come out with a small singleplayer version of your game to upload to a flash portal within weeks, given that you can produce your own artwork. If the game gets popular, you'll start to attract other developers and fans etc.

An indie game that started like this is "Dead Frontier". The developer uploaded a 2D singleplayer demo version on Newgrounds, then made a 2D multiplayer version on his website. One year later, it has evolved into a profitable 3D top down shooter.

Legendre I appreciate the humbling perspective. Given my lack in knowledge of programing you're probably absolutely right on every point. What would you say is the biggest hurdle in programming a shooter? The reason I've chosen 3D is because I've modeled rigged and animated the assets and I'm eager to import and implement gameplay mechanics for them. As for the multiplayer, does it make programing multiplayer easier if I alter the design to suit an 8 player match or is latency just a pain no matter the number of players? I wasn't really aiming for the persistent world or thousands of players found in an MMO but if by capping the number of players to a very low number is easier to program, then the design can be easily altered. Thanks again for the feedback, with any luck I can get this design to a stage where its approachable, achievable and actually moving beyond the conceptual stage.

Have you thought about using something like the Unreal Development Kit? It can handle small scale multiplayer, has all of the 3D code already written for you, and includes a graphical scripting language. It's also free to use until you make something like $50k in sales.