only ranged FF reflective?

[hippy_with_a_scimi]

Mr Shine is right. 

Any tk penalty can be used for griefing. Just step into their swing / line of fire at the right time and *boom*, gotcha. Hahah, i made you lose xp and gold.

No way around that, i think. 

 that jump in their swing \ line of fire excuse  has to go , we cant have a serious talk with that getting spit around the thread  either with or without FF ,  people will always do that. 

 

   

[Phazey]

the fact an archer will almost always have a target on the field that he can fire at without risking hitting a team mate, which is what he should be doing.

Sorry, but that's just not true. Take, for example, the end of a round. You (the archer) and one of your team mates, a peasant, are still alive facing one two hander wielding tincan.

The tincan engages the brave peasant. The peasant turns out to be a reasonable blocker (recently retired player maybe) and manages to stay alive for 30 seconds whilst desperately blocking the tincan's swings. Maybe he even gets a hit in himself.

Should you not fire at that tincan? Ofcourse you should! You try to manoeuvre into a favourable position but not shooting at that tincan, even though you risk hitting the peasant, is just stupid.

Reflective damage for ranged is lame and it will not fix your 'problem'. People will still get teamhit by ranged, but now it will suck even more because the ranged tends to drop dead at odd moments due to reflective damage.

In short, reflective damage sucks. 

[Wookimonsta]

+1, best idea i heard all day

[The_Bloody_Nine]

This is practically all that is needed to know to state that reflective damage is no good. I stand by Phazh's comments like a fanboi on this one, a much clearer and better way of saying what I wanted to say and failed to do.

Well yeah, kind off misunderstood you there then.

To the sound of Phaz!

[Tennenoth]

Well yeah, kind off misunderstood you there then.

To the sound of Phaz!

To the sound of Phazh! xD

[gazda]

I have a solution

Our hero legolas shoots into melee, and hits, but no, oh god is it true, he hit a TEAMMATE. God almighty gets very furious and punishes our poor legolas by punishing his damned eyes.*

*edges of the screen get transparently blackened periodically by each shot, so the angle of sight gets smaller and smaller

[Raki]

Tbh, I'd rather have 2-3 friendly archers try to help me kill one person than joining a ganking squad to kill said person. I get shot by a friendly archer maybe once or twice a week. On the other hand, join a ganking squad (not talking about organized killing squads from one clan or something) and you can bet your life on it there's going to be at least one teamhit. I'd go as far as saying that there's a pretty big chance that your team ends up damaging itself more than it damaged the other team.

So yeah, I know getting teamhit by an archer sucks, but adding FF is a bit too much.

Also, if an archer sucks at shooting and yet can't help but play Legolas, his team will probably tell him to find another class.

[The_Bloody_Nine]

Regarding the problem of being shot in the back while in melee:

I rage like mad if I'm in a one on one, have everything under control, and feel like having a good chance of beating the enemy and boom - a friendly arrow in the back and I get finished off in two secs. It can be even worse with cav, I dehorse an enemy, go in for the killing strike while he's on the ground and boom - a friendly cav tks me.

Those situations are extreme and extreme unnecessary, but in most cases people say sorry for it and mean it as far as I can tell. I tried cav and archer alts as well and of course I did some stupid teamwounding now and then, but reflective damage surely would not make it feel more wrong. Sure it is possible and likely that there are a few assholes out there who don't even feel a bit sorry for it, but reflective damage would mean too much sacrifices in therms of immersion and gameplay.

[Summer Glau]

Archers = overpowered 100% confirmed tbh plz nerf/ban ASAP imo tiatiatia

[The_Bloody_Nine]

nvm, sarcasm detector fail.

and you changed your post