TheAlliance TheAllian
From Starfleet Commander
Revision as of 07:34, 24 June 2010 by Markap1970 (talk | contribs)
Hierarchy: Diplomatic Policies: Rules of Engagement:
TheAlliance is currently ranked #140 out of all alliances and, as a whole, is rapidly advancing.
Hierarchy:
Diplomatic Policies:
- Alliance members should not send threatening or offensive messages to other players. This may only cause them to be more aggravate and cause more attacks on you and alliance members.
- A member of our alliance must support the alliance that we have a NAP proposed. They must also give a reason why we should have this NAP.
- if you are contacted by a Alliance Leader in regards to an attack that you did on there member please forward it to the AL or the GL of the galaxy that the attack happened in.
Rules of Engagement:
- Inactive planets are fair game, even if they belong to a NAP.
- Attacking Alliances that we have NAPs with, is NOT allowed!!!!!! unless they are inactive planets. If they mail about the attack you are to call it off if you can and inform the AL or GL of where it happen.
- Being attacked by any alliance or player is not acceptable unless you leave you fleet and resources out to be taken. If this happens then there is nothing that we as an alliance can if you do not Fleet and Resource Save (FRS).
- Before attacking any alliance or player you need to make sure that you know how to FRS. happy hunting.
Merger request:
- getting a list of members, officers and the current NAPs. NAPs will be reviewed pending members request for them one member want it then we try to get it for them.
- accept the members and rank placement. All your offices will be made cpt regardless of there rank points and those that have the points to have better rank will be placed in the corresponding rank as well as the rest of the members in there ranks spots.
- Identifying galaxies and setting up GL for the galaxies that have none.
- setting up Fortress systems and the support for members in all the galaxies
- address all grievances that members have. this may happen at any time in the merger process or after.