Quantum Firewall Traps cause the hacker to lose 99.99% of their cloak, but they still manage to hack you. Why?

It should prevent the hack entirely and then lower their cloak. It literally does nothing to protect the person who puts it on. Isn't that the purpose of a firewall to protect? It only serves as an annoyance for the hacker to have to stop for 3 seconds to use a null, or if they are low enough rank stop them for 2 hrs. It should prevent the hack and cause the hacker to lose their cloak. That way they have to use a Time manipulator in order to successfully hack someone.


Compromise:

Right now if the hacker is successful the trap triggers, meaning if they fail they get no punishment other than having to wait 5 minutes or use a TM. This should definitely not be the case, they should be hit with the trap regardless. Onicrons, thetacrons krionus virus and halcyon don't wait until the person is gets disabled to trigger (sometimes it happens and it is funny especially the halcyons but that's another topic). So why does QFTs only trigger on only on successful hacks? It should hit the person attempting to hack even if they fail to hack, just because they are incompetent hackers they get off with nothing? if anything that should be the reason they get hit with the trap. It prevented them from getting to the database and did its job.

I think the QFT should be programmed to launch a follow up hack after reducing their cloak.

That makes it virtually impossible to hack if your low ranked. Having to wait 2 hours, you'll have to hack someone else, and then they'll have a QFT, and it continues.

It doesn't make it impossible, just tougher. And it is more likely that they at lower ranks will keep hitting qft's if they are hacking those of much higher ranks, but at their similar ranked opponents it should be mostly an equal opportunity. It should be tougher for a lower ranked ship to be able to hack a higher ranked ship anyway, just as it would be for them to try to disable a higher ranked ship. They should suffer the consequences of trying to hack a high ranked ship in the same way, with needing to wait longer to hack again, or make sure they have a supply of null fuses.

+1 need update for QFT.

+1 qft do nothing to protect your ship .. the only thing they do is prevent the hacker from doing the same to another ship .. so you are only applying a trap for anothers benefit .. which is silly ..

Sums up my point exactly

+1 from me, it's basically a useless trap and a waste of a null as it is.

I've been double QFTed at least four times now. It's painful to sit there and wait 2 hours to hack again, just to trigger another QFT. In two days I triggered 8 QFTs and been QFTed twice during one of those sessions.

Something needs to be done about QFTs. It shouldn't punish the hacker rather protect the player from being hacked, or better yet, a QFT should increase the chance that a hacker fails to hack someone.

yeah I wondered that too. this needs to be changed... +1

+1

Making the trap more effective and/or more painful would take away the excuses slow rankers have as well. i'm tried of seeing rank 60 ppl refusing to rank because they're trying to get 2k hacks to get onto the leaderboard. Doesn't happen much in my legion but i've heard stories.

+1 to changing QFT's at low levels they are to over powered running into one is more or less akin to a 2 hour legion alert you will get your rear handed to you the whole 2 hours at higher ranks its a joke even me who does a modest amount of hacking i wont even bother to use a null on it more or less just beating the hull off there paint (yes i meant it that way) for wasting my time and stopping me from getting hacks for 2 hours.

*ahem* only 1578 hacks are needed to get on the hack leaderboard.

so, 1077 to go for me

as for the QFT, i think it's working as designed. the double QFT popping off the dark pyramid sux, but that's part of the challenge ... if you want to play the slow rank style, you must accept these kinds of sacrifices

as for providing a benefit to the person who sets the trap ... how about making it zero their hack actions ?