A fix to accidentally placing a ward immediately after a teammate in the same location

Shìv··13 votes·7,186 views

Have you ever been walking alongside a teammate and both of you placed a ward in the same bush, at the same time, and right next to each other? If so, and you want to consider solutions, read on.

I think this would be an easy fix if after a ward is placed, it has an exclusion radius wherein you or a teammate cannot place another ward for a short time. Say, a radius of 2 Teemos and it only applies for 1 second. This could be done with or without visuals being added for ward placement (e.g., a small ring around a new ward that lasts for 1s).

This way, in the scenario above, whoever lays the ward first still places their ward but in the fraction of a second afterward where the second player tries to place a second ward in that same location, their action is simply canceled.

Although this would require some programming, it may be worth the man hours for a significant (I think) QOL improvement. Actually this is more than a QOL improvement because wasted wards can be a significant setback. In fact, I've done this with a teammate where we both placed control wards at the same location. RIP 75g.

Hopefully that was clear; thanks for reading.

18 Comments

vyoda6 votes

As a Support main, I really like this QOL change [sg-ahri-2] have an upvote!

Autrah Fang4 votes

{quoted}

Although this would require some programming

Some programming... with no immediate financial payoff when it's finished??

Riot has left the chat

Shìv1 votes

Haha, yeah I was tempted to add "(so it will never happen)" somewhere in that sentence but refrained.

Sister meow4 votes

What about those rare occasions where you really want to double ward to ensure one of the wards survive in case they insta-target the first one? [sg-janna]

Shìv1 votes

Good point! I don't have an answer for that.

Disulfiram1 votes

Good point on paper, but personally I've never ever seen this used... maybe some pro teams could have the kind of coordination required to pull this off, but I've yet to see this used in game.

(I'm assuming that this "ward prevention" idea would apply only to teammates, and that you double-warding an area by yourself would still be possible the way it is now)

Starcraft243ver3 votes

Problem would be with champions that can ward jump, if they want to reach a precise location, you, as an ally, could deny this from by placing a ward at the wrong time.

Shìv2 votes

This is a pretty insightful critique of this solution. I'm unsure how often this solution would impact this scenario but you're right that it is possible. Maybe they could just disable this "double ward protection" for these champs (e.g., LeeSin )? But that requires more programming!

Critmaster Garen3 votes

only problem i see is, if your whole team wants to throw multiple wards into the baron pit at the same time, to make it difficult for the enemy to remove them all before you can attempt a steal.

we all have probably been there at some point. the enemy team is doing baron, and its in the vicinity of smite range, so 3 people on your team throw 3 to 4 wards over the pit.

the enemy team now has to decide if they want to stop and take extra 5 to 10 seconds to take all the wards out, or if they want to risk bursting it while you have vision on it. in both cases it gives your team a window to make a play.

Shìv1 votes

In my mind, the exclusion radius is small, like the river bush in between mid and dragon pit. This could obviously be tuned to be smaller or larger. If it were small enough, multiple people could still ward dragon pit. Good thought though!

koshkyra2 votes

I do agree that there should be some kind of prevention to the double warding, but this could have unintended effects.

For example, a ward is about to expire (lets say 5 seconds) and the area of the ward will not be safe for you to be in 5 seconds later when it expires. Currently you can place a ward in its spot (sacrifcing 5 seconds of ward lifetime for safety) but with that change you wont.

Shìv9 votes

I understand what you're saying but this "double ward protection" would only be active for a second or so after the ward has been placed. So you can still place a ward next to another one that's about to expire since the "double ward protection" timer has long since expired.

Ahri Body Pillow1 votes

{quoted}

I understand what you're saying but this "double ward protection" would only be active for a second or so after the ward has been placed. So you can still place a ward next to another one that's about to expire since the "double ward protection" timer has long since expired.

Those seconds matter in Baron steal situations

Sky Cardis1 votes

Or communicate better? Or judge the situation. Not disagreeing with you IT BE USEFUL TO HAVE. Me and ADCs do this time to time, but I learned better about it over time, if I see ADC head to bush I follow but don't place ward right away just in case, if they keep moving w/o warding I then place a ward.

But hey lets admit, ADC and Supports have a laugh about it EVERY time it happens...I never seen outright rage/blaming/tilting about it.

Shìv1 votes

Yeah I often ping "on my way" and then ping that my ward is off cooldown. There are workarounds to be sure.

season10balanced1 votes

This happens to me and my premade all the time item 3070

MaskedMadness1 votes

how about no. these are the kind of things that make the game to easy. you are supposed to be communicating your actions not going with the flow. Riot is forgetting that the game is supposed to be skill and commucatively inclined. with abilities like Qiyanas E allowing her to press Q anywhere and it auto targets whoever she pressed E on is an ease of life bs.

More from Gameplay