Surrah
|
Posted - 2008.09.09 22:15:00 -
[1]
Given the updates, this is probably out-dated and worthless. Oh well, here it is.
Why don't you just use the population of a system/constellation to determine sov. How many pilots are in the system per hour, on average, over the last week? This would allow small alliances to claim sov without massive investments. It will also allow a more realistic view of sovereignty as to be in control of space you have to be there.
This would work as follows. Your alliance has moved into a system and taken over. You, as a group are not large, but are fairly active. Over the last 168 hours (thats one week) you averaged a population of 24 pilots per hour in system. That sounds minimal, but you must consider that it considers all 24 hours per day, for the last 7 days. Thanks to downtime, there is at least one hour of 0 population every day.
If you get invaded by a group of 24 pilots from another alliance who stay in your system from downtime to downtime for 2 days straight, at the end of the second day they will have only accrued 6.57 pph (pilots per hour, over the last 168 hours). They don't challenge your sov.
If you get invaded by a group of 468 members of another alliance, and they hang out and harass you and blow up your assets, after 8 hours they have 22.3 pph. After 9 hours they will have 25.1 pph and will initiate a transfer of sov, which I'm assuming will occur at the next downtime.
Say the group of 468 was just harassing you and they leave the system after 9 hours, leaving their pph at 25.1. If no one beats that rate, the attacking group will have sov for the next week, until their occupied hours start to slip off of the 168 hour grid and your group's 24 pph is back above their now 22.3 and falling pph. That is assuming you maintained a pph of 24 the whole time.
This system will allow for not having to deploy Cap ships to gain sov. It will also allow POS killing to be more directed. If you want to take sov, move in, and kill the POS's that allow the current residents to stay in system and keep their pph up.
You would need, however, an option to assign your pph to another alliance. This would be to allow space "rental" and other allaince to alliance agreements.
You should also allow a system that is say, sov 2, to also apply a percentage(say 10%) of its pph to it constellational neighbor systems. This would given an inherent bonus to gaining sov in all systems in a constellation, as each would end up boosting it's self. As system A gets sov 2 it gives an additional 10% of it's pph to system B. After a while, system B will gain sov 2, and give an additional 10% of its pph to its neighbors, systems C and A. In this method, A and B are boosting each other at 10%, and getting back another 1% of that in the return from the other system.
Generating a double cycle of boosting will allow a smaller group to gain a meaningful hold in a constellation, while still making them vulnerable to highly organized efforts of large groups of pilots.
If you go one step further, and install a pph cap(168 hour average, not actually hour by hour) this mechanic won't make big alliances upset proof. In the event of a tie at the cap, sov will go null, then the first to lower the other's pph will win sov.
You should also put a pph minimum for sov to ensure systems aren't being claimed by random traffic. 2 pph should suffice for this.
Additionally, you should put in an inactivity timer to avert afk'ing in station to keep sov up. Ideally it would be some kind of clicky with a countdown before it logs you out. This would help prevent cov ops from being inadvertantly logged, while logging people who aren't at the puter. After 25mins of inactivity, you get a pop up message saying; "You are being logged off in [TIMER]" The timer starts at 5 minutes and counts down. Say a pilot doesn't want to be logged, give them an ESC menu check box; "I wish to not be auto logged, at the expense of not being counted toward my alliance's Pilots Per Hour rating".
|