The Shield discussion thread
- Thread starter NameNotFound
- Start date
Python.
In a 1v1 the Anaconda is a powerhouse but the minute you go up against multiple opponents you can get into trouble fast.
The shield cell change will hit the Conda harder because its such an easy target to hit with any weapon that you need to have a large battery of SCBs to tank the damage.
Plus its power plant is extremely vulnerable in comparison (try taking out a Pythons power plant..)
Ive just sold my entire fleet including my battle Conda and kept the Python. Even after the balance it will still be the king of combat.
In a 1v1 the Anaconda is a powerhouse but the minute you go up against multiple opponents you can get into trouble fast.
The shield cell change will hit the Conda harder because its such an easy target to hit with any weapon that you need to have a large battery of SCBs to tank the damage.
Plus its power plant is extremely vulnerable in comparison (try taking out a Pythons power plant..)
Ive just sold my entire fleet including my battle Conda and kept the Python. Even after the balance it will still be the king of combat.
InMemoriamSirocco
Banned
Stop it right there. I am using a PS 3 Controller emulated as an Xbox360 controller, and I just bound "activate shield cell" to "(A) + [<]".
Problem solved. It is intuitive, because [<] is used for diverting power to shields usually.
Yes, but considering how many different features there are and how many buttons a controller has, you sacrificed a bind (combination) for this feature. This means that you will have to activate some other thing from the side panels- something HOTAS and Keyboard users don't have to and this gives them an advantage. I am arguing that the cost doesn't justify it in that if the module were passively activated, the actual loss of control is negligent as it is required on rare occasions and that therefore the benefit of not having an extra bind outweighs it.
P.S.: great idea, I'll do that myself actually.
Last edited:
InMemoriamSirocco
Banned
It's a pc game, so we also have a whole keyboard at our disposal.
Everything I need to be able to do quickly without searching for the right button I was able to map to my controller. Everything else, like navigating the galaxy map, for instance, I use the keyboard and mouse for.
All functions necessary for combat I can access from my controller just fine.
Everything I need to be able to do quickly without searching for the right button I was able to map to my controller. Everything else, like navigating the galaxy map, for instance, I use the keyboard and mouse for.
All functions necessary for combat I can access from my controller just fine.
Yeah I've been in battles before where I just couldn't trigger the shield cells fast enough... especially when against an opponent who can take them out in two shots. I'm loathe to hit them when I still have two rings remaining but the fact might be I can go from two rings to shields down in a single hit... so it's a choice, do I trigger them now or hope I can make one more sortie on my target before needing them. This at the moment is the shield cells' saving grace for gameplay... and if they were more limited in number (i.e. you can't just fit loads of them) or limited in some other way, like you suggest, or for example using them requires something in your SYS capacitor, then they would be kept as a strategic option rather than a way to arbitrarily extend any fight.
I agree with them in principle, particularly as a defensive option for a fleeing ship such as trader. 4 pips to ENG and two to SYS is the typical configuration of such a ship, and therefore shield cells will perhaps suit them more... and I feel that rightly, taking out a pilot whose mind is set on escaping should be a challenge... even if you are in an anaconda and they only have a hauler.
Last edited:
just make shield cell banks external slots instead of internal ones.. then you need to chose, an extra weapon or a shield cell bank
No, that would be a buff rather than a nerf for me. I use 4 beam lasers on my Viper, when I use all of them on my target the weapon energy is drained within a few seconds, with 4 pips and an A3 power distributor. So if I had one laser less it wouldn't hurt my damage output at all, on the opposite I'd be happy to have a nice internal slot free for something else. It would be different if the Viper had enough energy, but that's the big disadvantage of that thing imho. Half of the time I have a target in my aim but can't shoot because of the drained energy.
Yup you re probably right, does the vulture release on 1.1 too?
In 1v1 or 1vX, the Anaconda is vulnerable to being out maneuvered, but 2+ Anacondas can use cooperative tactics to bring their overwhelming firepower to bear against any opponent(s) that dare to engage them.
While the Pythons Power Plant is better defended than the Anacondas, it's FSD is a real weak spot.
A Python with A rated drives should still be able to out turn an Anaconda, but the changes to shield cells are going to be interesting for each ship!
There's no new ships in this update. I think we have to wait until 1.2, hopefully no longer than that!
A Python with A rated drives should still be able to out turn an Anaconda, but the changes to shield cells are going to be interesting for each ship!
There's no new ships in this update. I think we have to wait until 1.2, hopefully no longer than that!
Shield Cell Suggestions
Personally I think the shield cells are fine the way they are but at the same time should pose a little more risk. My idea is similar to the devs. Basically, my idea is that when used, the shield cells induce a huge amount of energy in order to boost the shield back up to full rate. Make it so that when a shield cell is used, due to the energy, as a safety precaution your ship surge drains your weapons subsystem as well as most from your systems, subsystem, during the course of the shield recharge. This could be accompanied by a warning stating "Warning, Power Surge Detected".. This would make it so that when you use it, you are temporarily unable to retaliate and are thus vulnerable to attack. This would force a person to be far more strategic about when they boost their shield back up instead of sitting in front of an anaconda, blasting away and pressing a key whilst still tearing the enemies shields down. Instead, they would have to retreat whilst the shield recharges and get to a position where the enemy cannot fire whilst his weapons are down due to the shield cell. Also, using the Shield Cells should create a massive amount of heat, almost akin to railguns due to the surge of energy they give the shields, even if it is a recharged battery.
This is another idea for the shield cells. Since they use pre-charged batteries, shouldn't the battery casings be ejected after use? It would be cool if after each use the casings would appear in your contacts and after a battle, providing you lived, could pick up the dead batteries and get them recharged at a reduced price.
Personally I think the shield cells are fine the way they are but at the same time should pose a little more risk. My idea is similar to the devs. Basically, my idea is that when used, the shield cells induce a huge amount of energy in order to boost the shield back up to full rate. Make it so that when a shield cell is used, due to the energy, as a safety precaution your ship surge drains your weapons subsystem as well as most from your systems, subsystem, during the course of the shield recharge. This could be accompanied by a warning stating "Warning, Power Surge Detected".. This would make it so that when you use it, you are temporarily unable to retaliate and are thus vulnerable to attack. This would force a person to be far more strategic about when they boost their shield back up instead of sitting in front of an anaconda, blasting away and pressing a key whilst still tearing the enemies shields down. Instead, they would have to retreat whilst the shield recharges and get to a position where the enemy cannot fire whilst his weapons are down due to the shield cell. Also, using the Shield Cells should create a massive amount of heat, almost akin to railguns due to the surge of energy they give the shields, even if it is a recharged battery.
This is another idea for the shield cells. Since they use pre-charged batteries, shouldn't the battery casings be ejected after use? It would be cool if after each use the casings would appear in your contacts and after a battle, providing you lived, could pick up the dead batteries and get them recharged at a reduced price.
Last edited:
Two things:
Shield cells are being worked on as we speak, so I doubt they're going to listen
There's a suggestion forum that will be more useful for your suggestion.
Shield cells are being worked on as we speak, so I doubt they're going to listen
There's a suggestion forum that will be more useful for your suggestion.
Two things:
Shield cells are being worked on as we speak, so I doubt they're going to listen
There's a suggestion forum that will be more useful for your suggestion.
1. I do realise that but never too late to give ideas.
2. I did that with a couple of ideas but were ground to the dust quickly. Plus this is more up to discussion anyways.
Multiple Shield Cell units
I have an Asp with two A3 Shield Cell units with the "use Shield Cell" button mapped to the joystick - I am NOT using firegroups to activate the shield cells.
.
When I hit the button BOTH Shield Cells fire a charge and it appears to replenish the shields really fast. This happens even if the units are different types, e.g. an A3 and a B2.
.
The question is: Am I gaining a benefit from both cells firing together, i.e. halving the shield recharge time compared to only having one cell? Or is ED ignoring the duplicate cell and the performance is the same as only having one unit?
.
I haven't managed to get a reliable simulation working to get some hard data and I don't want to accidently blow up a 40m CR Asp in the process if I can avoid it.
.
Has anyone any info/done their own tests on this?
.
I have an Asp with two A3 Shield Cell units with the "use Shield Cell" button mapped to the joystick - I am NOT using firegroups to activate the shield cells.
.
When I hit the button BOTH Shield Cells fire a charge and it appears to replenish the shields really fast. This happens even if the units are different types, e.g. an A3 and a B2.
.
The question is: Am I gaining a benefit from both cells firing together, i.e. halving the shield recharge time compared to only having one cell? Or is ED ignoring the duplicate cell and the performance is the same as only having one unit?
.
I haven't managed to get a reliable simulation working to get some hard data and I don't want to accidently blow up a 40m CR Asp in the process if I can avoid it.
.
Has anyone any info/done their own tests on this?
.
Parallel vs serial shield cells.
I'd love to know the answer to that one too.
Using the cell key (via voiceattack) they kept "running out" even when I had more than one bank (four shots not eight), until I spotted they were being fired all at once.
Map a firegroup to one cell, turn silent on/off and drop SYS to 1 pip and then hit cell button once shields come on line. See which method restores most?
I'd love to know the answer to that one too.
Using the cell key (via voiceattack) they kept "running out" even when I had more than one bank (four shots not eight), until I spotted they were being fired all at once.
Map a firegroup to one cell, turn silent on/off and drop SYS to 1 pip and then hit cell button once shields come on line. See which method restores most?
