It really sucks that you have that timer on your repairs as the repairing person doesn-¦t get the WP and it-¦s often even worse for your team mates as they sometimes aren-¦t repaired anymore. This often can turn the tide in a battle.
It worked well earlier in BETA but got abused because there were no limitations and now there are the wrong limitations.

If the game would remember who has done how much damage to whom it would kinda fix this. WP would only be awarded if the damage was dealt by hostiles and not by falling, your own explosives or blueberries (in PC). The client would simply remember which person did how much damage to you and it would give out WP depending on this. Repairing through built in repairers would have nor influence o the distribution but only on the total WP given out.
If you reach full armor again all stats are deleted again to save RAM.

Example 1:
Merc A has taken 100 HP armor damage from enemies. So if Merc B repairs him he gets full WP.

Example 2:
Merc A has taken 100 HP armor damage from friendly sources. If Merc B repairs him he gets no or just very little WP.

Example 3:
Merc A has taken 50 HP armor damage from friendly sources and 50 HP from enemies. If Merc B repairs him he gets 50% of the WP he would normally get.

Example 4:
Merc A has taken 50 HP armor damage from friendly sources and 50 HP from enemies and with his built in repairer he already has repaired 20 HP. So he actually has only 40 HP from friendly sources and 40 HP from enemies taken. If Merc B repairs him he still gets 50% of the WP but he repairs less HP and thus gets less WP total.

So the repairing person gets WP depending on how much of the repaired damage is dealt by hostiles. It could either be split into various sections like 0-10% damage = 10% WP etc. or be directly translated.

If this is implemented it can also be used in other areas. So in the kill screen there could be shown more than the guy who finished you off and Kill Assist WP could be distributed depending on the damage done then.

I-¦m not good at programming so I-¦m not absolutely sure if this is technically feasible but I haven-¦t found a reason against it either.

Bump

I was convinced that this is how the system works, except rewarded WP with are always set for A WP per B repaired enemy demage.

I made a suggestion about ways to reset the timer for when you get a kill, kill assist, guardian bonus, or revive, to prove that you are in combat and should be earning points.

The problem with your idea is that it's too complicated, and not easy for the DEVs to code into the game.

Sure, this is the way we all would like the system to work, but you have to think realistically.

I made a suggestion about ways to reset the timer for when you get a kill, kill assist, guardian bonus, or revive, to prove that you are in combat and should be earning points.

The problem with your idea is that it's too complicated, and not easy for the DEVs to code into the game.

Sure, this is the way we all would like the system to work, but you have to think realistically.

You mean this thread?

@OP, Code load effects performance which effects the game as a whole. The tech side is important and often the best suggestions are those which require the most minimal mechanical changes. Granted we as players cannot always know what those are but gearing suggestions to fit that is often key.

0.02 ISK
Cross

It would only need a bit more prozessing power since the game already saves information for Kill Assists and code loading would only minimally effect performance as it would only be one code more.
It is just a minor change and problably needs less processing power than the current system.

Still don't see why anyone would care if WP caps like that. Logis already have the best chances for WP out of any other class.