Glest manual or instruction book?

[gust0208]

Hello everyone!

I just stumbled onto this very impressive program (and will be going on my DVD of gems of open source programs), but I was having difficulty finding a manual or instruction book for the game.  I read through the read me for basic key commands, but wasn't sure if there was more about certain units, buildings, etc.

Thanks for the hard work.

Cheers,
Tom

[josepzin]

We dont have a manual or instruction book.. Only a readme.txt

Look here http://www.glest.org/board/viewtopic.php?t=857

[laok]

Today I have been looking around in the game and managed to harvest en build things. But how on earth can i defend myself against the attacks?
The game loos reaaly nice! Compliments!

[EineTasseKaffee]

Hi.

I have an idea:
We could make a competition of Glest documentation.
Everyone who wants to write a doc how to play Glest could post it maybe here or we make a new tread and the best will be taken as an "official" Glest manual, which is part of the next Glest release.

[crusadingknight]

Hi.

I have an idea:
We could make a competition of Glest documentation.
Everyone who wants to write a doc how to play Glest could post it maybe here or we make a new tread and the best will be taken as an "official" Glest manual, which is part of the next Glest release.

DocBook format?

[EineTasseKaffee]

Hmm, thats a good question.
A "Getting started" could be done in a *.txt file, but a 'real' doc shouldn't be done as *.txt .
It's a question what kind of doc is needed. People who played Warcraft or C&C or some other real time strategy game will be able to handle Glest without any help, i think.

We should ask some developer, what kind of doc they want to have and IF they want it to be part of the next release....

It's only an idea now, but I allready started working.
I'm sure, they would publish ANY documentation as an "additional download" if its good (they would be foolish if the do not).

But it would be an extra motivation if we could make a competition and the best one could be the 'official' Glest doc, part of the Glest package like the "readme.txt" .

[Speedator]

I think uisng a wiki would be a adequate solution.
The new user can read the wiki or we also make a downloadable compendium, which will be updated once in a wihle, based on the wiki.

[Ka]

yes, wiki, oh wiki, good old wiki.
(ahm, i dont have the actual need for a documentation, but i like wikis, oh wiki.)
ka

[crusadingknight]

Hmm, thats a good question.
A "Getting started" could be done in a *.txt file, but a 'real' doc shouldn't be done as *.txt .
It's a question what kind of doc is needed. People who played Warcraft or C&C or some other real time strategy game will be able to handle Glest without any help, i think.

We should ask some developer, what kind of doc they want to have and IF they want it to be part of the next release....

It's only an idea now, but I allready started working.
I'm sure, they would publish ANY documentation as an "additional download" if its good (they would be foolish if the do not).

But it would be an extra motivation if we could make a competition and the best one could be the 'official' Glest doc, part of the Glest package like the "readme.txt" .

That's why I recommended DocBook.  

[shirishag75]

Hi guys,
         Just started playing this game, even though I've played AOM & AOE lots of times, there are differences in game play, in the way they move & attack & lots of big & subtle differences. I think we should start a wiki. Some very basic stuff we can plough on are:-

1. Configuration :- Although the auto is the best, but still for lower spec config or on-board graphics what will be better.

2. Game-play:- I hardly played for 1/2 hr. as came to know that there is day/night condiition. Before that had to reconfigure my comp. so it plays good. Now either there should be a manual which explains or an in-game tutorial which tells a newbie, a la AOM.

  I know that as this is an Free/Open-Source project, it would be unfair to ask of any support or something but I'm sure like me there would be lot of guys who would 've spent quite a bit of time understanding what works & doesn't by simple trial & error. By making some documentation on the wiki it would be great idea to have a transparent understanding both from the user as well as the developer's sense. It's a two-way street. Having a manual makes it much more polished & then can seriously tell my friends to go ahead with it.