Names
All character names on the Empire of the Blue Lotus should fit the theme. Hints, helpfiles, and links to baby name sites are provided on the website. Names should not be derived from western names, names famous in fiction, legends, mythologies, cartoons, or anime.
Staff files are exempt from this rule as they are not part of the in character world, though the player characters of staff members are expected to abide by it.
Player Rewards: QPs and RPPs
These basic guidelines may be awarded a number of points at the discretion of the staff.
RP Points (amount at discretion of the staff based on the actual RP submitted)
Note players may submit their RP for consideration themselves:
- excellent level of RP
- willingness to RP with a wide range of other characters
- a strict adherence to the personality and demeanor of the character
- participating in RP they happen to be around during rather than being passive
- consistent involvement in RP
- participation in RP events for the MUD as a whole
- designing activities and events for small groups
- designing activities and events for the MUD as a whole
QPs (amount for some dependant upon quality of work or approval):
- filling out a character background
- participating in MUD RP events
- participating in quests
- reporting bugs and typos
- submitting ideas for skills and spells
- submitting other ideas to improve the MUD
- submitting original fan art (must be hosted elsewhere)
- submitting original fan art (must be hosted elsewhere)
- ASCII
- Pixel art
- Sketch, black and white
- Colored sketch
- Cel art
* submitting fan writings
- poems
- short stories
- fables/myths
- character fan fiction
- working as a builder to design, create, develop, and improve the MUD’s areas
Both qps and rpps are taken into consideration and used to purchase certain advantages including:
- stat enhancement
- access to restricted high tiered skills and spells
- permission to play certain restricted application characters
Application Characters
Certain types of characters, by virtue of the privileges that come with them or their rarity in the game world, are restricted and played only by those granted permission from the policy staff, and no one may have more than one at a time, or take one of these roles if already a guild leader.
Application form found here.
Permissible RP
Out of respect for the emotional impact of such situations, there will be no role-play of rape or suicide on the Empire of the Blue Lotus. Those engaging in such role-play will be subject to removal from the game for a period of time determined by the policy staff.
Out of respect for the administration’s desire to maintain a predominantly family-friendly atmosphere, there will be no mudsex or role-play of excessively compromising positions. These situations can always be left at “we all know what happened next” on the screen. Those engaging in such role-play will also be subject to removal from the game for a period of time at the discretion of the policy staff.
Bug Abuse
Any bugs, glitches or problems in the code, are to be reported immediately so that they may be fixed quickly. Abuse of a bug is subject to punishment at the full discretion of the programming staff, ranging from loss of any unfairly gained benefits up to and including permanent removal from the game.
Code Abuse
Abusing any facet of code to gain any benefit for a character by means other than the accepted methods of practice, training, skill use, spell use, and role-play is subject to punishment at the discretion of the programming staff, ranging up to and including permanent removal from the game.
Playerkill Policy
A character who meets their death at the hands of another player will be given the choice to simply accept the outcome and immediately create their new character, or contest it and have their concerns heard by a member of the policy staff. A decision will be made regarding the validity of the death, and the character will either be returned to the game or asked to create anew as a result. In making the decision, the burden of proof is on the killer to clearly display that their actions meet the requirements for a valid playerkill. Logs are always welcome and helpful.
To be validated, a playerkill must be:
- attempted for in character reasons. Revenge for the death of the killer’s previous character or alt is not permitted as a reason, nor any other reason that does not directly relate to what the involved characters have done through role-play.
- roleplayed. Attack upon entry/ambush can still have the role-play of a brief demand “Your coin if you value your life,” or something similar to make it clear an attack is imminent or pending. A deadly ambush with no immediate warning must be clearly supported by prior role-play.
Spam
It’s a food, not something to do. In general, spam refers to repeatedly sending the same input to the MUD in a very short period of time.
- Spamming through the various forms of MUD communication channels will result in loss of the ability to use those channels.
- Skillspam and training spam, any form of circumventing the limits code places upon the proper times and places for either, is punishable by loss of any skills, spells, or stats gained or improved by so doing, and other punishment at the discretion of the programming staff.
- Creation spam, creating multiple characters in a very short space of time and taking advantage of their abilities in any way, is subject to punishment ranging from deletion of the offending new files to deletion of all files or temporary removal from the game.
Proper Channel Usage
Flaming and vulgar, offensive, rude or foul language from one player to another on any channel will result in having all means of communication and role-play withdrawn from that player. Keep it clean.
Circumventing language censor code on the various public channels will be punishable by loss of the abused channels.
Repeatedly asking the staff for various favors is considered harassment. Staff is expected to be completely neutral, which is made more difficult by pressure.
Botting
The use of scripts, triggers, and other forms of botting designed to allow the player to accrue in-game benefits without actively earning them is not permitted on the Empire of the Blue Lotus. Save triggers are permissible, as are login scripts and other forms that do not affect game play.
Guild Leaders/Guild Policy
Guild leaders are expected to give enough time to the game to adequately perform their role and duties. Should they be unable to for a long period of time, they are expected to speak with the staff to arrange a temporary substitute during their absence. Should unexpected and sudden conditions arise, it is asked that they notify staff as soon as it becomes possible. If it becomes necessary to remove them from their position due to absence, circumstances will be taken into account when making the decision regarding their reinstatement upon their return.
The guild leader is responsible for keeping track of the membership of their guild, and for maintaining the flow of proper advancement through the guild ranks where applicable.
Entrance into a guild is based upon role-play. Guild leaders are expected to show no favoritism for out of character reasons, though in character based favoritism is acceptable, such as favoritism towards members of the guild leader’s own clan. Likewise for raising or lowering a person’s ranking, or removing them from the guild, which are expected to most often be done according to the guidelines for typical advancement and the guild’s code of conduct.
Staff Policy
- Staff members are expected to uphold the rules when logged on as any character they possess, and encourage others to do the same.
- Staff is expected to be productive with their staff profile. If unable, they may be asked to step down from their positions
- Staff is expected to remain friendly and courteous to all players. Favoritism is to be avoided. This includes any form of assistance to the staff member’s player characters, or using information learned through the staff file to help the player characters.
- Interaction with the players will always be out of character, and should be limited. There should be very little reason to go to a player in role-play, as discussions can be held in tells or by transferring the player to the staff member.
- When transferring a player, always ask their permission or warn them ahead of time, allowing them the chance to reasonably extract themselves from the role-play they may have been involved in.
- The roles of each staff member should be filled only by the appropriate staff member(s).
