Phoenix Risen (HOD)

Alliance Name: Phoenix Risen

Alliance Tag: HOD

Genre:

Phoenix Risen, or HOD, established August 25, 2011, has risen quickly to become a force to be reckoned with in the SFC Original universe. As of August 11, 2012 we are the #19 ranked alliance. We rank #17 in alliance average.

We believe, foremost, that our members and our opponents are to be respected as people and as SFC players. As is seen in the following Alliance rules, we expect our members to be civil to each other and to opponents. In return, we expect our opponents to be aggressive but civil toward us. Being human and humane toward each other is a dictum of the basic rules of (real) war. Applied to SFC, this helps retain players and ultimately increases game enjoyment for all of us.

We are fiercely protective of our Alliance members when they are attacked or messaged in a spiteful manner. Opponents who do so can expect to find themselves beset by the full resources of our Alliance.

HOD recruits players of all ranks and playing styles. We have our warlords with large fleets, and we have our master builders. We attract mature players who are serious about their game play. When given the opportunity to work under the tutelage of our senior members, even the newest players can move up quickly in game rank, develop substantial civilizations, and make valuable contributions to the Alliance and to the overall SFC playing community.

Origins

Most of the HOD officers and several other players began the new alliance to provide the opportunity to play with people who valued multiple styles of play and who were sold on the importance of respect among players. Subsequent members have been attracted to HOD because of these core Alliance values.

Leadership

Leader: Commander Applejack

First Officer: Death Viper J

Battle Commander: Sun Killer. Wars: Research requests, find suitable targets, organise MAC opportunities. Heph wing: Tactics, CNC of the Heph wing once launched

Recruitment and Training Officer: Major-Disaster. Recruiting; training; data generation and control

Operations Officer: Jimbo007. Monthly missions; competitions; message board management

Intelligence Officer: Star Slayer 420. Gathering intelligence, rumours, and other information which might prove useful to other departments

Quartermaster: Douglas Simmons. Duties: to be provided soon

Alliance Rules

Each member agrees to abide by the following rules:

1. No attacking fellow alliance members unless they are inactive. This includes probing.
2. Do not use the alliance as a threat towards others.
3. Be polite to not only fellow alliance members, but the community as a whole. Foul language and insubordination will not be tolerated.
4. No begging. It is ok to ask for help. That is how you learn. There are a lot of people here willing to dole out advice.
5. Learn to Fleet and resource save. If you are not in dip mode, this is just a way of life if you want to survive .
6. No bullying. This is where you attack the same active target day in and day out the max number of times, in an attempt to drive them away from the game.
7. More of a suggestion than a rule, but get out there on the forums and meet a few people. The people here are better than this game ever will be on it's own.

Alliance-Specific Ranks

HOD members have Alliance-specific ranks that are based on overall SFC ranks:

1-999: Reincarnated Phoenix
1000-2499: Candescent Phoenix
2500-9999: Embered Phoenix
10000-14999: Charred Phoenix
15000+: Hatchling Phoenix

Tools of the Trade

We recommend that our members use the following scripts and tools to enhance their SFC playing experience:

1. The Eljer scripts, for Chrome and Firefox browsers, offer several enhancements to the basic SFC user interface, report reformatting, etc;
2. The AstroSpy and Open Parser galaxy page parsers are scripts that run within the Chrome and Firefox browsers. Each parser collects game information whenever a player who has installed the tool navigates to a different solar system using the SFC Galaxy page. The parser then sends the information to a server-based database, where it is stored with information that is collected as other game players navigate from one solar system to another. This collective information then can be accessed and queried to better understand opponents' dispositions, Heph locations and historical tracks, and the location of NPCs. Each tool provides information that is not provided by the other. Because of this, we recommend that both tools be installed.

The Greasemonkey scripting engine must be installed into Firefox before any of the above tools can be installed into that browser.

HOD maintains an MS Messenger chat room for use in plotting attacks or simply talking about SFC and other vitally important aspects of life. Contact Sun Killer for access to the chat room.

Sharing Spoils from Multi-Player Engagements

HOD's position is that each participant in a multi-player engagement is a valuable contributor and should share equally in the spoils of war, irrespective of the amount of resources they committed to the engagement. The spoils to be shared are those which remain after each player's expenses (hydro burned as fuel, cost of IPBMs, and cost of destroyed ships) have been covered, to the degree that is feasible, using the acquired resources. The cost of defenses destroyed during a Group Defend are not to be subtracted from the spoils of the GD prior to calculating player shares.

This position applies to players involved in a Group Attack, Group Defend, or debris field pickup. It also applies in the case where a player identifies a target, then asks a particular Alliance member to "provide all the muscle" to take out the target. In this latter case, the identifying player and the active player share equally in the spoils of war. This position does not apply if a player posts an identified target to the Alliance's message board. Any reader of the board is free to take on such targets and has no expected obligation to share in the fruits of war with the poster.

This is the Alliance's default policy. It isn't mandatory. Players are free to negotiate alternative arrangements before performing a multi-player engagement or collaborative operation, such as farming of an inactive. If no such alternative understanding is agreed to before the engagement, it is expected that the involved players will abide by the default policy.

Admission

Please send requests to join to either Commander Applejack, Death Viper J, or Major-Disaster. Commander Applejack and Death Viper J are located at ‎[20:252:0], and Major-Disaster is at [9:179:15]. Please include at least one of your colony locations in the memo box of your request to join.