only ranged FF reflective?

[Armbrust_Schtze]

this is the ultimate solution. it prevents archers from shooting noobish into melees, but doesnt disturb the infantry by doing their work..

good idea/bad idea?

[Gisbert_of_Thuringia]

Pf.

Most teamhits are done by melee chars, because half the server is stupidly slashing around.

Why do you want friendly fire for archers only, when they are the smaller number of teamhitters?

[Arrowblood]

Pf.

Most teamhits are done by melee chars, because half the server is stupidly slashing around.

Why do you want friendly fire for archers only, when they are the smaller number of teamhitters?

[Teeth]

I dont get why we dont have full reflective damage.

[Jacko]

No, no. Melee teamhits are a much bigger problem then friendly fire ever will be.

Also, reflective damage is silly.

[Slamz]

I agree that reflective damage is silly.  If anything, look into a Planetside style system where you have a certain pool of team damage you're allotted.  This pool decays over time by itself.  If you exceed your limit, you are booted into spectator mode until it decays back under your limit.

e.g., you can do 1000 points of team wounding before you get auto-booted.  It decays at a rate of 150 points per hour (online or offline).  Back-to-back damage gets a multiplier though so if you start massacring teammates you'll hit that limit long before you actually do 1000 damage.  It's meant to allow "accidents" while punishing rampant teamwounding.
 
It was probably the single best idea in Planetside and it worked really well to keep intentional (or needlessly reckless) teamwounding under control.

[bagge]

Also, reflective damage is silly.

Indeed.

[The_Bloody_Nine]

I dont get why we dont have full reflective damage.

reflective damage is silly.

.

[Tennenoth]

I might be taking this a little too personally but ranged friendly fire is normally the fault of the person who was hit by it, now, don't get me wrong, there are loads of times I have fired into melee and hit my teammate, ironically it's normally 5 to 1 odds against my ally, the soul reason for me shooting to help him out but in reality, the main reason we don't have reflective damage is because you don't want to punish the better players in order to save a peasant.

For example, if I shot into melee where I hit an allied peasant, with no reflective, i'd kill the poor bastard and have more of a chance of taking out the enemy with a sorry shortly followed, yes i've ruined that guys game, but he will get over it and he might even get a multi for it while if it was reflective, it would have killed me, the peasant would have stood no chance and had his arms ripped off by the angry flamberge wielding, pot helm wearing, dagger throwing strength ninjas and there would be less of a chance for the team to win.

It's the same for melee, as people have said, more team damage is done by melee than it is by ranged, therefore, if for example, lets say... Tor... He swings and a peasant dives in the way, he gets the epic damage from his ridiculous axe and cuts himself in half, yeah, peasant gets away fine, ripped apart by the enemy while Tor can't go on his 10 kill streaks.

Not a great idea, reflective is a good idea in theory, but bad in practice because it punishes people who don't deserve to be punished.

[The_Bloody_Nine]

I might be taking this a little too personally but ranged friendly fire is normally the fault of the person who was hit by it, now, don't get me wrong, there are loads of times I have fired into melee and hit my teammate, ironically it's normally 5 to 1 odds against my ally, the soul reason for me shooting to help him out but in reality, the main reason we don't have reflective damage is because you don't want to punish the better players in order to save a peasant.

For example, if I shot into melee where I hit an allied peasant, with no reflective, i'd kill the poor bastard and have more of a chance of taking out the enemy with a sorry shortly followed, yes i've ruined that guys game, but he will get over it and he might even get a multi for it while if it was reflective, it would have killed me, the peasant would have stood no chance and had his arms ripped off by the angry flamberge wielding, pot helm wearing, dagger throwing strength ninjas and there would be less of a chance for the team to win.

It's the same for melee, as people have said, more team damage is done by melee than it is by ranged, therefore, if for example, lets say... Tor... He swings and a peasant dives in the way, he gets the epic damage from his ridiculous axe and cuts himself in half, yeah, peasant gets away fine, ripped apart by the enemy while Tor can't go on his 10 kill streaks.

Not a great idea, reflective is a good idea in theory, but bad in practice because it punishes people who don't deserve to be punished.

I am all against any kinds of reflective damage, but this argumentation sucks IMO. Peasant deaths are Ok as long as you help the team? no thanks.

[Tennenoth]

I am all against any kinds of reflective damage, but this argumentation sucks IMO. Peasant deaths are Ok as long as you help the team? no thanks.

Read a little more into it... I didn't say they were ok, I said that being punished for a mistake and then coupled with punishing your team at the same time isn't good for being able to punish a few who intentionally teamattack.
It's not a matter of "it's ok to kill peasants if it helps your team" it's a matter of how best to punish the people intentionally teamattacking without punishing all the others who don't do it intentionally, whether or not directly or indirectly.

EDIT: That's what admins are there for, to punish the idiots who think it's ok to teamattack/kill intentionally.
Just to rid people of getting hit by archery fire because of a miss-shot would lead to mass griefing of people intentionally jumping in the way of arrows in order to cause the firing archer harm. That's another negative on reflective damage of any kind, it would increase the work load of admins for one thing and it would increase the amount of griefing, and instead of having Teamwounding/Teamkilling collectively being the main banning, it would have griefing.

From a players point of view, an archers point of view & and an admins point of view, this is a silly idea that would lead to more harrassment and abuse of other players.

[Blondin]

Reflective damage is for pussies, the ultimate solution is Instakill!!
Whenever an archer hit you, he's dead!!

Btw, why only archer...? This doesn't apply to xbowmen?

Silly proposal...

[Henry_Broodsonson]

Melee/Ranged
       \  /
        \/
        /\
       /  \
 Good/Bad

[Teeth]

I'm sure this point has been covered thousands of times but what is wrong with reflective damage? They guy that makes the mistake gets punished by it, instead of the unlucky bystander. No more getting killed because your teammate hits you and interrupts your block just before the enemy's flamberge will cleave your head.

[The_Bloody_Nine]

Read a little more into it... I didn't say they were ok, I said that being punished for a mistake and then coupled with punishing your team at the same time isn't good for being able to punish a few who intentionally teamattack.
It's not a matter of "it's ok to kill peasants if it helps your team" it's a matter of how best to punish the people intentionally teamattacking without punishing all the others who don't do it intentionally, whether or not directly or indirectly.

mh, maybe I'm too pricky on that but I still don't like the sound of your argument.

However, of course I agree that ff would only worse the situation and not help at all neither in therms of punishment nor gameplay.

I'm sure this point has been covered thousands of times but what is wrong with reflective damage? They guy that makes the mistake gets punished by it, instead of the unlucky bystander. No more getting killed because your teammate hits you and interrupts your block just before the enemy's flamberge will cleave your head.

Its ugly.
and:

No reflective damage. It is horrible.

these arguments sounds good, eh?
iIt is difficult to determine, but reflective just makes the whole game feel clunky and terrible. And it has been discussed many times and luckily the crpg-team seems not to like it as well.