Judgement going grey when another player is using it

[DrRocket]

2 hours ago, Greycat said:

 

Here's the thing. You've just prevented people from using Judgement on (a) a large pull or (b) an ambush. And if there's no max range, (c) people on opposite sides of the map. For judgement? Absolutely not. 

 

There *are* powers, though, that I'd like to see something similar on. Single target rezzes, specifically. I've seen multiple people waste a rez on someone who went AFK or lost connection - and those tend to have a long cooldown. What I'd *like* to see is the first rez "stick" to that player - similar to when you have multiple people offering someone a team, they get the "Player is considering another offer," if one isn't accepted, further rezzes are blocked for some time (and the dead player gets a window on their screen they have to respond to.) 

 

 

The point I am trying to make is the game is allowing others to shoot duds because they activated their judgment just after another player did, and thus I am searching for a way for the players not to fire a dud and be able to keep their judgment available for another time. 

 

I do see your point with your comment about preventing another player in a different area of the map, perhaps the greyed button would have a radius based on the player who used the judgement.

 

But what I seek are workable solutions to prevent the phenomena of your judgement activating to only be a dud, because you activated yours fractions of a moment after.

 

If the grey out proposal as it overwhelmingly seems to be a no go, then I ask propose solutions, thank you

 

Regards

[Rudra]

30 minutes ago, DrRocket said:

The point I am trying to make is the game is allowing others to shoot duds because they activated their judgment just after another player did, and thus I am searching for a way for the players not to fire a dud and be able to keep their judgment available for another time. 

 

I do see your point with your comment about preventing another player in a different area of the map, perhaps the greyed button would have a radius based on the player who used the judgement.

 

But what I seek are workable solutions to prevent the phenomena of your judgement activating to only be a dud, because you activated yours fractions of a moment after.

 

If the grey out proposal as it overwhelmingly seems to be a no go, then I ask propose solutions, thank you

 

Regards

Which happens with absolutely every attack in the game including nukes. And also happens with heals. And rezzes. And you have already been told this repeatedly. Welcome to being on a team. Where the chaos that is combat means that not all of your abilities will get to be used to maximum effect or even at all at times.

[lemming]

Actually, there's a little bit of that with some of the adaptive recharge being applied to some powers.   Hit a bunch of targets, longer recharge. Hit none, very quick.  Maybe if we get that applied to judgements, etc... more so.  (though as pointed out, hell on some procs)

[Greycat]

3 hours ago, DrRocket said:

If the grey out proposal as it overwhelmingly seems to be a no go, then I ask propose solutions, thank you

 

 

Solution: Tell people you're going to use the power. 

Implementation time: 0 months 0 days 0 hours 0 minutes 0 seconds. 

 

Why should Judgement get this special treatment? Why not blaster nukes, which have had this issue since... issue 0? Or - well, pretty much every power that affects a target in the game? Should I not be able to throw a heal on someone because their health has just hit 100% from someone else's? Should I not be able to hit a target because the blaster's snipe is still winding up and would take that target to 0? Should I not be able to use the big nuke I'm in the middle of a spawn to set off because someone started clicking Judgement half a second ago, or vice versa? (And on the programmatic side, how many of these checks on how many targets do you want the server - because this *can't* be done client side - to do for every player in every mission continuously?)