New feature poll: Alliances!

A few days ago Pardus developers announced that they will be making another upgrade to the game and created a poll for the players to decide which feature it will be.


Here are the poll options and explanations what new features may look like:

This is your time to decide which of the following topics you would like to see us working on next. Voting will be open until February 28th. This thread will remain open indefinitely for comments.

This poll is directed towards a single theme: Collaboration


Alliance command station upgrades
Alliance command stations can be upgraded to have them log and notify the alliance of additional events:

When a timebomb placed by an alliance member is triggered in the ACS' cluster.

When an alliance member triggers a timebomb in the ACS' cluster.

Ships bypassing a military outpost owned by an alliance member in the ACS' cluster.

Damage done to starbase buildings not having any defense and invasions of a starbase owned by an alliance member in the ACS' cluster.

Attacks on an alliance member's ship in the ACS' cluster.

Interferometer effects with new percentages for above events apply. The speed at which the ACS notifies the alliance of new events is increased.


Alliance ruling body
Different types of governments can be selected for alliances:

Autocracy: All power is in the hands of the alliance leader. This is the current form of alliance government. The alliance leader may switch to a new form at any time. Once switched, the new ruling body makes the decision whether to switch type of government once again.

Oligarchy: A council of 5 pilots replaces the current leader position. The votes of the council replace all decisions previously made by the leader. With the exception of changing the alliance's faction alignment and anything targetted at a council member requiring a two-thirds vote (at least 2/3), a simple majority (more than 50%) is required for votes to succeed. This includes electing or recalling a treasurer/application manager, kicking a non-council alliance member, handling the alliance funds (if the treasurer position is vacant), accepting a new member (if the application manager position is vacant), senior membership, modifications to the alliance page, private conflicts. The council also oversees taking credits out of the alliance funds - an amount over a configurable amount of credits taken out by the treasurer needs to be approved. A council member stays in the council for as long as they remain part of the alliance, or until they are voted out, or until they resign. If they resign they may choose their successor; if they are voted out or if they are no longer part of the alliance the council chooses their successor by two-thirds vote. Council seats may remain free, however a council with only a single member will have the alliance government type automatically switch back to an autocracy. If the treasurer or application manager positions remain vacant, all of their responsibilities are taken over by the council and voted on.

Democracy: There is no council or leader position - its responsibilities are taken over by all members of the alliance through their participation in votes. Two-thirds votes are required for electing and recalling the treasurer/application manager, for kicking a fellow alliance member, for changing the alliance's faction alignment. A simple majority is sufficient for anything else.
For both democracies and oligarchies the required participation of voters is based on the members or council members of the alliance currently active.
The feature of the treasurer being overseen doing transactions over a configured amount of credits is added to all types of governments.


Alliance tasks
Tasks comparable to bulletin board missions can be defined to be completed by members of the alliance. The type of tasks ranges from killing an NPC (e.g. a space crystal blocking the way) at a specific location/a certain amount of NPCs/a certain individual, to delivering specific goods to a starbase or building (optionally from a specific location).
Tasks can be given a start and an expiration date. They can be set to be placed repeatedly (e.g. each week). They can be restricted to be completed only once or any amount of times by any amount of pilots. Tasks can be configured to notify specific members of the alliance on completion. The completion of a task results in a payout of the set amount of credits from the alliance funds which has to be approved by the treasurer. Each type of task has a set amount of points rewarded to the pilot completing the task. An internal alliance ranking of the top contributors ordered by said points is added.
A new alliance position "Mission coordinator" is added. Mission coordinators may set up alliance tasks. The alliance leader can set it to include specific pilots, any senior member or any starbase owner.



Each option includes a preliminary summary but is in no way meant as a full feature description.
The selected feature will be first implemented in Pegasus to honor Premium Account players and their essential support for the maintenance and further development of Pardus.