Shield bypassing weapons?

I was recently attacked by two Corvettes and while I would normally take them on, I decided to FSD away as soon as my modules started to malfunction, which happened in the first 7-10 seconds of the fight.

My Corvette's shields were on half strength, but that was mostly thanks to all Shield Boosters being destroyed and heat was around 50-60%.
Those guys never managed to get past half of my shields, yet they managed to destroy a lot of my modules and severely damage (40-60% integrity left) the rest, however, my two Module Reinforcement Packages were almost undamaged (around 92% integrity left).

I know there's Phasing Sequence, but it shouldn't be this powerful from what I've read....then again, I was being shot at by two Corvettes...

1. What else could they have used to do this?
2. How to counter this?
3. What's the point of MRP if it doesn't protect my Modules?
 
My guess is that you may be incorrect about your heat during this fight. There is a mod for lasers called Phasing Sequence, which does allow a small percent of damage to bleed through shields and hit the hull. This damage does not impact modules, so would not have caused malfunction.

As far as I know (and I could totally be wrong, I am still relatively new!), heat damage is the only way your modules could have malfunctioned while having active shields.
 
They got me also. Makes shields useless. One corvette. The one with letters and dots in his name is the one that's generating the heat. He has cannons but that's all I know. Kinda frustrating. I love the Engineers but it always seems I'm a day late and a dollar short to the party. It's all about the heat. Back to the drawing board.
P.S. No sport in what their doing in the Kaal system. If you want to dominate. Do it till the opponent is your play toy then move on. I don't log but I will if these two yank me again.
 
Last edited:
It's quite obvious what their doing, one is set up to take out nothing but shields and as their doing that the other is set up to attack nothing but hull. Neither one could do it alone. It takes two. Hence logging out on them is conducive to their style of play and more than likely the only way to either stop them should everyone do it. Or just as a way to learn to stay away the next time.

I would concur that FDev is not going to consider the antics of phychotics when they incorporate a combat logging prohibitation policy and or any punishment for doing so. They are doing litterally, nothing wrong within the confines of playing in open. If deliberate griefing is going to be allowed, than so should deliberate logging. If logging out becomes an real offence which can have possible ramifications, then so should griefing.
 
My guess is that you may be incorrect about your heat during this fight. There is a mod for lasers called Phasing Sequence, which does allow a small percent of damage to bleed through shields and hit the hull. This damage does not impact modules, so would not have caused malfunction.

As far as I know (and I could totally be wrong, I am still relatively new!), heat damage is the only way your modules could have malfunctioned while having active shields.
I checked and I was not receiving Heat damage. That was the first thing that occured to me.

It's quite obvious what their doing, one is set up to take out nothing but shields and as their doing that the other is set up to attack nothing but hull. Neither one could do it alone. It takes two. Hence logging out on them is conducive to their style of play and more than likely the only way to either stop them should everyone do it. Or just as a way to learn to stay away the next time.

I would concur that FDev is not going to consider the antics of phychotics when they incorporate a combat logging prohibitation policy and or any punishment for doing so. They are doing litterally, nothing wrong within the confines of playing in open. If deliberate griefing is going to be allowed, than so should deliberate logging. If logging out becomes an real offence which can have possible ramifications, then so should griefing.

That's the thing, they didn't break my shields and hull was around 97%.

Was it railguns - Super-Penetrator?

https://inara.cz/galaxy-blueprint/60/ (on right)

(No expert ;))

The description would certainly fit and they did ram me at first, so they were close enough to just spam this.


Ok, still, how do you defend against this?
 
1 against 2, there is no defense. 1 on 1 the best defense is a good offence I guess. I have the same questions as OP. My Vette runs hot if I have a smoke within 50' of my ship. Is my Vette more susceptible to the opponents weapons because I'm close to running hot to begin with ?
 
Best to always lock a neighboring system. The moment you see you're getting ganked, high wake out. Really the only defense.

Also if you naturally run hot, then thermal shock is likely to be more of a problem for you.

Also the mrp has a certain amount of integrity just like the modules. It can only absorb so much punishment. If you have an afm you can repair it to keep the damage reduction there. Kind of a pain, but it's not like you can just repair your thrusters mid fight.
 
