CCP would probably just take some of the ideas in consideration, take 5-6 months to make the changes, and then poorly execute the new mode.

The code is available to have one terminal control multiple assets. What was interesting to learn, it can control the owner of any asset, not just null cannons. This can be used to make the current skirmish a little better while we wait for 3.0.

How it works - add a new console, the "Defense Command Terminal". If your team captures it, all turrets on the socket belong to you. To make this meaningful, all turrets would no longer be hack-able individually. An additional "Support Command Terminal" would do the same for CRUs and supply depots.

What it means - you have new objectives that don't directly help you win, but are still necessary to balance your tactics around. It spreads out important places to be which penalizes zerging. It make the turrets themselves more valuable since taking over the socket will flip the entire perimeter defense at once, not just the current location that is likely already cleared.

When is it - it could happen very quickly, before Uprising 1.2 even, but only if the community wants it because it would replace entirely the current mechanics if introduced for Skirmish, and would be unwise to introduce as a new queue at this time. So does this appeal to you? Why? Does it sound terrible? Why not then?

Also, turrets need at least supply depot health, it's silly they can be 1-2 shot by common fits. But that only partially is on-topic.

Once turrets are player dropped, we don't want a zerg of super strong turrets do we? We will probably have a good deal of them showing up once you guys can call them in. Those should be the ones you guys can fit to be stronger. My personal opinion on that anyways.

The code is available to have one terminal control multiple assets. What was interesting to learn, it can control the owner of any asset, not just null cannons. This can be used to make the current skirmish a little better while we wait for 3.0.

How it works - add a new console, the "Defense Command Terminal". If your team captures it, all turrets on the socket belong to you. To make this meaningful, all turrets would no longer be hack-able individually. An additional "Support Command Terminal" would do the same for CRUs and supply depots.

What it means - you have new objectives that don't directly help you win, but are still necessary to balance your tactics around. It spreads out important places to be which penalizes zerging. It make the turrets themselves more valuable since taking over the socket will flip the entire perimeter defense at once, not just the current location that is likely already cleared.

When is it - it could happen very quickly, before Uprising 1.2 even, but only if the community wants it because it would replace entirely the current mechanics if introduced for Skirmish, and would be unwise to introduce as a new queue at this time. So does this appeal to you? Why? Does it sound terrible? Why not then?

Also, turrets need at least supply depot health, it's silly they can be 1-2 shot by common fits. But that only partially is on-topic.

Why not have three turrets?

Small: Like the ones that vanished shortly after Craterlake, hackable, low HP, droppable, great AI to make them a severe threat against infantry if not controlled, customizable by players in the future.

Large: Like the ones we have now, customizable by players in the future and droppable.

Fortress: Ones even bulkier then the ones we have now with significantly more HP, NOT droppable, customizable in the future by players for player bases thus already present at the start of a "game," NOT hackable and activated by hackable terminals in a network. This third type could be considered a "new" or "separate" type then the normal turrets (like our Null cannons) if that would be easier code wise then modifying current turrets to be hackable or not.


The new "fortress" type would allow you to not worry about super-HP turrets being deploy-spammed as they are a visibly separate type of turret that are restricted to being part of a static base network.

wouldn't this be a indirect nerf to hacking skills
since it would be used less there is less reason to spec into it

While you're here, Logic... is this not a slight modification of the code used in the old alpha builds?

When we hacked a point weapons and spawn points would spawn in. Why can't we just do that and 'lock' the modules dropped down to be unhackable?

I get the map guys may need more time to work on it, but I don't see it taking an incredibly long time. All the code and assets are there for both systems (Old alpha game mode + Ambush OMS).

They just need tying together, surely?

The code is available to have one terminal control multiple assets. What was interesting to learn, it can control the owner of any asset, not just null cannons. This can be used to make the current skirmish a little better while we wait for 3.0.

How it works - add a new console, the "Defense Command Terminal". If your team captures it, all turrets on the socket belong to you. To make this meaningful, all turrets would no longer be hack-able individually. An additional "Support Command Terminal" would do the same for CRUs and supply depots.

What it means - you have new objectives that don't directly help you win, but are still necessary to balance your tactics around. It spreads out important places to be which penalizes zerging. It make the turrets themselves more valuable since taking over the socket will flip the entire perimeter defense at once, not just the current location that is likely already cleared.

When is it - it could happen very quickly, before Uprising 1.2 even, but only if the community wants it because it would replace entirely the current mechanics if introduced for Skirmish, and would be unwise to introduce as a new queue at this time. So does this appeal to you? Why? Does it sound terrible? Why not then?

Also, turrets need at least supply depot health, it's silly they can be 1-2 shot by common fits. But that only partially is on-topic.

That code has been ignored since the implementation of SK 2.0. It just does not function and would require an entire re-write to work the current code.

Why not have three turrets?

Small: Like the ones that vanished shortly after Craterlake, hackable, low HP, droppable, great AI to make them a severe threat against infantry if not controlled, customizable by players in the future.

Large: Like the ones we have now, customizable by players in the future and droppable.

Fortress: Ones even bulkier then the ones we have now with significantly more HP, NOT droppable, customizable in the future by players for player bases thus already present at the start of a "game," NOT hackable and activated by hackable terminals in a network. This third type could be considered a "new" or "separate" type then the normal turrets (like our Null cannons) if that would be easier code wise then modifying current turrets to be hackable or not.


The new "fortress" type would allow you to not worry about super-HP turrets being deploy-spammed as they are a visibly separate type of turret that are restricted to being part of a static base network.