Talk:Successful Mod Team Tips: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
* Thanks Tim - I'll add my comments from projects i have been involved in. --[[User:Amckern|Amckern]] 03:49, 29 Dec 2005 (PST) | * Thanks Tim - I'll add my comments from projects i have been involved in. --[[User:Amckern|Amckern]] 03:49, 29 Dec 2005 (PST) | ||
:[http://www.igda.jp/modules/mydownloads/visit.php?cid=2&lid=42 Robin Walker's presentation] contains tips for teams. | |||
*Small as possible | |||
**Focus on production | |||
**Avoid management | |||
**Don't hire anyone until you're about to fail | |||
*Scope design by resources | |||
**Don't grow the team to fit the design | |||
:I myself still believe in one person mod(from [[Garry's Mod]] to latest [[Mistake Of Pythagoras]])...carefull design can make it possible and it can still deliver a new experience.--[[User:N-neko|n-neko]] 05:45, 29 Dec 2005 (PST) | |||
Revision as of 06:45, 29 December 2005
This is a rough draft of what I hope can be a good set of pointers and tips about what makes a good mod team. Tell your stories both good and bad! --Holtt
- Thanks Tim - I'll add my comments from projects i have been involved in. --Amckern 03:49, 29 Dec 2005 (PST)
- Robin Walker's presentation contains tips for teams.
- Small as possible
- Focus on production
- Avoid management
- Don't hire anyone until you're about to fail
- Scope design by resources
- Don't grow the team to fit the design
- I myself still believe in one person mod(from Garry's Mod to latest Mistake Of Pythagoras)...carefull design can make it possible and it can still deliver a new experience.--n-neko 05:45, 29 Dec 2005 (PST)