Who wants to help us write documentation?

[Maxstate]

Storywriting, technology, lore, politics, social situations, factions; we need more of everything. Who'd like to have a go at writing documentation for the game?

On that note, we also need more developers of every kind. Modelers, animators and texturers are more than welcome, while programmers and other libertarians are also invited.

[Monochrome]

Again, it's a bit hard to join the boat when one has no idea where it's headed for. Could you please outline the project's premise, theme, and gameplay basics, and then create a thread for a propper discussion of these? It's just that I think that the information you've provided us so far is a bit too vague. I feel it's a bit hard to find motivation or to get interested on any project without knowing what it's all about, and what lies in your imagination that lead you to the creation of it in the 1st place.

[Monochrome]

And again, if you don't want to share certain details, which is totally understandable, I would be happy with a simple one-sentence description of the premise. Think about the awesome factor or associated awesome situations that you think it would be worthwhile to reproduce in actual gameplay. Think of it as a sentence that would make other people say something like "Fuck yes, I would like to play something like that!". Here's some examples:

For a shooter:
"A space mercenary frozen in a drifting capsule for 500 years, crashes on a giant abandoned space station where he must fight for his life"

For an RTS
"Steampunk armies battle for planetary dominion by using all sorts of giant steam robots and airships"

For an RPG
"You are a necromancer on a quest for power to become the supreme death god and enslave mankind"


Get it? The awesome factor!

[Maxstate]

It's hard to get the awesome factor written down correctly, when we're not sure on what to do yet. Someone like you might come along and have fabulous ideas that might involve changing the entire theme of the game to something different. I'd rather let you and other developers READ the documentation we have first, brainstorm about whether to keep it, THEN decide what to publish and what not to.

[Monochrome]

Therefore I suggest you to lock and sticky the documentation thread and create a another one strictly for discussion. It's a bit hard to navigate on a sea of tl:drness.

[Maxstate]

I made it a bit easier to read.

http://bound.filefreak.net/forum/showthread.php?t=16

Check it out.