Getting points for destroying shields.

[Templar_Steevee]

Last days I noticed that there are plenty shielders around. Lot of times they are dying after you destroy their shield.

It would be nice to get some points for destroying shields (like 1/2 or 1/3 of points for hitting enemies).
It will show that you are actually usefull for your team and at least reward a bit ppl who fight against shielders whole round, destroying their shields, but not making a single hit on enemy, because you died to them or just your teammates came at the end just to stole your kill.

What do you think about it?

[Torost]

They just run and pick up a new one from the ground.

With the mindset of crpg players, we would be seeing leechers and valorfarmers crushing eachothers shields let and right.
Bringing 3 0slotshields to ensure valor every round.

i agree that smashing shields is helping your team, but creates a new way for silly people to game the system.

[Templar_Steevee]

They just run and pick up a new one from the ground.

With the mindset of crpg players, we would be seeing leechers and valorfarmers crushing eachothers shields let and right.
Bringing 3 0slotshields to ensure valor every round.

i agree that smashing shields is helping your team, but creates a new way for silly people to game the system.

that's why i suggest to lower amount of points you get for hitting shield - devs will just need to adjust it.

bringing with you 3 shields won't give you valor, because enemy is getting points for killing your shield.

Also tactic "run and find a new shield" is common atm.

[Soulreaver]

give points for every successful manual block of a shielder

[Shadowren]

give points for every successful manual block of a shielder

Easy points for me

[MURDERTRON]

The problem is some clown is going to run to the corner of the map with 3 shields to meet his buddy who also has 3 shields and they're both going to get valor for not really fighting.

[Kafein]

1 point per hit seems reasonable, maybe even that is too much.

[Gurnisson]

I see no point in adding this. Why would you reward damaging a shield? Should we give points for swinging into blocks next time as well?

[Templar_Steevee]

did i menion about negative points for hitting teammates shield? 

I see no point in adding this. Why would you reward damaging a shield? Should we give points for swinging into blocks next time as well?

Shield is something like a horse, it's helping a lot in battle.

We are geting points for killing horses, so destroying shields should also be rewarded. With shield you can survive gang, without it it's way harder, close to impossible.

ATM we have pointing system rewarding killing players, a bit less for killing horses and seeing a way less points gained for smashing shields would be nice.

[San]

A 0.1 multiplier may accumulate to a few extra points over the course of a round. It might be a pain to add since I am not sure whether or not you can link the on-hit trigger to a shield.

[Huscarlton_Banks]

Code: [Select]

WSE\WSESDK\header_triggers_addon.py

ti_on_shield_hit = -103.0 #can only be used in module_items triggers
# Trigger Param 1: receiver agent no
# Trigger Param 2: dealer agent no
# Trigger Param 3: inflicted damage
# Trigger Param 4: raw damage (before shield skill and skill resistance bonuses)
# Trigger Param 5: item kind no
# Trigger Param 6: item modifier
# Trigger Param 7: missile item kind no
# Trigger Param 8: missile item modifier
# Trigger Result: if set, damage dealt to shield

[Templar_Steevee]

Code: [Select]

WSE\WSESDK\header_triggers_addon.py

ti_on_shield_hit = -103.0 #can only be used in module_items triggers
# Trigger Param 1: receiver agent no
# Trigger Param 2: dealer agent no
# Trigger Param 3: inflicted damage
# Trigger Param 4: raw damage (before shield skill and skill resistance bonuses)
# Trigger Param 5: item kind no
# Trigger Param 6: item modifier
# Trigger Param 7: missile item kind no
# Trigger Param 8: missile item modifier
# Trigger Result: if set, damage dealt to shield

I'm not sure, but it looks like it shouldn't be a problem while having code above...