| Author |
Thread Statistics | Show CCP posts - 7 post(s) |
|
CCP Navigator
C C P
C C P Alliance
   |
Posted - 2009.09.16 21:05:00 -
[1]
CCP Weirdfish introduces a new blog concerning testing of Dominion on Singularity over the coming weeks.The three tests will involve the new Navy ships and changes to Faction ships. Super Capitals will also be stress tested along with the new changes to sovereignty.
Full details are available in this blog.
Navigator
Senior Community Representative
CCP Hf, EVE Online
|
|
|
CCP WeirdFish
|
Posted - 2009.09.17 08:00:00 -
[2]
 Originally by: Sidrat Flush
I love the devblogs and the flow chart, and hello to CCP Weirdfish.
Right so you anchor the claim marker and if it's still there 24 hours later Sov is yours (which leads to Pi - I like spreadsheets more than cake).
In order to lose it, the hostiles/renters will have to plant a module 'disruptor field' and keep it alive for twelve hours which makes the claim marker vulnerable to attack - before this however it's not. Seems simple enough, and I'm not going to ask questions that can change after testing or even overnight, like hp and m3 size, but I will ask two questions.
Will claim markers and disruptor fields bpo's be seeded on the market?
Will you be able to anchor them anywhere at all in the system and, wether you're limited to a moon/planet/gate will they appear on the overview for everyone and their Orca of doom to warp in and try to take it out/defend it?
Alliances that want 0.0 access should be able to cover the entire 23 hour game day. If you're trying to defend twenty systems you'll need the man power to do it as well, although in most regions there's choke points a-plenty which could be focused on instead.
I like the direction it's going in, there'll be work-arounds of course and if these modules can be anchored anywhere it could mean going in with a smaller force will be harder to probe down, just depends on the actual points on the modules and the ship you need to carry a few AS WELL AS getting your own marker through as well!
I hope I'll be able to get to the test servers for the fun and games.
The only information you are missing is that one disruption beacon must be anchord on every stargate of the solersystem you are trying to take before the claim marker becomes vulnerable to attack.
|
|
|
CCP WeirdFish
|
Posted - 2009.09.17 08:04:00 -
[3]
Originally by: DRACO selen
Edited by: DRACO selen on 17/09/2009 05:17:08
serious question incomming 
Does it take 24h or 24h+next dt to claim sov?
Once the claim marker is online fully you have sov , there is no waiting until downtine
|
|
|
CCP WeirdFish
|
Posted - 2009.09.17 08:39:00 -
[4]
I would like to take the opportunity to reiterate that the system detailed here is only the first iteration of the new sovereignty and there are more parts yet to be announced and explained. Also that all the mechanics timers and the like are as i explain in my blog subject to change. Don't panic!
|
|
|
CCP Sisyphus
|
Posted - 2009.09.17 09:07:00 -
[5]
Some of you have raised some questions, or made comments that might not be completely correct. So some summarization of the mechanics and reasons might be in order. (Also note - numbers are preliminary, they are subject to change depending on feedback of play on Singularity)
Sovereignty is just: While you have sovereignty all your Starbases will have a 10% (subject to change) fuel bonus. The system will be marked as belonging to your alliance. You will have the ability to upgrade the system (via infrastructure hubs and investments).
You have to pay upkeep for all systems you claim.
Claiming a system is as simple as: Anchor Claim Marker, online it (takes 24 hours).
During those 24 hours it is vulnerable to being destroyed. Once online it is invulnerable.
To contest a system (i.e., make the claim marker vulnerable again): You need to have System Restore Units ONLINE at every gate. Onlining takes 12 hours. They are vulnerable to being destroyed at all times.
If the system is unclaimed, there will be a battle between different alliances planting Claim markers and trying to defend them while trying to destroy enemy claim markers.
If the system is claimed, there will be battles at every gate trying to destroy the System Restore units while the enemy tries to defend them. Once they are online, you need to defend your Claim marker while simultaneously trying to destroy one of the System Restore Units.
The advantage is inherently with the defenders, as they only need to destroy one (1) of the System Restore units, while the invaders need to defend all of them.
|
|
|
CCP Abathur
|
Posted - 2009.09.17 09:52:00 -
[6]
Originally by: CCP WeirdFish
I would like to take the opportunity to reiterate that the system detailed here is only the first iteration of the new sovereignty and there are more parts yet to be announced and explained. Also that all the mechanics timers and the like are as i explain in my blog subject to change. Don't panic!
Quoting this for emphasis. What's presented in WeirdFish's blog is the sov system at its most basic level. The timers are subject to testing and feedback and there are numerous bits that are still to be introduced and explained.
We had a choice in how we planned to release these changes and we chose to go with the 'more information sooner' strategy. Please keep your feedback constructive and helpful as we go forward. Thank you. 
|
|
|
CCP Greyscale
|
Posted - 2009.09.17 10:00:00 -
[7]
Sorry about the confusion on this matter; it turns out that the design doc was wrong 
The onlining time for the System Restore Unit / Disruption Marker is correctly set at 24 hours. The text description and the flowchart in this blog are both using an incorrect value of 12 hours because that's what it says in the design. Which is wrong.
We are having a ponder over whether the claiming unit should be less vulnerable - either moving its cycle to 12 hours, or giving it a longer invulnerable anchoring time and a shorter vulnerable onlining time or similar.
Also, when considering how easy/hard sov is to take/disrupt, it's informative to ask yourself why you're trying to do so in the first place. Specifically, bear in mind that sov has no impact on station ownership under the current design.
|
|
| |
|