Graal Communication Center/Playerworld Rules: Difference between revisions

From Graal Bible
No edit summary
m (Updated Rules for Playerworlds - 11/16/2011)
Line 1: Line 1:
[[Category:Creation]][[Category:Forums]]
[[Category:Creation]][[Category:Forums]]


All Graal servers are bound by a set of rules to ensure that players are kept in a safe and friendly environment. Servers which fail to keep to these rules may find themselves being punished, including the possible removal of their Classic/Hosted status or even being shut down completely.
'''Hosted/Classic Requirements:'''


* Managers are responsible for ensuring that their server follows the 'Rules for Classic and Hosted Servers', the '[http://www.graalonline.com/docs/agreement.php  'GraalOnline User Agreement 1]', and the [http://www.graalonline.com/accounts/rules.php 'GraalOnline User Agreement 2'] as well as the [http://www.graalonline.com/accounts/rules.php 'GraalOnline Acceptable Use Policy'.]
The purpose of this document is to clearly and definitively state what the requirements are to become a Hosted or Classic server and their respective criteria.  
* Managers are responsible for all content available on their server, and should ensure that nothing is made available to players that breaks these rules.
* Managers are responsible for ensuring that their staff behave professionally and within the rules at all times.


'''Hosted Requirements:'''
Hosted status is given to servers that are awaiting approval Classic status. The Playerworld Administration uses the Hosted status as a way to get players involved in determining whether or not the server will be effective if it is to be approved for Classic status. This will help Graal’s administration is determining whether or not a Hosted server is to be approved for Classic status.


Managers should be proactive in their role, and if they are found ignoring or not enforcing these rules, they may be forcefully removed from their position.
1) The server pending approval from the Playerworld Administration for Hosted status must have the following: Quality content (graphics, levels, scripts, etc…)Some player entertainment (the intention is to bring players onto the server, thus it is necessary to have some playable content)
Having an established or the means of establishing a stable staff team
Have an original concept/storyline.


In addition to these rules, servers should outline any further rules specific to their server and make these easily available to players.
2) You must accept and follow the rules for Playerworlds outlined in (http://forums.graalonline.com/forums...ad.php?t=84379). If the server is approved, the server manager accepts and will enforce the rules outlined in that document. Failure to do so will result in immediate termination of Hosted status, and depending on the severity, further punishment may occur.
Hosted servers will be constantly reviewed by the Playerworld Administration. The Playerworld Administration will be looking for a constant flow of development and an active administration. If it is observed that the server is in a state of stagnation, a warning will be given to the server’s administration, and if nothing is done to change the current status of the server, the server’s hosted status will be terminated.


Files and Content
'''Classic Requirements:'''


* No copyrighted material should be used on the server, and any content found to break copyright should be removed immediately.
Classic status is given to servers who are on the hosted server list and are successful. Successful is defined in terms of the average amount of players that play the server and a clear distinction from other Classic servers, making it a unique and entertaining server.
* No content of a graphic or adult nature should be used on a server. All content should be age appropriate and not offensive in nature regardless of background.
* Any websites linked to on the server should be free from graphic or adult content.
* Servers which host their own radio stations should ensure that all sounds produced from the radio are suitable for all ages and do not feature any excessive swearing or graphic depictions.
* Servers should not steal content or ideas from other servers.
* With the exception of global content, all server-specific content (e.g. local levels, graphics and scripts) are to be used only on the server they were submitted to, unless it is permitted otherwise.
* Any player-centric content, such as head, shield and sword graphics, may be uploaded to multiple servers, but only with the express permission of the original artist.
* All files uploaded to a server immediately become the property of GraalOnline. Usage rights are granted to the server on which the files were uploaded. Consequently staff may not remove any of their work from the server upon quitting or otherwise leaving their position.
* All data held on GraalOnline servers is subject to loss or corruption at any time. It is the responsibility of the server staff to ensure that data is backed up adequately.
* Servers on the Classic (Playerworlds) list may not reset all of their users' account data without prior approval from the PWA.  


Staff
1) The servers pending approval from the Playerworld Administration for Classic status must have the following:
Have an adequate amount of playable content to keep players on the server for an extended amount of time
A clear, unique concept that will make an asset to servers listed under the Classic status
Is GS2 compliant
A competent administration


