|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Driftward
Subdreddit Test Alliance Please Ignore
54
|
Posted - 2013.05.13 17:48:00 -
[1] - Quote
Every other equipment item has methods of earning direct WP (nanohives-triage, resupply; injectors-revives; reppers-triage, guardian; remote explosives-kills, uplinks-team spawn) however, with active scanners you have to be able to scan then hope you can find and kill those enemies you ping in the 2ish seconds that they are active on your minimap and still only gain kill war points. (seperate bug about scan duration there)
If you play as an EWAR support position you should be able to earn WP in proportion to your contribution. My idea is to get a bonus of 5-10 WP per kill of a enemy that you highlighted either within the window of target visibility or within 5 seconds after visibility ends. As with triage/guardian points there should be a cooldown of points after say 50 wp gained to maintain parity.
One final argument, for your team, support by EWAR (specifically active scanner) can make or break an enemy encounter. This usefullness should be reflected in your WP as your contribution towards the team as a whole and not just through your team standings. |
Driftward
Subdreddit Test Alliance Please Ignore
63
|
Posted - 2013.05.13 19:49:00 -
[2] - Quote
Turkevich wrote:I think the same argument could be made for snipers who spot targets which is a similar job to using an active scanner. It would be a great idea to see some war points for these activities.
As much as I agree with the idea that snipers should get wp for spotting, the mechanic to build that in is probably much more difficult to implement than in comparison to active scanner....regardless I'm glad that some other people support the idea. Hopefully the Devs will take notice. |
Driftward
Subdreddit Test Alliance Please Ignore
72
|
Posted - 2013.05.14 16:44:00 -
[3] - Quote
Wombat in combat wrote:Driftward wrote:My idea is to get a bonus of 5-10 WP per kill of a enemy that you highlighted either within the window of target visibility or within 5 seconds after visibility ends.
As with triage/guardian points there should be a cooldown of points after say 50 wp gained to maintain parity. There is a problem with awarding WP per kill of scanned enemies. Imagine an ambush game where the majority of both teams are duking it out at a relatively open area, then you could just stand back behind your team mates scanning in front of you, making potentially allot of points but not necessarily making a good contribution because your team already knows the enemy is in front of them. I'd suggest awarding X amount of WP for target you revealed to the TacNet radar that have not been visible to it for Y amount of time. There is however a problem with that, for example if you scan in a direction and get nothing, still a valuable intell but no rewards. I don't agree with you on the triage/guardian WP thing. It's fine as is, if anything I'd like to see less cooldown
I think you misunderstood my comment about triage/guardian points. Those were merely meant as an example of the game mechanic not a request to lower their cooldown threshold. I personnally like the triage guardian exactly where they are.
I mentioned 50 wp as a potential threshold for the active scanner only. I actually think (after some more reflection) that a 100 wp threshold would be plausible with either a 30 sec to 1 min cooldown period. |
Driftward
Subdreddit Test Alliance Please Ignore
85
|
Posted - 2013.05.15 21:49:00 -
[4] - Quote
Cruxio wrote:It should break down and operate like this
+5 for each redberry picked up (revealing locations should be important, this allow allows the team to avoid enemies too)
+5 for each redberry killed after a scan (someone made use of it)
Then some timer restrictions on points applies to this mechanic, similar to how armor repair tool has on it.
This would make the Active Scanner on par with other equipment.
I see three options 1. Have as Cruxio suggested.
As much as I would love this, it would break the mechanic. I routinely scan and hit about 6-10 redberries, especially in the start of a match. 5*6 (being conservative) = 30 points per scan * 4 (say 4 scans per minute 1 every 15 sec ish, with a long duration scanner, much faster for other variants) = 120 wp/minute * ~10 min/ game (ambush is around here +/- 3 min) = 1200 WP from scanning alone with no killed reds.
If a cooldown mechanic was added that limited scanning wp (with kills after scan limited too) to perhaps 100-150 wp on a rolling 2-3 minute basis, that might work. Thus total wp by active scanning is limited to ~600 in a 10 minute ambush and 1200 in 20 minute game play.
I take it back, doesn't necessarily break it . Math makes the world go round. However, maybe tweak the numbers to +2 or 3 for scan only and +10 for kills after scan. Regardless, there will be ***hats who exploit this beyond all reason, but at least they'll be lighting up the reds at the same time. Can't make everyone play nice.
2. Limit wp to kills after scanning.
In this situation keep the same cooldown period and max, but increase the reward to perhaps +25 as in a kill assist. This makes it more liable to abuse in the ambush small map situation where you sit just outside the action and highlight unnecessary targets (as in redberries already obvious).
3. Do as Wombat in Combat suggested [quote=Wombat in Combat/]I'd suggest awarding X amount of WP for target you revealed to the TacNet radar that have not been visible to it for Y amount of time. There is however a problem with that, for example if you scan in a direction and get nothing, still a valuable intell but no rewards.[quote/]
While I agree it makes the mechanic less abuse friendly, might be difficult/more work for the devs. Still recommend a cooldown for this too. Finally, I don't think that wp for just scanning is viable sadly, just too much abuse potential there. |
Driftward
Subdreddit Test Alliance Please Ignore
87
|
Posted - 2013.05.16 18:11:00 -
[5] - Quote
ladwar wrote: so shhh and wait like the rest of us.
Well, normally yes. But as they have yet to specify what the mechanic is we may as well throw out our ideas and provide some good feedback rather than have to ***** about it being crappy after they implement the system. |
|
|
|