Advertisement
aggelosQQ

Protocols and Policies

Sep 12th, 2014
243
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.79 KB | None | 0 0
  1. All policies listed in this thread shall be of immediate effect.
  2. Ignorance and intransigent shall not be permitted and if refusal to acquire this policies, please resign forthwith without any form retaliation and or drama.
  3.  
  4.  
  5. Name: "Special Effects information Protocol"
  6. Nicked: 'SEIP'
  7. SEIP, Section 1, part 1 - Administrators and players may not speak in bold, italic, underline, and colored lettering on any pending, application in the process of denial or acceptance, without content and approval of any Executive Administrator that is currently in the position of power to allow this behavior.
  8. SEIP, Section 1, Part 2 - This doesn't limit your ability to post funky coloring and or designs on accepted applications.
  9. SEIP, Section 1, Part 3 - You may not, forthwith and forever more, be allowed to post comments in bold, italic, underline, and colored lettering with/on denied applications.
  10. SEIP, Section 1, Part 4 - You may not post symbols to say something sure as '✔øʊ¢♄' or others on pending application without the approval of any Special Executive"
  11. SEIP, Section 2, Part 1 - Images are prohibited on pending applications without the approval of a Special Executive Administrator.
  12. SEIP, Section 3, Part 1 - 3rd party links debarred unless listed below.
  13. SEIP, Section 3, Part 2 - 3rd party links to utilities sure as Calenders, Timezone Maps, Dictionaries, and others are permitted if deemed to fix in the following situation.
  14. SEIP, Section 3, Part 3 - 3rd party links cannot link onto Search Engines sure as Bing, Google, or Yahoo violate SEIP, Section 3, Part 2 unless if providing information sure as Google's Calculator.
  15.  
  16. Named: "Forbid Rude Comments"
  17. Nicked: 'FRC Policy'
  18. FRC Policy, Section 1, Part 1 - Administrators shall not be allowed to include expletives, profanity, words on applications.
  19. FRC Policy, Section 1, Part 2 - You may exempt the single word "hell" from the classification of profanity on Telnet and Senior application for the single purpose, and the only purpose, of congratulation. An example would be, "Hell yeah! I knew you could become Senior Admin!"
  20. FRC Policy, Section 2, Part 1 - You may not intentional harm and hurt a person or persons feelings, and or status on any applications.
  21. FRC Policy, Section 2, Part 2 - You are still allowed to report any member, but it may not be directly on any application instead in another thread in the appropriate sub-forum.
  22. FRC Policy, Section 2, Part 2 - Stating information which may harm a users status, sure as this user is a griefer, is required to provide clearly identifiable proof.
  23.  
  24. Name: "Administrator Obligatory Grace Period"
  25. Nick: 'AOGP Policy'
  26. AOGP Policy, Section 1, Part 1 - Administrators appointed under SPaS ("Senior Pick a Super"), TPaS ("Telnet Pick a Super"), DPaS ("Developer Pick a Super") or any other policy aren't required evidence for suspension and or removal for the first sixty ('60') days.
  27. AOGP Policy, Section 1, Part 2 - Administrators directly appointed under the server current operator/owner aren't required to wait ninety days for the full status of promotion.
  28. AOGP Policy, Section 2, Part 1 - New Super Administrators ("Super Admins") aren't required evidence for suspension and or removal for the first thirty ('30') days.
  29. AOGP Policy, Section 3, Part 1 - Telnet applications are required a twenty ('20') day pending period regardless of objections and vouches.
  30. AOGP Policy, Section 4, Part 1 - Senior applications are required a thirty two ('32') day pending period regardless of objections and vouches.
  31. AOGP Policy, Section 5, Part 1 - Any promotion, besides direct appointments from Craftersmith12, are able to be revert with agreement of eighty five ('85') percent of Special Executives agreeing with the requirement of 1 System Administrator recommended the removal.
  32. AOGP Policy, Section 6, Part 1 - Any and all players ("OPs") will be required to wait a minimum of 30 days before applying for Super Administrator
  33. AOGP Policy, Section 6, Part 2 - Any and all Super Administrator will be required to wait a minimum of 15 days before applying for Telnet Administrator
  34. AOGP Policy, Section 6, Part 3 - Any and all Telnet Administrator will be required to wait a minimum of 26 days before applying for Senior Administrator
  35. AOGP Policy, Section 6, Part 4 - Any and all Senior Administrator will be required to wait a minimum of 42 days before applying for Special Executive ("Forum Moderator")
  36. AOGP Policy, Section 6, Part 5 - The waiting period will be nullified if a Special Executive administrator or above recommends his/her for the following rank.
  37.  
  38. Name: "Administrator Crew Creation Standardizes"
  39. Nick: 'ACC Standards'
  40. ACC Standards, Section 1, Part 1 - Any Administrator Crew(s) ("Helper Crews") made before July, 2014 are exempted all standardizes proposed by 'ACC Standards'
  41. ACC Standards, Section 2, Part 1 - Any Administrator Crew ("Helper Crew") found in violation of his/her own policies may be warned up to, but not limited to, termination.
  42. ACC Standards, Section 3, Part 1 - Any Administrator Crew asking for private information is required to ask an {Special} Executive and or System Administrators regarding if this information may be asked.
  43. ACC Standards, Section 3, Part 2 - Any Administrator Crew requesting private information is required to state this is optional.
  44. ACC Standards, Section 3, Part 3 - Any Administrator Crew requesting age isn't allowed to ask for what day of birth. However, Year, and month is perfectly okay.
  45. ACC Standards, Section 4, Part 1 - Administrator Crew are not allowed to discriminate against age, gender, location, time zone, etc.
  46. ACC Standards, Section 4, Part 2 - Although age discrimination is not tolerated, age restriction(s) are allowed.
  47. ACC Standards, Section 5, Part 1 - Administrator Crews ("Helper Crews") may only be created by Telnet Administrators with a Senior Administrators backing the Crew.
  48. ACC Standards, Section 5, Part 2 - Telnet Administrators creating a Crew are required to be a registered member of FreedomOP's forum for a minimum of 46 days.
  49. ACC Standards, Section 5, Part 3 - Telnet Administrators creating a Crew are required to be a Telnet Administrator for a minimum of 23 days.
  50. ACC Standards, Section 5, Part 4 - Telnet Administrators creating a Crew are not permitted to have swear words (cussing) on the application template/format
  51. ACC Standards, Section 6, Part 1 - Administrator Crews ("Helper Crews") are required to train user(s) of the following crew.
  52. ACC Standards, Section 6, Part 2 - Failure to train members of the Crew may result in seizure of the crew, up to permanent termination.
  53.  
  54. Name: "Common Ground Rules"
  55. Nick: 'CGR Rules'
  56. CGR Rules, Section 1, Part 1 - Griefing as defined in "CGR Rules, Section 1, Part 1b" will not be tolerated from user nor administrator and is a ban-able to perm ban-able offence.
  57. CGR Rules, Section 1, Part 1b - "Griefing" is the act of purposefully adding, removing, or otherwise changing of any block, blocks, entity, or entities in the attempt to cause damage or otherwise unpleasant appearance or process of any constructed or constructing building or system.
  58. CGR Rules, Section 2, Part 1 - The act of 'accidental griefing' as defined in "CGR Rules, Section 1, Part 1b" may not be punished in a 'normal' ban, however, a temporary of a maximum 300 minutes is allowed.
  59. CGR Rules, Section 2, Part 1b - "Accidental griefing" is the act of unintentionally adding, removing, or otherwise changing of any block, blocks, entity, or entities that caused unwanted action(s) or appearance(s).
  60. CGR Rules, Section 2, Part 2 - Accidental griefing temporary bans must be just and fair. You may not sentence a user an extended time due to personal feelings.
  61. CGR Rules, Section 3, Part 1 - Stealing, taking items that don't belong to you, will not be tolerated any may result a ban.
  62. CGR Rules, Section 4, Part 1 - Chat messages, nick names, and tags may not contain the following codes: k (Obfuscated), m (Strikethrough), n (Underline), o (Italic).
  63. CGR Rules, Section 5, Part 1 - Unwanted intentionally Player Vs. Player (PvP) shall not be tolerated and is a ban-able offence.
  64. CGR Rules, Section 6, Part 1 - The modification of a users speed in the attempt to cause or create lag and or stop the server is a perm ban able offence.
  65. CGR Rules, Section 7, Part 1 - The process of rapidly or on a mass scale of creating, removing, or editing any block(s) that cause lag and or the server to crash is a perm ban able offence.
  66. CGR Rules, Section 8, Part 1 - The act of sending unwanted, or otherwise non-readable message(s) or command(s) will not be tolerated and may result in a mute, ban, or perm ban depending on the severity.
  67. CGR Rules, Section 8, Part 2 - The rapid sending of message(s) or command(s) will not be tolerated any may result in all commands being temporarily blocked, muting, banning or perm banning depending on the severity.
  68. CGR Rules, Section 9, Part 1 - The act of tweaking or modifying any user or users inventory shall not be tolerated unless given permission.
  69. CGR Rules, Section 10, Part 1 - Invisibility and invisibility potions are not tolerated and will result in a warning, smite, or ban depending on the severity.
  70. CGR Rules, Section 11, Part 1 - The act of annoying any user(s) with chat messages and or commands will not be tolerated and will result warning, smite, blockage of all commands, or ban depending on the severity.
  71. CGR Rules, Section 12, Part 1 - The act of pretending or otherwise using similar to exact nick names as any administrator or otherwise online user shall not be tolerated and shall be dealt with the 'punishment' chosen by any online administrators.
  72. CGR Rules, Section 12, Part 2 - The punishment dealt by any administrator must be just and non-abusive.
  73.  
  74. Name: "Children Play Here act"
  75. Nick: 'CPH Act'
  76. CPH Act, Section 1, Part 1 - Implied and or direct links onto pornographic content shall not be allowed and may result in a ban, or perm ban depending on the severity.
  77. CPH Act, Section 1, Part 2 - Direct links of pornographic content on our forums or otherwise operated website shall result in an perm ban, forums account and IP address banned, and reported on Proboards.com and StopForumSpam.com
  78. CPH Act, Section 2, Part 1 - Expression of sexual orientation via blocks shall not be tolerated and will result in a ban.
  79. CPH Act, Section 3, Part 1 - Avoid using the terms "sex" and "intercourse" on any platform owned and operated by FreedomOP or FreedomOP's users.
  80. CPH Act, Section 4, Part 1 - The widespread or moderate amount of swearing shall not be tolerated on forum signature by any administrator.
  81. CPH Act, Section 4, Part 2 - A maximum of 8% of the text may be classified as profanity and or "offensive language".
  82. CPH Act, Section 4, Part 3 - Special Executives and above may classify a user{s} signature offense and has the ability to ask for an amendment or amend at will.
  83.  
  84.  
  85. Modification log and Archive Log:
  86.  
  87.  
  88. Edit Date, URL, By Whom
  89. Aug 12 2014 01:57:10, http://pastebin.com/j91sN97E // To be changed to Mega.co.nz - cowgomooo12
  90. Aug 09 2014 00:04:27, https://mega.co.nz/#!8RwCwDrS!xNclIAcVRgKZ4emWAhR7QhSyf7CzxNTGUWVWsrR3yTw - cowgomooo12
  91. May 27 2014 16:55:17, https://mega.co.nz/#!tVwnBIJa!-iNPafojzgyUfPMi0jaoJGKhlz9oxzaKcO5UgicuA-w - cowgomooo12
  92. May 27 2014 17:11:50, https://mega.co.nz/#!QNonAQCZ!AEIy5Bju8s2oybzf_vbbLfcKJzOOQ_imrQnVAr3xvsg - cowgomooo12
  93. Jun 25 2014 20:55:25, https://mega.co.nz/#!sEIj0TIC!g2uV_QKH9gT3Ox2_7C0dSye9L7RoDaeUY_uOeDlcR0g - cowgomooo12
  94. Jul 29 2014 01:05:34, https://mega.co.nz/#!UARAjSZC!kVJgjUIrg6ADz3hgk-gMkiu7GhHgvAR27Fjp4UvfgOc - cowgomooo12
  95. Sep 12 2014 11:21, http://pastebin.com/u8fkCXD2 // I need someone to change it to mega.co.nz - aggelosQQ
  96.  
  97. Disclaimer:
  98. Modification of this thread may materialize with, or without warning. Please, do note this protocol is still in Alpha Stage. If you foreshadow any problem, please private message myself. If you have any suggestions, please do share!
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement