I'm fracking sick of solo killing 1-3 players guarding a point, going to hack either the point or CRU, and dying because invisible, invincible mercs spawn in behind me. They failed to defend the point, I succeeded in assaulting it, yet unless I kill them all at the same time right next to the console, I'm nearly guaranteed to die (10 seconds to hack - 10 seconds to spawn = 0 seconds to start hacking after the kill). This issue is particularly bad with CRUs- point spawns often don't spawn you near the console, but CRUs spawn you right next to it.

Yes, I know, complex codebreakers, systems hacking skill V, and Min logi would make this a non-issue, but it shouldn't be a problem in the first place.

Almost like you would want someone there with you to watch your back or make the hack faster... but that would require teamwork, and as we all know, this is "I HAS TO SOLO ERRYTING WAHWAHWAH 514"

Hack skillz yo.

I seriously stopped reading after your first sentence. "Solo" is a 4-letter in DUST 514.

Don't solo hack crews or objectives, unless of course you're a Prototype Minmatar Logi with level 5 hacking and a complex codebreaker equipped. Or you have flux in the pocket.


I do think that AI turrets should stop shooting when they are getting hacked.

What makes solo so automatically bad? Yes, sure, I'd get slaughtered by any competent pair of communicating mercs, much less a proper corp squad, but I'm a casual player playing pub games- the majority of my enemies are clueless redberries. I can't pull this off every time, but when I do I feel like I'm being robbed of my reward despite having beaten my opponent(s). The point of FPS games is to shoot the enemy... if I can kill everyone guarding the point without help, don't I deserve the hack?

We shouldn't be allowed to spawn on objectives at all. It makes placing uplinks in strategic areas redundant.

I was under the impression you already can't spawn on an objective being hacked? (Which is silly btw, spawn should remain until virus completes the takeover).

I stopped instigating hacks on red objectives long ago when I am lone-wolfing...

I should not need team support to successfully hack a point when I successfully infiltrated it ALONE, successfully killed all enemies guarding the point ALONE, and successfully destroyed all equipment at the objective ALONE.

And nevermind that spawning on objectives almost entirely kills the need for uplinks in skirmish.

I'm fracking sick of solo killing 1-3 players guarding a point, going to hack either the point or CRU, and dying because invisible, invincible mercs spawn in behind me. They failed to defend the point, I succeeded in assaulting it, yet unless I kill them all at the same time right next to the console, I'm nearly guaranteed to die (10 seconds to hack - 10 seconds to spawn = 0 seconds to start hacking after the kill). This issue is particularly bad with CRUs- point spawns often don't spawn you near the console, but CRUs spawn you right next to it.

Yes, I know, complex codebreakers, systems hacking skill V, and Min logi would make this a non-issue, but it shouldn't be a problem in the first place.

You want to work alone... in a team game. So, how is CoD?

I love how people always bring up CoD.

Yeah skill into hacking or just be like me and camp the CRU and kill everything that comes out. *Shrugs*

Really? How odd. Wonder why

Ok:
"Really?" No. I don't love it. Sarcasm.
"How odd." No, not really.
"Wonder why[?]" Doubtful. As you already know, as do I.


Now, as to the actual topic that some people seem to be ignoring:

Evidently, some don't realize that you can be a member on a team or a person in a squad, and do certain things ALONE in order to help your team.

To make things clear:

Large battle at objective [A].

Me, in a Minmatar Logi, speak with my TEAMMATES with my mic. We decide that because of the large battle, enemy defences at point [C] on the other side of the map will be lacking. So my TEAMMATES decide that due to the big battle, they have to stay and defend [A], but send me to point [C] ALONE, as they can only spare one person. I go ALONE, avoid enemy detection, arrive at [C] ALONE, destroy the uplinks, flux the REs, and kill the enemy or two there. I then begin my hack. ALONE. Because it should be just a one person job. But it is not, due to the stupid "spawn-on-objectives" mechanic that should not be in the game.

Now, sorry for being ALONE, doing what is beneficial to my team, and using these things known as TACTICS. I guess that means I like CoD, and have a "ME ME ME"-mentality.

*Note: CAPS for emphasis only.

No. We have to learn to counter that. I don't want a safeguard for everything. I want that element of danger there.

Plus, you need to be listening to your audio. Once you hear a "wurrrrrowurrr" that means someone spawned in and you need to pull back to get the drop on them before you. Obviously they know you're hacking it, so stay one step ahead.

Let members on your team know about this. Communication is key. But putting a safeguard? You can't buff or nerf the player unless they decide to do that on their own. Until then, the training wheels don't need to be on everything.

This isn't Sesame Street. It's New Eden