Tallen Ellecon
KILL-EM-QUICK
RISE of LEGION
2089
   |
Posted - 2015.01.22 21:10:00 -
[1] - Quote
I haven't read every post in this thread so I may retread on a similar idea.
I want to talk about the EVE implications. And an overall scheme.
It's a big idea but I just throw it out in case someone can expand or use any part of it.
First I love the war barge idea, they don't have to be large vessels, but even if they are it's not too much of a stretch in New Eden to have one person in command a large vessel.
Personal Warbarges can be thought of as just an extension of the merc quarters and have benefits that are contained in Dust/Legion
The Corp warbarge on the other hand could be npc controlled in EVE(for the time being) with a simple function, being the engine of planetary conquest. All internal functions management and upgrades would be DUST based, leaving new skills for those given the responsibility by their corp. It is based by the corporation CEO at inception in an EVE station which will act as the initial corp HQ. When Planetary Conquest battle is initiated the chosen warbarge is set to go to the district at the time of the battle. It will automatically undock, warp to gates, jump, warp, jump,...etc. If clones are being moved it has to go to the system where the clones originated first then the battle or new system if it's just a move, no attrition loss necessary. It should be set to arrive 10 minutes before the battle is set to start.
During the battle it will function like usual for the attacker in Dust, the defender on the other hand has the option of deploying their warbarge or not, up to the point where it would not reach the district in time. If they elect not to when attacked the only difference in Dust will be the lack of warbarge strikes or any other benifits a warbarge affords, but they could have an alternative as the district owner like an inferior or higher WP cost orbital strike platform.
So now with limited Warbarges dictated by either ISK cost, activity, or member donations, simultaneous mass attacks are limited as well. It also means deploying all your warbarge(s) in a mass attack leaves you districts more vulnerable since you don't have the option of deploying yours or moving clones.
If you're still following me this is where corp warbarge subsystems come into play.
Each corp automatically gets 1 warbarge, warbarges have the capability to generate clones and manufacture MCCs. The rate at which clones are generated and MCCs manufactured are still up for discussion. To make it completely cooldown based would make alt corp farming a problem if there was ever any trading. Making it ISK based gives richer corps a huge advantage, but it wouldn't be dissimilar to clone packs. The most important thing is to make it require work and time of some sort by any sized corp, but not let a larger corp get a huge advantage. I personally would base it heavily on corp WP gain so more active corp get more fights as opposed to richer corps. The point is this will replace clonepacks and if ISK is out of the equation it might incentivise more casual fights.
The second automatic function would be a shield that would make it practically invincible. The warbarge is automatically shielded and untackleable (not a word) This allows players without EVE support the ability to defend their warbarge, the drawback being the warbarge loses any ship to ship offensive capabilities and moves slower, thus making it harder to have simultaneous attacks. During battles this is turned off if various other subsystems are used.
Other subsytems limited and grouped according to what bring better gameplay and balance could include but not be limited to.
-Various ship to ship offensive capability ranging from anti frigate, to anti battleship, or anti warbarge. This would be the preference of EVE based corps who could defend their warbarges and choose accordingly. All AI controlled dictated by the Dust player assigned to the warbarge.
-Improved WB strikes, decreased WP costs, increased damage.
-Increased ground forces stats, like more resistant shields (no more than 5%) or reduce hack time.
-Reduced OB cooldown
-Increased ground detection to a certain db, making all vehicles and high db mercs visible to all.
-MCC hangars, to allow an additional attacks if the first fails
-Clone reserves, if an attack is successful but the attacker has less than 100 clones they can use reserves to reach 100 for a reattack
-MCC repair, damaged MCCs from and enemy MCC destruction return with partial damage relative to how the precious match ended
A good way to balance them out could be to make them slot CPU and PG based to prevent OP warbarges but allow a wide range of customization.
Tying it back to districts, districts can similarly have subsystems
-orbital strike platform
-enhanced radar
-MCC repair
-Clone reserves
-MCC hangars
-Anti warbarge cannon
-Similar stat enhancers for EVE support
-increase resource (clone, Isk) rate
By keeping district subsystems modular as well it allows district usefulness as far as clone and ISK generation are concerned to be independent, for future possible EVE interaction
Main systems to replace current ones being
-ISK generation (continuosly)
-Clone generation (continuosly)
-Warbarge hangar, this is where a corp would house warbarges, this is where they repair. Useful to shorten distance warbarge must travel
-Warbarge factory to produce smaller warbarges.
Reserve warbarges would function just like the Corp warbarges except, they'd have more limited slots, and would have to be assigned to a warbarge Hangar, if the district with a warbarges hangar is lost, the warbarge must be assigned to an empty hanger or it's deactivated at the corps HQ station where it is unusable until a hanger is assigned. The corps HQ station can always function as a warbarge hangar for the Corp Warbarge, but the corp warbarge can also rebase at a district hangar.
cont..
"F*ck the polis" - Socrates
|
Tallen Ellecon
KILL-EM-QUICK
RISE of LEGION
2089
|
Posted - 2015.01.22 21:10:00 -
[2] - Quote
.....
cont
As far as WB destruction.
reserve Warbarges can be destroyed. A Corp warbarge cannot be destoyed, if it takes 99% damage it immediately warps out and heads straight back to it's hangar. The merc managing the warbarge can give it a set damage threshold before warpout, but the align time means a high max damage taken can still allow WB destruction. A low max damage threshold is conservative but it would negatively impact the rest of the battle. At that point for the attacker there can be no clone reinforcement from reserves, no warbarge strikes, no retreat, no MCC repair, or any other benifits the warbarge gave. For the defender a lost or retreated WB functions just like it would if it was never there, unless of course the district in conflict was the home of the warbarge in which case a district conquest would result in WB destruction (or possible capture).
Battles would be similar to before but attack functions would go through those in control of a warbarge, a merc would need to be assigned and have the skills for each function built in. Assignments can be based off CEO preference, allowing whoever is available with the privledges and skills to be eligible, set up a function so only the currently assigned merc or director can reassign a warbarge A CEO or director can order an attack, and choose a warbarge and clone source, but the details would have to be done by someone assigned to that warbarge. Based on the warbarge's MCC and clone reserves, and those of the hangar in which it's based the assigned merc dictates the subsystems used (if available), the posture (aka damage threshhold, aggressiveness (only attack opposing alliance, shoot on site, only fire when fired upon), the composition and order of attacks. By default attacks would function like they do now in case no assigned merc was there to change any details, the default shield and non aggression would come into play.
The assigned merc could have the option to set up automatic functions in case they were unavailable or were busy fighting. They can also change actions manually at any point. For example, the assigned merc could set it up so the WB would not automatically reattack if the enemy clone count was over a certain number after the first battle. This can get more complicated but the control of the assigned merc could become greater as the whole WB system expands. Maybe even give the ground commander to get updates on the warbarge and give them the ability to change functions based on how the battle is going.
To take a district the attacker must destroy all the defenders clones, each defender MCC destruction nets up to at least 150 clones lost like now. In order to stop further attacks the defender must destroy all the enemy MCC, clone reserves, or destroy or route the attackers warbarge.
This was long, and it's not meant to be a perfect system but it's just some stuff to look at. I won't even go into the economics or the details of how things are acquired, I'll leave that to the devs.
TL;DR
AI controlled WB in EVE
Merc controlled WB functions
Enhaced WB and District Subsystems and Infrastructure
More control over multiple battle aspects in real time
"F*ck the polis" - Socrates
|