Quote:
It's part of the zone. |
Originally Posted by Caelwn_NA
I've just been in to Warburg for the first time and noticed that I don't seem to be able to attack the target of my (friendly, party member) target, I get 'Invalid Target' when targetting the party member and attempting an attack. I play in duo, normally healing my meat-shield in between shooting fiery bolts at his target, and I find that much more convenient than manually switching targets between him and whatever he's shooting. Is this something that is disabled in Warburg?
Come to think of it, this may specifically be in The Web. When we were ungrouped in the villain base he was blue to me, but when we ungrouped in The Web to see if regrouping would help he turned out to be red to me (sort of embarrassing given that I'd just clicked him to select him and rebuff, and ended up blowing him up). I'm guessing it's a facet of the zone but I wondered if anyone could tell me for sure, it's really painful not being able to do target of target attacks. |
Warburg is the only zone in which you can attack a person of the same faction as yourself that is not on your team. It's a coding thing.
In the rest of the game, the CPU sees that you are targeting your teammate and does the calculation to determine that you are trying to attack what they are targeting.
Warburg doesn't have that piece of code in it. Since a team member is the only thing in the zone you CAN'T attack, the CPU simply interprets you clicking an attack while targeting your teammate as an attempt to attack that teammate, which the code of the zone will not allow you to do.
My theory on the reasoning for that is that your teammate can become an enemy at ANY point in time, either by them quitting the team or you kicking them, at which point they become a valid target again. Seems to me like they did it that way to make things easier on the processor by not forcing it to figure out what you're trying to do there. If it DID force it to try and figure it out you would end up with a lot of bugs in which your attempt to attack your teammate's target resulted in an attack on your teammate instead. Which would really suck if you hit your scrapper or brute buddy with a nasty debuff by accident.
Instead of leaving a system in place that would probably have bugs sprouting up every other week they just made it so any attempt to attack while targeting a teammate was considered invalid.
Quote:
|
Originally Posted by Dechs Kaison See, it's gems like these that make me check Claws' post history every once in a while to make sure I haven't missed anything good lately. |
I think the OP was referring to the assist mechanism in general. That does not work for any PvP zone at all, not just Warburg.
You are right about why his friend was showing up as an enemy before they were teamed though. That zone is "Free-for-all". The area within your side's base is a "safe zone" against your own faction tough, which is why he originally showed up as blue until they left that area. You'd have to be on a team to continue to buff a friend outside of that area.
Quote:
Yeah - that's there to prevent things like a blinded player using it to attack things he cannot see, etc.
|
Originally Posted by Master-Blade
I think the OP was referring to the assist mechanism in general. That does not work for any PvP zone at all, not just Warburg.
|
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Quote:
I've always found that reasoning kinda fishy actually. If you are blinded in PvE and try to assist a teammate, it simply gives you the overhead error "Target too hard to see". I don't see why that functionality would work any differently in PvP. |
Originally Posted by Rajani Isa
Yeah - that's there to prevent things like a blinded player using it to attack things he cannot see, etc.
|
I think it's more so that you cant all target your team's leader and go after the same target immediately. You have to all find and select the person you are going after yourself.
Anyway, whatever the reason actually is, the point is that it's supposed to work that way, so it's just something to get used to if you are going to spend time in PvP zones.
I thought that prevention was for Teleport Foe, since TP Foe's range is beyond the range you can normally see opponents. If you can't target through someone else, you can't have them help you TP-gank someone.
http://www.fimfiction.net/story/36641/My-Little-Exalt
Quote:
i thought TP Foe's range was considerable shorter than that, but it's been a long while since i used it, so i'd have to go check.|
Originally Posted by Fleeting Whisper
I thought that prevention was for Teleport Foe, since TP Foe's range is beyond the range you can normally see opponents. If you can't target through someone else, you can't have them help you TP-gank someone.
|
Edit: According to the entry at City of Data the range of TP Foe is 200 feet. That's considerably shorter than perception range.
Still, as i recall from when it was implemented, not being able to target through teammates was intended to make coordinated damage spiking a bit more difficult. Having to target the called enemy while in a scrum is much less convenient than simply selecting the designated targeter for the group and opening fire whenever they say "Kill!"
Dr. Todt's theme.
i make stuff...
Quote:
It's also to make coordinated strikes require at least a tiny bit of skill
|
Originally Posted by Fleeting Whisper
I thought that prevention was for Teleport Foe, since TP Foe's range is beyond the range you can normally see opponents. If you can't target through someone else, you can't have them help you TP-gank someone.
|
It's all these reasons and maybe a few more. It is pretty important for pvp.
Originally, you were able to target through people, as well as use targeting binds. Of course this led to retardedly high scores in arena matches because only one person needed to find a target. They removed that ability and the use of binds stayed around for a while, but that got changed too and now the only way to target someone is to tab onto them or click them.
@macskull, @Not Mac | XBL: macskull | Steam: macskull | Skype: macskull
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
It also makes dual-boxing more difficult in PVP, which is a good thing.
eg You can't have a back-up Defender targetted on you on follow, buffing you and blasting your targets.
Thanks for the info everyone. I generally play in fairly quiet times so I've not actually met anyone in the zone anyway. The whole PVPness of it hasn't yet been driven home 
Manual targetting is sort of working, I'm sure I'll get better at it over time.
I've just been in to Warburg for the first time and noticed that I don't seem to be able to attack the target of my (friendly, party member) target, I get 'Invalid Target' when targetting the party member and attempting an attack. I play in duo, normally healing my meat-shield in between shooting fiery bolts at his target, and I find that much more convenient than manually switching targets between him and whatever he's shooting. Is this something that is disabled in Warburg?
Come to think of it, this may specifically be in The Web. When we were ungrouped in the villain base he was blue to me, but when we ungrouped in The Web to see if regrouping would help he turned out to be red to me (sort of embarrassing given that I'd just clicked him to select him and rebuff, and ended up blowing him up).
I'm guessing it's a facet of the zone but I wondered if anyone could tell me for sure, it's really painful not being able to do target of target attacks.