| Pages: [1] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 2 post(s) |
DrysonBennington
Eagle's Talon's
108
   |
Posted - 2014.05.01 00:39:00 -
[1] - Quote
With the increased CODE Alliance activity in high sector located around the asteroid belts becoming more and more a problem I propose a new method of dealing with the threat. The method would involve establishing patrol fleets within each belt that the members of a corporation could put ISK towards each week in order to fund the patrol fleets.
Each local system patrol fleet would have the duty of protecting a certain asteroid belt.
How the patrol fleet would work and accomplish the job of defending the mining operations is rather easy.
First the patrol fleet is established using either cruisers or battle cruisers set for MAX DPS. The battle cruiser I have in mind would be the Talos because its fast and heavily gunned.
The patrol fleet would patrol its area or areas making certain to guard the barges in the belt. If an unusual ship such as a Stabber appears close by to a mining barge then a strike is imminent on the mining barge within a few minutes.
Once the CODE Command Ship appears the Patrol Ship would move to within an orbit of 1000 meters from the barge that the CODE Command Ship is near. Once the attack vessels arrive which will mostly like be two to three catalyst destroyers and begin the attack is when the Patrol Ship is able to respond. As soon as the attack vessels begin their attack on the barge which begins with one attacker firing first and taking the barge to half armor before it is popped by Concord with the second attacker finishing the barge off the Patrol Ship is able to open fire on the lead attacking vessel since there is alot of time between when Concord arrives which depends on the system security status.
See below to manage your attack on CODE Assault Ships.
Quote:CONCORD Response Times
The CONCORD Response Time depends basically on the displayed security status (not the real sec) of the system and the status of CONCORD presence in the system. It's possible CONCORD still has to spawn in the system, has already spawned elsewhere in the system, or is present on grid.
It seems the lock time of the CONCORD ships does not depend on the signature radius of the offender's ship. The following table gives the time in seconds between the offending action and the first felt action of a CONCORD ship when CONCORD has just spawned in a system.
0.5: Roughly 19 seconds
0.6: Roughly 14 seconds
0.7 : Roughly 10 seconds
0.8 : Roughly 7 seconds
0.9 and 1.0: Roughly 6 seconds
When CONCORD is already on grid, the response time is severely reduced. There are no hard numbers on that yet but it looks like as if the response time drops to 2 seconds in 1.0 to about 8 seconds in 0.6 and 9 seconds in 0.5.
When CONCORD has already spawned elsewhere in the system but isn't on grid, the response time is significantly increased. In this case it will take about 22 seconds them to arrive and start firing in a 0.6 system.
A Thrasher has a cycle time of 7 seconds, and does about 1000 damage per volley. So for a ship that costs less than a 1 million ISK you can be suicide ganked for 1000-2000 EHP in a 0.5 security system where CONCORD still has to spawn. The same setup in 0.9 would only do 1000 EHP of damage.
If CONCORD has already spawned in the system and is not on grid, it's possible the Thrasher can do 3000 EHP damage in a 0.6 system.
As you can see there is more than enough time for a t2 fitted Talos to attack the CODE attack vessel and earn the kill.
Each Patrol Fleet Corporation should have no less than ten members in it and no more than twenty that way each solar system can have its own Patrol Fleet that is responsible for its own system.
The High Sector Patrol Fleet is a good way for a corporation to earn ISK and learn how to PVP in High Sector systems.
This would also be a good thing for the 500 new pilots being trained by CCP as their presence will be much appreciated as well as establishing a good firm standing with the rest of the pilots in New Eden. |
Daoden
The Scope
Gallente Federation
47
|
Posted - 2014.05.01 01:19:00 -
[2] - Quote
So you want NPC mercs in high sec that attack CODE guys? |
Domanique Altares
Rifterlings
Point Blank Alliance
2617
|
Posted - 2014.05.01 02:02:00 -
[3] - Quote
Just ignore CODE assclowns. Best outcome possible.
Rifterlings pirate corporation is now recruitng members for lowsec PvP operations. Newbie friendly, free T1 frigate and dessy hangar, solo tutoring and PvP classes for new members. Join our in game channel 'weflyrifters' and speak to a recruiter today. |
Michael Ignis Archangel
Caveat Emptor Technologies LP
Spaceship Samurai
40
|
Posted - 2014.05.01 02:26:00 -
[4] - Quote
If you're talking about an arrangement between other players, no new features are needed. If you're talking about NPC mercs to be faster than CONCORD, no thank you. |
Bohneik Itohn
Periphery Bound
51
|
Posted - 2014.05.01 03:07:00 -
[5] - Quote
You don't introduce annoying and awkward mechanics to deter slightly more annoying and awkward players.
If you mine in high sec and you aknowledge that CODE is a threat, they should be on your watch list and you should be watching local. Eve is full of threats so keeping an eye out for CODE is only a problem if you like to AFK mine. Anyone can decide to form a suicide ganking gang and go out and harass you just because they have nothing better to do, so you should always be paying attention.
If you don't like being forced to sit in the station until CODE leaves, fit out a cruiser and put it in your home station you drop ore off in. Almost all CODE members are criminals that you can shoot without repercussions in high sec and they fly destroyers fit for alpha damage, not PvP. You shouldn't have any problem with them with even a smattering of combat skills.
Return the favor, it's more interesting than staring at rocks, or rather staring at reddit and getting shot because you weren't paying attention. |
Dinokin Askiras
OAK Company
RAZE Alliance
0
|
Posted - 2014.05.01 03:46:00 -
[6] - Quote
http://javaminerbingo.googlecode.com/svn/minerbingo.html |
|
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |