This is a draft. Unapproved and not enforced, to be submitted to the directors for approval before being acted on. This is simply to revise the rules before submission. This is also not a GraalOnline policy at this time.
Source:
http://forums.graalonline.com/forums...ad.php?t=49824
---
Rules for ALL servers
These rules apply to all worlds regardless of popularity.
It is the manager’s responsibility to make sure these rules are followed, and if they are broken some punishments are:
-Being made Private
-Shut Down
-Disable playerworld for a set period of time
-Revoking free hosting (Classic worlds)
-Banning people who break rules
-Replace of manager
-Banning from being public for a period of time.
These need a lot of working-through, some of these require authority not available to the PWA and couldn't be actively managed.
Manager's Role:
-Responsible for enforcing these rules and making their staff aware of changes.
-Enforce and comply with the GraalOnline User Agreement (e.g. dealing with anyone who deserves it according to the agreement)
-Govern their staff, and must be aware of all RCs/rights given out.
-Responsible for server content, and should limit uploading to "live" areas of the world.
File Manager:
Do not upload anything into the file-manager that you do not have permission to upload. Additionally, no inappropriate or copyrighted material should be uploaded.
Do not use content that has been uploaded elsewhere on Graal without the consent of
both the creator and the manager of the original world.
NO music files should be uploaded to the playerworlds file-manager. It is difficult to prove who created music so music should be hosted on a private web-server and played with the command "play". (e.g.:
play
http://www.host.com/song.midi;)
Staff:
All staff positions should be have an exclusive purpose. For example, you do not need someone to upload heads when the manager or graphics admin can do this.
Staff should be given training on how to use any RC rights they have and the responsibilities of their job. If they don’t know how to use a certain thing, limit how they can use it until they learn. The manager is responsible for all staff's actions regardless of that staff member's experience.
Each staff member should have their rights given to them individually. Any rights given must be needed and fit their position.
Only managers should have level 4 RCs. The manager should be active to perform tasks that can't be done without level 4 rights. A second level 4 RC can be given to the highest positioned admin, but only if needed (e.g.: timezone conflicts).
No playerworld should have more than 3 level 4 RCs total. A third level 4 RC can be given to the Admin-Playerworld## or Admin-ClassicWorld account only.
No playerworld should have more than 3 level 3 RCs. For any task requiring level 3 rights a staff can ask a level 3 or 4 RC to do it.
All RCs should have an IP range defined to limit unauthorized access to the RC account. See Security.
Only managers are allowed to add RCs. The managers may also allow one other staff member to edit rights, if this person is trusted and their job role allows them such responsibility. E.g.: Assistant Manager
Staff should never PM or Mass Message offensive material. They should also not have offensive material in their profile.
Local Server Rules:
All playerworlds should a posted set of local rules for their world. These rules should comply with the GraalOnline agreement.
RCs:
RC should ONLY be given to those who need it.
For example, FAQ and Events staff do not need RC as they are in-game positions only. Duties such as adding/fixing events are the NAT's and LAT's responsibility. Adding new FAQ/ET members, as well as any staff tools like "boots", should be done by the manager.
Any RC in the "staff=" server-option should be an active staff member. Honorary RCs are forbidden.
Guests who help with temporary problems or projects should not be left in the staff list, nor with any rights in their account as they are often used to attack a playerworld.
Invisible and closed off playerworlds do not need staff such as FAQs or GPs and should not have any until they are visible. When they are visible as "Hosted" they should only have these staff if the playercount warrants it.
Security:
Only managers should have full rights RCs for security reasons.
Do not give out rights if they are not needed... If a staff member doesn’t use a right for their job, they don’t need the right.
Nobody other than the manager should have rw access to any important logs such as rclog.txt
NPCs should be used to substitute RC actions (e.g. warpto) where possible. These should be secure (e.g. account and guild checking).
NPCs should not be used to substitute RC rights if they can’t be made secure.
ALL RCs need an IP range set. This can be no less than two numbers. e.g:
12.34.*.*
Managers should limit the amount of people who have ‘rw’ (read & write) rights to "live" folders, the folders current downloadable levels are in. Management should transfer files into "live" folders from non-live staff folders after checking them.
NPCs:
NO NPC Should be abusive such as changing players names, changing players looks etc. IF you really need this then it should have security measures such as account and guild checking, and the NPC
must log all users' actions.
All NPCs must be created for your world or you should have permission to use them.
Bans:
All bans must be for a clear reason. You can not just ban someone because you dislike them.
Players should be warned and go through some sort of punishment system before a ban, such as warning, then jail. Big offenses such as disruptive behavior affecting the whole playerworld do not need a warning first. However it is suggested you use the jail before a ban.
Players using trainers can by banned on first offense if there was obvious cheating. Messages from the server that "player is using cheat tool:" should be verified by staff in game whenever possible.
Bans comments should include the following: Reason, Account (if PCID ban), and the banning staff member. If there isn't enough information to verify a ban that is questioned, the player may be released.
Because bans are often done for incorrect or wrong reasons only people with level 3 or 4 RCs should be allowed to ban. This means that 5 people (MAX) should be able to ban.
Guilds:
Do not make guilds that mimic any special or global staff guilds (e.g.: GM, VIP)
Do not make local guilds that are the same as global guild names.
No guilds should be offensive, allow players to be in the staff list, or have copyrighted names.
Trial Accounts:
No playerworld under any circumstances should save trial account data.
Trial accounts are accounts that allow the user to see and test the game on their computer system. Graal does not allow trial accounts to gain items/stats easier than paid accounts.
Playerworld Websites:
If you link to your playerworlds website all content found within your website must fall within Graal's rules and there must be no offensive or illegal material. This includes links out of your website.
Reviving A Playerworld Project:
Any files uploaded into the file-manager becomes the sole property of GraalOnline. When a player works for a playerworld as a 'Staff' member all files given to the manager to upload, or uploaded themselves, becomes property of GraalOnline. Temporary usage rights (until shutdown of a playerworld) is given to the playerworld manager while the playerworld is online. This right of usage is terminated when the playerworld is shut down. If someone wants to use any of the files again (i.e.: Playerworld Revive Project) Graal and its representatives must be contacted before they can be uploaded again. To gain usage rights to any Playerworld previously online, the individual must contact Graal's representative and the last active manager(s) to gain permission and usage rights to the files of a shutdown Playerworld.
Any scripts with ‘NPC Made By ’ need separate permission for their usage. If any file, like a graphic, is being used elsewhere you also need permission from the creator and any playerworld using it. This also applies if the filename contains a player’s name: e.g. player_gfx1.png
Need two posts 
12-13-2006, 08:34 AM
Hybrid Mode
