Top Mud Sites Forum - View Single Post

Turxx · 01-20-2013, 08:02 AM

General Guidelines of Staff Conduct

Initial ideas for the world are:
Worldmap for navigation between zones
Allows for expansion of system including vehicles, etc
Heavily quest and story orientated progression
Keeps players involved to see advancement of a story
Heavy usage of scripting to create a “living and breathing” world
To not take out any stock zones, but redesign them to fit our environment
Keeps content high
Keeps mud-stats high
Allows some familiar zones for those who have affectionate memories of some of the stock zones
The goals for Beta in mechanics and code have already been established. The allowance for change in direction is limited due to time-related goals. After Beta, major changes in system CAN be considered.
Very simple to understand the mechanic goals: view any d20/DnD3.5 rules website to get the idea
The lead designer is choosing what to implement and what not to implement based on
Ease
Past experience on what systems work
Fun-factor
Ideas coming from the staff should be well thought out to avoid clutter. If you have a lot of ideas, it’s best to start a Forum-Topic and post them under your topic, then go to town
Bugs and Typos do NOT need to be thought out at all, if you even slightly think something is a Bug/Typo, do not be afraid to report it
Builders or Builder’s Leadership should NOT try and change the standards and system established by TBA – that would destroy our primary community of potential builders.
One of the big advantages of using TBA codebase is the active community
It’s OK to discuss with other leadership ideas in their field of leadership, but remember whose field of leadership it is… and AVOID arguing if that leadership makes a decision; exampes:
If you are the Lead Designer or Lead Builder, don’t try to trump the Lead Admin (for example in establishment of in-game player-to-player rules)
If you are the Lead Designer or Lead Admin, don’t submit lore or content that isn’t consistent with the Lead Builder/Lore
If you are the Lead Builder/Admin, don’t try to insist on game mechanics or design of OLC interface, etc
Try to be at least a little respectful and sensitive to any individuals who are committing a lot more of their effort/work into the MUD
Do NOT take other’s time for granted, if you ask a coder to do something that takes 10 hours of his time, you should be prepared to do that much work in return for the coder
Although the Lead-Designer does tend to heavily implement ideas submitted by the community, the default expectation is quite simple: we do NOT customize the MUD to individual preferences.
Leadership positions individuals are expected to lead by example
Life comes first, but if you can’t handle the responsibilties and time investment of leadership, you should try to find a replacement
ANYONE has a right to request the code
ANYONE can request a copy of their zone at any time, but see the on-line DISCLAIMER help file for details on the MUD’s rights with the builders zones
REMEMBER: Ultimately, if push comes to shove, the owner does have a right to trump decisions that aren’t in-line with the initial vision. Or if he knows the idea to be ineffective base on past MUDding experience.

01-20-2013, 08:02 AM	#2
Turxx New Member Join Date: Sep 2010 Posts: 18	Re: Looking for builders. General Guidelines of Staff Conduct Initial ideas for the world are: Worldmap for navigation between zones Allows for expansion of system including vehicles, etc Heavily quest and story orientated progression Keeps players involved to see advancement of a story Heavy usage of scripting to create a “living and breathing” world To not take out any stock zones, but redesign them to fit our environment Keeps content high Keeps mud-stats high Allows some familiar zones for those who have affectionate memories of some of the stock zones The goals for Beta in mechanics and code have already been established. The allowance for change in direction is limited due to time-related goals. After Beta, major changes in system CAN be considered. Very simple to understand the mechanic goals: view any d20/DnD3.5 rules website to get the idea The lead designer is choosing what to implement and what not to implement based on Ease Past experience on what systems work Fun-factor Ideas coming from the staff should be well thought out to avoid clutter. If you have a lot of ideas, it’s best to start a Forum-Topic and post them under your topic, then go to town Bugs and Typos do NOT need to be thought out at all, if you even slightly think something is a Bug/Typo, do not be afraid to report it Builders or Builder’s Leadership should NOT try and change the standards and system established by TBA – that would destroy our primary community of potential builders. One of the big advantages of using TBA codebase is the active community It’s OK to discuss with other leadership ideas in their field of leadership, but remember whose field of leadership it is… and AVOID arguing if that leadership makes a decision; exampes: If you are the Lead Designer or Lead Builder, don’t try to trump the Lead Admin (for example in establishment of in-game player-to-player rules) If you are the Lead Designer or Lead Admin, don’t submit lore or content that isn’t consistent with the Lead Builder/Lore If you are the Lead Builder/Admin, don’t try to insist on game mechanics or design of OLC interface, etc Try to be at least a little respectful and sensitive to any individuals who are committing a lot more of their effort/work into the MUD Do NOT take other’s time for granted, if you ask a coder to do something that takes 10 hours of his time, you should be prepared to do that much work in return for the coder Although the Lead-Designer does tend to heavily implement ideas submitted by the community, the default expectation is quite simple: we do NOT customize the MUD to individual preferences. Leadership positions individuals are expected to lead by example Life comes first, but if you can’t handle the responsibilties and time investment of leadership, you should try to find a replacement ANYONE has a right to request the code ANYONE can request a copy of their zone at any time, but see the on-line DISCLAIMER help file for details on the MUD’s rights with the builders zones REMEMBER: Ultimately, if push comes to shove, the owner does have a right to trump decisions that aren’t in-line with the initial vision. Or if he knows the idea to be ineffective base on past MUDding experience.