* All staff should be aware of, and abide by, the 'Rules for Classic and Hosted Servers', the 'GraalOnline User Agreement', and the 'GraalOnline Acceptable Use Policy'.
2) You must accept and follow the rules for Playerworlds outlined in (http://forums.graalonline.com/forums...ad.php?t=84379). If the server is approved, the server manager accepts and will enforce the rules outlined in that document. Failure to do so will result in immediate termination, and depending on the severity, further punishment may occur.
* All staff positions should serve a genuine purpose. Honorary staff roles such as 'Founding Staff' or 'Original Creator' are not allowed.
* Staff positions should not be created for minor tasks such as uploading player graphics without special permission from the Playerworld Administration. These tasks should be handled by appropriate existing staff. For example, graphic uploading could be handled by the Graphics Team.
* Staff tags should clearly identify the role of the staff, and where appropriate, indicate if that staff member is a trainee or administrator.
* All staff tools should be created in a fashion that cannot be abused. For example, a tool to change offensive nicknames should simply set that player's nickname to their community name, rather than allowing for the staff to enter a new nickname.
* Staff should only be given access to the rights and tools required by their position. This includes access to RC. Before being given a right, staff should be trained in its usage.
* Staff should only use their rights and tools for the reasons required by their position. Any other use is considered abuse, even if it does not directly affect players in a negative way.
* All RC access should be restricted by IP or PCID to prevent unauthorised login.
* Only the staff positions Server Administrator and higher should be given full rights on RC. Please take note that full rights should be given sparingly.
* Write and delete file access should be restricted from staff as much as possible. Where relevant, staff should be given their own folder to work in rather than having write access to the main levels folder.
* Only the server Manager should have write access to server logs.
* All staff with RC access override players options to ignore mass messages. These staff should restrict their massing only to important server information.


Once a server attains Classic status, the administration will be under constant observation from the Playerworld Administration. In addition, all managers of Classic servers will have to follow Classic-related rules set forth by the Playerworld Administration. Failure to do so will result in possible termination.
(Note: All current Classic servers will remain Classic even under the new definitions.)


Local Guilds
Both the Playerworld Administration and Stefan determine whether or not a server meets these requirements.
 
* Guild names should not impersonate any privilege or staff guild (such as 'Playerworld Administrator' or 'VIP').
* No local guild names should replicate any global guilds names.
* Guild names should not contain any offensive, copyrighted or threatening material.
* No guild should allow players to appear in the staff list if the guild is not an official position on the server.
 
 
System Abuse
 
* No scripts should allow one player to imitate another, for example by changing their nickname to '*Stefan'.
* Scripts should not interfere with any built in part of Graal, such as preventing the auto-disconnect for idling from working.
* Scripts should only identify players uniquely via their account name, nickname or community name. Any other attempt to track a player such as through their IP address, PCID or by planting corrupt files in their system could constitute a criminal offence. Servers are strictly forbidden from using any sort of method to store or retrieve the player's IP address or PCID with script.
 
 
GraalOnline reserves the right to make special-case amendments and additions to its rules and policies and the steps it takes concerning violation of these policies and rules. Players are required to keep up-to-date with any changes to Graal policy concerning rules and gameplay by checking them frequently. To keep users aware of any amendments they will be posted in the GraalOnline communication center forums, under the section 'PlayerWorlds Main Forum'.




External Link: [http://forums.graalonline.com/forums/showthread.php?t=84379 Rules for Playerworlds]
External Link: [http://forums.graalonline.com/forums/showthread.php?t=84379 Rules for Playerworlds]

Revision as of 11:46, 19 November 2011


Hosted/Classic Requirements:

The purpose of this document is to clearly and definitively state what the requirements are to become a Hosted or Classic server and their respective criteria.

Hosted Requirements: Hosted status is given to servers that are awaiting approval Classic status. The Playerworld Administration uses the Hosted status as a way to get players involved in determining whether or not the server will be effective if it is to be approved for Classic status. This will help Graal’s administration is determining whether or not a Hosted server is to be approved for Classic status.

1) The server pending approval from the Playerworld Administration for Hosted status must have the following: Quality content (graphics, levels, scripts, etc…)Some player entertainment (the intention is to bring players onto the server, thus it is necessary to have some playable content) Having an established or the means of establishing a stable staff team Have an original concept/storyline.

2) You must accept and follow the rules for Playerworlds outlined in (http://forums.graalonline.com/forums...ad.php?t=84379). If the server is approved, the server manager accepts and will enforce the rules outlined in that document. Failure to do so will result in immediate termination of Hosted status, and depending on the severity, further punishment may occur. Hosted servers will be constantly reviewed by the Playerworld Administration. The Playerworld Administration will be looking for a constant flow of development and an active administration. If it is observed that the server is in a state of stagnation, a warning will be given to the server’s administration, and if nothing is done to change the current status of the server, the server’s hosted status will be terminated.

Classic Requirements:

Classic status is given to servers who are on the hosted server list and are successful. Successful is defined in terms of the average amount of players that play the server and a clear distinction from other Classic servers, making it a unique and entertaining server.

1) The servers pending approval from the Playerworld Administration for Classic status must have the following: Have an adequate amount of playable content to keep players on the server for an extended amount of time A clear, unique concept that will make an asset to servers listed under the Classic status Is GS2 compliant A competent administration

2) You must accept and follow the rules for Playerworlds outlined in (http://forums.graalonline.com/forums...ad.php?t=84379). If the server is approved, the server manager accepts and will enforce the rules outlined in that document. Failure to do so will result in immediate termination, and depending on the severity, further punishment may occur.

Once a server attains Classic status, the administration will be under constant observation from the Playerworld Administration. In addition, all managers of Classic servers will have to follow Classic-related rules set forth by the Playerworld Administration. Failure to do so will result in possible termination. (Note: All current Classic servers will remain Classic even under the new definitions.)

Both the Playerworld Administration and Stefan determine whether or not a server meets these requirements.


External Link: Rules for Playerworlds