The design we ended up with is fairly straightforward:

• We set two constants in our data: WP/minute ceiling and WP/minute limit
• Each player has a WP ceiling and a WP limit for each match
• These start at 0, and are incremented every second. This gives you two numbers that rise linearly over the course of the match
• If, any time you gain WP, your total WP score for the match would be above your current WP ceiling, we reduce the value of that WP payout proportional to how far between your current ceiling and your current limit it would take your score

This has the following consequences:

• So long as your WP total stays below the WP ceiling, you will never see this system
• As your WP total moves above the ceiling, we trim your WP payout in a way that starts gentle but gets firmer as your WP/minute gets higher
• We can mathematically guarantee that you can never score more WP per minute than the limit value over the course of the match, so this system should be 100% exploit-proof and never need to be adjusted again
• Because we are tracking a moving ceiling over the course of the battle, rather than say tracking your income over the last minute or the last X WP scores or whatever, once you get past the first few minutes in-match your WP income can be very uneven and still not trigger the cap so long as your average over the course of the battle stays below the limit
• As a side-effect of the above, the system is more likely to start clipping scores if you score large amounts of WP in the first minute or two; this isn't optimal, but in the course of a normal battle (ie starting from the beginning rather than joining midway through) there's little opportunity to get big scores in your first minute or so, which should significantly reduce the impact of this factor.

Sorry yeah, I should've said, that 2k WP was scored in six minutes If you're scoring 2k WP over 10 or 15 minutes you're unlikely to run into the cap unless you score a large number very early on. 2k evenly spread over 10 minutes is only 200 WP/minute, which isn't a problem even with current cap numbers.

If your 4000 point game is taking longer than nine minutes, and you're not scoring more than 1000 points in the first two minutes or so of the battle, you'll not be affected by this feature once we get the new numbers onto TQ.

Equipment WPs are naturally limited, you don't need an additional throttle (over the new general one anyway).

Deployment earns zero WPs. Usage is what rewards the Logi, and usage is limited by need.

You can't spawn more clones on uplinks than you start with in match. It matters not if you have one or thirteen active, the limit is clone death.

Likewise nano-hives don't sit and generate WPs on their own. A team member has to be receiving ammo for the Logi to be rewarded. There's a slightly more elastic limit on this, but it's capped by need.

If a match has a single Logi working his butt off deploying equipment where it will be used he can top the leader board and he deserves to. He just spent a large portion of he match making sure the slayers will have a good time, not spending a lot of time running to the front and back to a SD. He keeps the action intense and the match fun for everyone, and this is often at high ISK expense as proto equipment is quite expensive and the Logi is often on the front line making deployments that count.

Multiple Logis can deploy more equipment, but they can't increase the need for it so they compete for the existing pool. In that case two Logis might do well, but each place below the player with the most kills.

Think about it this way, if a match had a dozen support players and one slayer that sayer would clean up every match because he isn't sharing the available kills. Ridiculous? Well why is there a single Logi on your team? Is that play style so little fun for the majority of players that they avoid it? Why aren't you?

Rather than nerf the rewards, maybe the job needs to be made more attractive so the task of supporting the entire team isn't borne by a single player.