I had a neighboring system locked. The FSD would get jacked before I could jump. I boosted away trying to jump for probably 2 minutes but they were both to close to me and I waited to long. I pulled one of them out of SC after I did some repairs. He was alone and within 10 seconds my modules started to get all wonky. It's frustrating to try to figure out the engineers. Yet at the same time its cool that it gives me something to do. Well its back south to run some taxi services. Those two cmdr's were the first two I ever blocked. Then I unblocked them, not sure why, I guess I don't like that feature. Love this game. It's not perfect but its still great ! o7
 
  • Like (+1)
Reactions: ste
My bet is these people have googled every exploit in the book, grinding in solo to get a fed corv, if you did manage to get there shields down they would be yanking out the internet cable before you could say pathetic.

And this is why I say to the people saying cheating and using exploits dont effect us youre talking out of your fer de lancing asp.
 
Last edited:
I think it can be 2 things, thermal cascade cannons or phasing sequence pulses/bursts.
But due to the description that your MRP's weren't touched and the heat....i would say it was the misuse of the currently bugged thermal cascade cannons. Getting hit by 2-4 of them can kill your modules and hull in lesser than 10 seconds.
You were lucky that you got out there. I hope FDev's fix finally those buggy basta.....sry...those buggy boys :D
 
I think your right. One of them I couldn't lock on for the life of me which I found strange. I wanted to see what he was packing before I blew up, but no matter how many times I hit the target button I couldn't get a lock, not even for a second. Is that even possible ? The other had cannons. I'll have to pick up that exploit. Don't like to do it if it's an exploit however if its the only way to remain competitive......?
 
I think your right. One of them I couldn't lock on for the life of me which I found strange. I wanted to see what he was packing before I blew up, but no matter how many times I hit the target button I couldn't get a lock, not even for a second. Is that even possible ? The other had cannons. I'll have to pick up that exploit. Don't like to do it if it's an exploit however if its the only way to remain competitive......?

Don't do it, you will regret it. These cannons are an iWin button and will be removed sooner or later anyways. That you weren't able to get a lock onto him can has also multiple reasons. Silent Running, low emmission powerplant grade 3 (my SR Anaconda can boost with clean drives and doesn't get beyond 18% heat) and/or heatsinks, or just the usual Target Lock Breaker mod on PA's. If put on Dentons advanced PA's you should better don't even try to get a lock and fire just on sight with fixed weapons.
 
There is the report function in-game, though I don't know if Frontier would consider what they are doing as punishable.
Otherwise, if anyone is harassing just block them and they won't show up again in your instances - they'll be in your contact history.
 
There is the report function in-game, though I don't know if Frontier would consider what they are doing as punishable.
Otherwise, if anyone is harassing just block them and they won't show up again in your instances - they'll be in your contact history.

How does one block?
 
Their antics really don't effect me much. This game is huge and my experience doesn't depend on Kaal. They are getting together and seeing how dominating they can be. Which helps others understand the game ultimately. And the way they work together is cool. Like I said earlier once your opponent is a play toy let them go. I don't like how unimportant the shields become though.
 
I checked and I was not receiving Heat damage. That was the first thing that occured to me.



That's the thing, they didn't break my shields and hull was around 97%.



The description would certainly fit and they did ram me at first, so they were close enough to just spam this.


Ok, still, how do you defend against this?

Was it railguns - Super-Penetrator?

https://inara.cz/galaxy-blueprint/60/ (on right)

(No expert ;))

Fair enough...but I still am not sure we have identified a mechanic that allows module damage with an active shield! Super pen. rails do not go through shields, so those are out.

It is going to be hard to figure out a counter if this can't be replicated and we can't identify mechanics that would have allowed for the reported variables here!

Edit: It is possible they were using reverberating cascade mines, but your shield generator would be the only module taking damage as far as I know.
 
Last edited:
It's probably like Lucius-Darcia said and maybe the cannons will be fixed in the next update. I think the mechanic is the effect of thermal-cascade cannons. They fry you. If you hit your SCB over and over it will fry me in the same way. It's all about the heat. They cook you to death.
 
Last edited:
Back
Top Bottom