Here are the draft guidelines for the sim. They are the same as the Google Doc ones that I PMed everyone a few days ago. Please leave comments and let us know what you think!!
1. Prime Directive
Be respectful of each other, and have fun!
2. The Command Staff
2.1 The USS Bunker Hill’s Command Staff consists of the Commanding Officer (CO), the Executive Officer (XO), and the Second Officer (2ndO).
2.2 The Command Staff functions as a collegiate body and strives for consensus. For the proper functioning of the sim, however, final decisions on all sim-related matters rests with the CO, except where these guidelines and the rules/regulations of Obsidian Fleet (OF) state otherwise.
2.3 In the absence of the CO, the XO assumes all rights and responsibilities of the CO until the latter’s return or in the event of vacancy until the vacancy is filled.
2.4 In the absence of the XO, the 2ndO assumes the rights and responsibilities of the XO until the latter’s return or in the event of vacancy until the vacancy is filled.
3.1 Primary Characters (PCs) are the players’ main characters. Each player may have only one PC on the Bunker Hill at any given time. Every PC must have a full biography.
3.2 Protected Non-Primary Characters (PNPCs) are secondary characters associated with a player and are linked to that player in the Nova system. The Command Staff may have no more than five, Department Heads no more than three, and all other players no more than one PNPC(s) at any given time. Mission Specific Characters do not count against this limit. Waiver may be granted by the Command Staff on a case-by-case basis.
3.3 The CO and the XO may create PNPCs in any department, provided the Department Head is given prior notice. Any other players may create PNPCs in any department with the approval of the Department Head. If the Department Head position is vacant at the time of the PNPCs’ creation, the approval of the CO is required.
3.4 Non-Primary Characters (NPCs) are secondary characters not associated with any players. Only Department Heads may create NPCs within their own departments with the exception that the Command Staff may create NPCs in any department, provided the Department Head is given prior notice.
3.5 No player may write for another player’s PC and PNPCs without that player’s express consent, the exception being that the Command Staff may do so but only a) in a JP that is already in progress, AND b) when a player is on LOA, ELOA or AWOL, AND c) provided that any such writing is kept to the minimum that is necessary for the progression of the JP in question.
3.6 Under no circumstances may a player harm, injure, or kill another player’s PC and PNPCs without that player’s express consent.
4. Storylines & Subplots
4.1 The Command Staff should make all reasonable effort to involve the entire crew in the crafting of mission storylines. All players should be informed of the basic structure and/or main elements of a mission at least two weeks before the mission’s official start. Changes to mission storyline after the mission has begun require the approval of the Command Staff.
4.2 All proposed subplots and significant changes to existing subplots require the approval of the CO. Approval will always be granted except in cases of (a) violations of the Sim Guidelines and/or (b) potential conflicts with the mission storyline and/or other subplots.
5. Posting Requirement
5.1. All posts should conform to the Bunker Hill’s sim rating of 13+, i.e. (a) infrequent, mild swearing is permitted, (b) mild sexual innuendo and references are permitted, and (c) mild violence is permitted. All players must keep in mind that just because something is permitted does not mean it must or should be used everywhere in every post. If in doubt, players should err on the side of caution or consult with the Command Staff.
5.2. A minimum of two completed posts every month are required of all players. Any player who cannot meet the posting requirement for more than seven days must request a leave of absence.
5.3. All players are expected to be involved in at least one Joint Post (JP) at any given time, not counting the time needed to set up a JP.
5.4. All players must respond to JP tags within 72 hours. If a player cannot respond within 72 hours, a one-time extension of another 48 hours will be automatically granted, provided the said player notifies all players involved in the JP before the expiration of the first 72-hour period. The extension will take effect after the expiration of the first 48-hour period. Only one extension is allowed for each tag in a JP.
Players are not subject to this requirement when on leave.
5.5. When on leave, players are not subject to the posting requirement specified in 5.2, 5.3 and 5.4, which are also waived for Thanksgiving, Christmas, and New Year. The CO may approve other waivers on a case-by-case basis. The duration of a waiver must be specified and clearly communicated to the players.
5.6. No player may change or edit another player’s work without that player’s express consent, the exception being that the Command Staff may make cosmetic changes including, but not limited to, spelling/punctuation corrections and necessary alterations for compliance with the Bunker Hill’s sim rating of 13+. No major alterations are permitted.
5.7. No player may damage or destroy any vessel or technology without the Command Staff’s approval.
6. Leave of Absence
6.1. No leave of absence requests made in accordance with these guidelines will be rejected except in cases of a player abusing the leave of absence system, the determination of which rests with the Command Staff. Abuse of the system may subject the offending player to strikes.
LOA (7 to 14 days)
6.2 Any player who cannot meet the posting requirement or otherwise participate in sim activities between seven and fourteen days must request a Leave of Absence (LOA).
6.3 A player should make an LOA request by either a) changing his/her status from Active to LOA through Nova control panel, or b) informing both the CO and the XO through either Nova PM or email. The player should also inform other relevant players (e.g. JP partners) of his/her leave.
6.4 LOA requests must be submitted no less than 24 hours prior to the the leave and must indicate anticipated return date. Reasons for LOA are not required, but are appreciated.
6.5 LOA expires seven days after the request’s submission, at which point the player is again subject to the posting requirement.
ELOA (15 to 30 days)
6.6 Any player who cannot meet the posting requirement or otherwise participate in sim activities between fifteen and thirty days must request Extended Leave of Absence (LOA).
6.7 A player should make an ELOA request by either a) changing his/her status from Active to ELOA through Nova control panel, or b) informing both the CO and the XO through either Nova PM or email. The player should also inform other relevant players (e.g. JP partners) of his/her leave.
6.8 ELOA requests must be submitted no less than 24 hours prior to the leave and must indicate both a) anticipated return date and b) reasons for the leave.
6.9 ELOA expires thirty days after the request’s submission, at which point the player is again subject to the posting requirement.
PLOA (more than 30 days)
6.10 Any player who cannot meet the posting requirement or otherwise participate in sim activities for more than thirty days must request Prolonged Leave of Absence (PLOA).
6.11 A player should NOT make a PLOA request by changing his/her status from Active to ELOA through Nova control panel. Instead the player should contact the entire Command Staff (i.e. CO, XO, and 2ndO) regarding the matter through either Nova PM or email so that appropriate arrangement may be made.
6.12 At the Command Staff’s discretion PLOA may result in the player’s position being made available to the general public for the duration of the leave, in order to avoid major disruption to the mission storyline.
6.13 PLOAs are automatically approved upon request for players on active military duty, and the player’s position will be locked until his/her return.
6.14 A player is considered absent without leave (AWOL) if there is no communication from the said player for at least two weeks since the last time the Command Staff reached out to him/her. Prolonged and/or repeated AWOLs may subject the player to strikes.
7.1 A player is assessed a strike when he/she fails to follow one or more of the Sim’s Guidelines to the proper extend. The assessment of a strike is at the discretion of the Command Staff in accordance with these Guidelines.
7.2 When a player is issued a strike, the CO should notify the said player in writing of the strike and the reasons for the strike. Copies of the notification should be sent to and only to the XO and the 2nO
7.3 If a strike is issued in error and evidence is presented within seven days of the strike’s issuance, the strike should be expunged from all records as if it had not been issued.
7.5 A strike is active for 90 days from its issuance. If a strike is issued while another strike is still active, the second strike will be the first to clear after 90 days from its issuance; then the first strike will clear after 90 days from the clearance of the second strike regardless of how many days passed between the issuance of the first strike and that of the second strike.
7.6 The CO is responsible for the safekeeping of the Bunker Hill’s strike records. Access to the strike records is restricted to the following cases only: (a) A player may request access to his/her own strike records; (b) The XO and 2ndO may have access to another player’s strike records, but only for the purpose of assessing disciplinary actions against said player; (c) if a player files an appeal with OF JAG Corps regarding the Command Staff’s disciplinary decisions against him/her, the said player’s strike records may be shared with JAG personnel assigned to the case, but only if it is necessary and relevant to the case. In all other cases, strike records must be kept strictly confidential.
8.1 Two or more concurrently active strikes may subject the player to demotion in rank and/or position at the discretion of the Command Staff. The CO should notify the player in writing of his/her demotion and the reasons for the demotion. Copies of the notification should be sent to and only to the XO and the 2ndO.
8.2 A player may be removed from the Bunker Hill under the following circumstances only: a) he/she has accumulated three concurrently active strikes, in which case the player’s removal requires the consent of both the CO and the XO, or b) he/she has endangered the safe, friendly, and productive environment of the Bunker Hill, in which case the player’s removal requires the consent of the entire Command Staff, i.e. the CO, the XO, and the 2ndO, unless one or more of the Command Staff are unavailable due to vacancy, ELOA, PLOA, or AWOL, in which case the consent of the remaining Command Staff is required.
8.3 The CO should notify the player in writing of his/her removal and the reasons for the removal. Copies of the notification should be sent to and only to the XO and the 2ndO.
Anything about the sim - other than missions/story and website/forum - goes here.
1 post • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest