Bureaucrats, developer, Administrators
10,625
edits
No edit summary |
No edit summary |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
==Introduction== | |||
ASR does not just look for individuals to join its ranks- entire units and task forces have joined the ASR universe in the past as well. If you are the commanding officer of an established unit, task force or fleet, and would like to bring your organization into the ASR universe, the guidelines below should help you decide if your organization is compatible with ASR. | ASR does not just look for individuals to join its ranks- entire units and task forces have joined the ASR universe in the past as well. If you are the commanding officer of an established unit, task force or fleet, and would like to bring your organization into the ASR universe, the guidelines below should help you decide if your organization is compatible with ASR. | ||
Line 5: | Line 6: | ||
If, after reading these guidelines and checking out the Library, you decide that your unit or task force is compatible with ASR, then send a note to ASR's Senior Administration to inquire about merging with ASR. | If, after reading these guidelines and checking out the Library, you decide that your unit or task force is compatible with ASR, then send a note to ASR's Senior Administration to inquire about merging with ASR. | ||
<br> | |||
<br> | |||
==Requirements== | ==Requirements== | ||
Line 19: | Line 22: | ||
**Groups of between 3-5 units: If the incoming group size is between 3 and 5 units, the group would either be split up and absorbed by the existing ASR fleets (depending on the general health of the existing fleets at the time of the merger), or they would be grouped together into its own task force (or two) and absorbed en masse by an existing ASR fleet. In the end, the solution would be the one which is deemed best for ALL parties concerned. | **Groups of between 3-5 units: If the incoming group size is between 3 and 5 units, the group would either be split up and absorbed by the existing ASR fleets (depending on the general health of the existing fleets at the time of the merger), or they would be grouped together into its own task force (or two) and absorbed en masse by an existing ASR fleet. In the end, the solution would be the one which is deemed best for ALL parties concerned. | ||
**Groups of larger than 5: If the incoming group is larger than 5 units, the group would either be split up and absorbed by the existing ASR fleets (depending on the general health of the existing fleets at the time of the merger) or, if the existing fleets are in good health, the incoming group could possibly be lumped together and designated a new fleet within ASR. In the end, the solution would be the one which is deemed best for ALL parties concerned. | **Groups of larger than 5: If the incoming group is larger than 5 units, the group would either be split up and absorbed by the existing ASR fleets (depending on the general health of the existing fleets at the time of the merger) or, if the existing fleets are in good health, the incoming group could possibly be lumped together and designated a new fleet within ASR. In the end, the solution would be the one which is deemed best for ALL parties concerned. | ||
<br> | <br> | ||
Line 32: | Line 34: | ||
*All new unit commanding officers would have the same responsibilities and privileges afforded to the existing unit commanders- they would participate as a voting member in the bi-annual Round Table; they would not need permission or approval to create new player characters, etc. | *All new unit commanding officers would have the same responsibilities and privileges afforded to the existing unit commanders- they would participate as a voting member in the bi-annual Round Table; they would not need permission or approval to create new player characters, etc. | ||
<br> | <br> | ||
==Notes== | ==Notes== | ||
Contents last updated SD 220110 (10 January 2010) | * This document was written by Scott Lusby, with edits by Jeffrey Jenkins. | ||
* Contents last updated SD 220110 (10 January 2010) |