0

Bug usage on First Strike Qualifier

Comments:
Threaded Linear
#1
duriica

Exploit used by thunderPEEK against Winfinity (First Strike: Europe, Qualifier D: Round of 128)

Location of the arrows on the map radar: https://imgur.com/a/Z3QZYR5

Sova shot reveal arrow out of bounds of map in the way it cannot be destroyed, but it still can reveal players. It was used by Defender team, to see where Attacker team is preparing to push.

I have clips from round 1 and 3. (It happened more than 5 times during the match).

https://streamable.com/ywye4x
https://streamable.com/e7b81h

Match ended with the close result of 11-13 (thunderPEEK won).

------

As it is stated in the VALORANT Global Competition Policy on page 14:

7.2.6. Exploiting.

Intentionally using any in-game bug to seek an advantage is exploiting and is prohibited.

Exploiting includes acts such as making use of any game function that, in the Tournament Operator’s sole judgement, is not functioning as intended and violates the design purpose of VALORANT. Team members may confidentially check with the referee at the beginning of a Competition to determine if a specific act would be considered Exploiting. Riot reserves the right to make an ex-post-facto determination of whether an exploit has occurred.

------

This exploit was reported to the admins of First Strike right after the match ended.

In the previous tournaments all over Europe there were another teams that got disqualified using this bug.

Same rule (7.2.6. Exploiting) was broken in the match between Guild Esports vs. G2 match, and Guild Esports have been issued forfeit. Guild Esports used exploit, which gave them advantage, so they get punished. But in the same stage of tournament (Qualifier stage) in our match, there was nothing done from the side of the First Strike tournament admins.

Why did Guild Esports get punished and thunderPEEK not?

A precedent was set in the previous case (Guild vs. G2), why isn’t this take to matter when deciding in this subsequent case with same issue (7.2.6. Exploiting).

------

I hope that this bug will be fixed soon, so players can focus on their gameplay and not waste time clipping these bugs and reporting it to the game admins.

What do you think?
Is this unfair?
Should it be fixed sooner as this is well-known bug?

#2
ideekae
0
Frags
+

I shoot arrows outside the map all the time. Except they don’t reveal anyone.

But honestly the exploits in both instances have been unaddressed for so long that it seems that there should be some forgiveness for the teams. Too bad the ppl at riot act like they gotta protect G2.

#3
Ricci
0
Frags
+

I see no problems here, to be honest, and don't think it's any sort of bug or exploit. Using environment objects out of bounce for Sova's arrows should be fine in my opinion.

It's very common to shoot arrows in the trees on Ascent B, for example, and they are also out of bounce.

#4
duriica
0
Frags
+

Even if you cannot destroy the arrow, but it's still revealing your position?

I think this should be patched.

#5
Ricci
0
Frags
+

Well, if that's the case then yes, it should be fixed. The clips you shared don't really show anyone being revealed or where the arrow could be, so it was unclear to me.

#6
Chronicle
1
Frags
+

that arrow can be destroyed

#7
duriica
0
Frags
+

There is a problem with invisible texture.

You can destroy the arrow only from one position.

Any other position is blocked by invisible texture, so the arrow can reveal the players, but players cannot destroy the arrow.

Simple as that.

  • Preview
  • Edit
› check that that your post follows the forum rules and guidelines or get formatting help
This thread has been locked.