SC2Mapster

We need a terrain designer and a trigger expert. All the other jobs have one person minimum.

@DrSuperEvil: Go

No, he had displayed all the brainstorming for the four first missions. But we can have a broader range of thinking, my point is just that if we focus on one map at the time, it may be better.

EDIT: Lorewise, we should find a agreement wether we talk about a weapon or something else. Even if the first mission is not too concerned by that.

Could you edit your post so we focus only on mission 1 please :).

EDIT : Thank you ;)

Okay boys !

So here is what I suggest. I'm contacting several people who showed some interest in this project to ask them their skill and if they want to participate. As I understand for a lot of you, starting a big project like this one is demotivating, I suggest we begin with a TECHNICAL DEMO. Let's make two or three missions, to prepare the plot, show some heroes and a few technological specificity of the campaign.

Thus we can now concentrate on designing mission 1, 2 and 3. The roles I try to assign are thus for a non-definitive basis and the work load won't be that big. I think one or two person MAX by role is way enough.

Here is the summary of the team (I will update), BTW DrSuperEvil do you agree being part of the story team?

• Team leader
• Data and actors manager : DrSuperEvil

• Terrain
• Assets / Actors
  • Flinkelinks
• Data
  • Kuelken
• Script, Trigger
• Story team
  • DrSuperEvil
  • EpicPrawnTime
  • Thunderzak

The map gameplay can be decided in brainstorming and we will take the better ideas. We already have a first mission script draft by DrSuperEvil we can work on. I think this should be our priority ONE now. If we can finish one map, and two more, we will see if the result please us and if the work load is OK or if we need more people.

Cheers !

Quote from Mozared: Go

We don't need bullshit on this forum.

Then you should close this topic. There is no place for such people in this forum. Should not even begin a discussion or a debate with such troll. Don't feed the troll !

@DrSuperEvil: Go

I totally agree on your last point, but I would not reject it entirely, thats why I tried to take the better of it.

Your idea of a inherited weapon is nice I think. It would induce some kind of undesired heritage and bring some interesting themes.

Sorry to insist, but who wants to work on this project? Epicprawn what can you do?

• Data
• Terraining
• Triggers
• Story team
  • DrSuperEvil (need confirmation)
  • Epicprawntime
  • Thunderzak

Quote from epicprawntime: Go

We thought of a twist for the plot that when the weapon is finally finished, your 'boss' betrays you and takes the weapon for itself, then the final missions start in which you have to destroy the weapon and your boss's followers. Thanks for the information above!

I know, I read it and thats why I'm telling you need a twist about why the boss would betray you.

Ookay. So I finished reading the script. It's very draft like for now in my opinion but with serious work and hard thinking could become a nice story. Sorry to give a lot of advises although I'm not showing any work or project, maps whatever on my side but that wont last forever, hopefully :) just trying to help.

If I get it the main axis of the campaign would be:

• You are assigned to the defense of a secret lab holding dangerous weapons
• As you fail to your assignement, you must endure the long path of redemption and overcome your failure to get back the weapons
• The terrans are shown as childish that play with forces they didnt created and couldnt use wisely
• The protoss are shown as creating weapons they cant keep/control and are shown divided (possibily threathned with extinction bring some exteremists ideologies)

Interesting developments and so on:

• Why the hell would the protoss think that imba weapons be better used in their hands than other races hands (i mean as a comparison why nukes are more frightening in the hand of third world or communist powerful countries than occidental countries)
• The motivations of the main characters could be mixed between the will to achieve what he originaly failed, the fear of weapon proliferation (sounds of actuality !) in the hands of others
• It could be told that the character was not really delighted to defend something he was idealigicaly against. A nice twist would be that at the end he manages to get the weapon back, but chooses to destroy it. That would be a nice lesson :)

The possible plotholes I see and other traps

• The Protoss are knowed to be not kin to develop incredibly powerful weapons (see the background behind the colossi). This can be countered by putting the protoss in a real extinction-threat that would kinda legitimate this researches.
• I'm usually not very excited by ulta imba weapons that could defeat swarm, terran governements alike, protoss. Sounds very unreal to me. But it should represent enough of a threat and have a massive realistic scientific explanation behind
• You should have a terrible twist to justify the betraying of your superior, but that could lead to interesting plot if well used
• I cant see the zergs would need a protoss-hand weapon as they are their own weapon, but showing them as only collateral damages or used by protoss/terran would be reducing. Unless you have a good reason to justify that weakness

Hope that thelps your thinking :) cheers

Question friends, do you have some sort of storyline written ? Or a list of maps and missions ? (Sorry dont want to look all the 98 messages)

Congrats ! The model is smoking good quality. Do you plan on adding a unit on top of that bike ?

2.What kind of 'staff' do we need?

Data (Actors, tech trees) Scripting (triggers) Cinematics Terrain design Lore Gameplay

Some may overlap (I would easily imagine gameplay would require a "manager" that would manage datas and scripting as well as the others, or could be done as a collaborative project). For example cinematics and terrain design could go together, except if the terrain guys are very specialized in melee or arcade.

3.How many members do we need at least?

The more members the hardest to manage and the easiest to loose productivity. The big question is, what scope do you want the project to have, what ambitions ? As someone stated above, doing a technical demo for less peoples could be a good way to start.

4.Are we going to plan everything out before creating any maps or are we starting off almost immediately to see what we can get?

For this kind of non-professional project I dont think everything must be planned, but some things need to be manage to organize the work of different jobs.

First thing is you need to list people willing to participate and their range of competence. Then find someone who can be put in charge and lead the project (not has to be a member that has advanced skill in mapping but who can organize and manage the work of the others). Anyway if enough people is motivated for this project a project leader will emerge anyway.

Thats the problem mate :) I've seen a lot of people posting and giving ideas (some very interesting) but no one taking the lead of this project. I think some serious project management could lead this brainstorming into a real end project.

And last question, how many people are working on this? Pure curiosity :)