Design Documents?

[FrikaC]

[Entar]

I probably would if I ever did a really big modding project, but thus far I've only done smaller stuff.

[RenegadeC]

For Envenom I did, TAoV was just built by suggestions by others and my own ideas and twists on established ideas. Generally, no I don't make design docs.

[HeadThump]

I have about a dozen notebooks full of detailed discriptions and drawings of maps, monsters, NPC's, puzzles, tricks, and story lines for mods for Quake, Thief, Deus Ex, NOLF, Doom 3 and stand alone TC's.

I also have dozens of prototyped maps and models on my hard drive.
As compulsive as that sounds I really sift through my material patiently until things comes together in interesting ways.

edited: Just noticed that this is in the coding section, so related to code documentation specifically -- errr - awkward

[Pulseczar]

my list is basically just reminders of what needs to be done, granted that I haven't done any big QuakeC projects yet..

[FrikaC]

[Sajt]

[ajay]

[SkinnedAlive]

[MauveBib]

[Dr. Shadowborg]

[leileilol]

[Quake Matt]

[Tei]

[spamalam]

If I was making my own mod from scratch (I only just looked at a modding quake a few months back and have done a little bit of playing, decompiled an old but not well known mod and have picked up and made a few changes), I would document it.

Whenever I start a Java project i'll use some UML diagrams, and obviously get to a design level class diagram. For QuakeC... meh, I've not done anything big enough, or infact a project from scratch to warrant it. That said i probably would.