[warlord]

I would like to see them as well.

[Flyby]

Originally Posted by DeeZire

I could post up the programmers docs that were used in development, but its time consuming as they are all in Excel format and changed many times. At least that way the list would be conclusive and would include things not used in Generals or ZH.

Flyby started on such a list also I believe.

Correct! Only it is just a detailed listing, and does not (yet) explain from A to Z..
And when I was just about finished, they've added Zero hour... :/
So I’m now in the process of listing all new behaviors they've added.

Then I'll need to go over all the Behavior tags again, because I noticed they've added new tags on older Behaviors.
The ZH additions will be in a different color, so they are easy to spot.

So much work, so little time....

I'll make the list available as soon everything is updated again...k?
If you only need the Generals Behavior tags, i can reorganize is it a bit and make it public right away... your call

[warlord]

All I can say is good work and would be a nice addition to any modders sources

[CodeCat]

It's done! Get it here!

[Flyby]

Shame we didn't know of each other, we could have worked together on this... :/

What if we join both listings?
You made an alphabetic listing with detailed discriptions, I grouped them according type/usage with pratical samples.
You're more detailed on the discriptions, but the document lacks a bit in readability..
If we join both listsings, I'm convinced we'll get a better document...

[warlord]

That would be good that you 2 joined since it could make it go faster to get it completed.

[CodeCat]

Well, joining forces seems like a good idea to me.

Your file just lists all the modules and parameters, while mine has descriptions as well. But yes, yours is a bit easier to read, and the examples make it easier to understand. The unreadability part is because I did mine in TXT format (and was therefore bound to the limitations of that format) to make it available to more people. DOC format is not as common as you might think. However, we could do both TXT and DOC. And about the alphabetical order, I just did that because it seemed the most obvious. My list was intended as something to "look up" a particular module, and that's where alphabetical lists are most usual. However, I included a simple list of modules as well, so we could make an alphabetical one (like mine) and another by type. And then group the explanations by alphabet. That would make it easier to read and look up.

[Flyby]

I've also considered setting it up alphabetically, but instead of a reference document, I wanted it to be a practical guide while modding.
We should use a HTML based document, so we can use hyperlinks.

I think we should keep both overviews, one according the alphabet, one according type.
Then use hyperlinks to jump to the topic, use my list as example and put your detailing under it.

as for the *.doc format :
everybody who runs windows, has wordpad. My file was made in wordpad, and not in MSWord.

[CodeCat]

HTML sounds like a good compromise. It has the formatting advantage that DOC also has, but can be viewed by lots of people like TXT format. But I'm not great at HTML myself (can do the basics but no PHP or anything), and I'm absolutely useless at visualisation and graphics.

But with HTML we could use two summaries, one by alphabet and another by category, and each of the names has a link under it that links to the relevant explanation. The explanations could be spread along several HTML documents, by category.