Valorant is a free-to-play first-person tactical hero shooter game developed and published by Riot Games in 2020. The game is supported by the dev with constant updates and received a new one a while ago. The patch notes of the Valorant 6.08 PBE update are below.
Valorant Update 6.08 PBE Patch Notes
AGENT UPDATES
Gekko
- Wingman
- Audio improvements to Wingman’s (Q) plant and defuse audio.
- The audio cues for Wingman’s spike and defuse sound were unclear during hectic combat situations. This should help make those audio cues standout.
- Audio improvements to Wingman’s (Q) plant and defuse audio.
- We’ve updated Gekko’s in-game portrait for better gameplay readability and quality consistency.
Killjoy
- Nanoswarm (C)
- Nanoswarm reveal radius increased 350 >> 525
- Nanoswarm audio has been updated.
- Audio loop now also turns off when disabled as a result of Killjoy being killed or suppressed.
- Improved feedback for the enemy when they destroy Nanoswarm.
- Nanoswarm is now revealed when it is disabled.
- Other Abilities
- Updated visuals for Killjoy’s ultimate Lockdown (X) being destroyed.
- Removed the yellow warning UI Indicator for enemies Killjoy’s Lockdown (X).
- Updated deactivate sounds for Killjoy’s Turret (E) and Alarmbot (Q) to make them more distinct.
Misc.
- Brimstone’s Sky Smoke (E), Orbital Strike (X), and Omen’s From the Shadows (X) ability have updated targeting visuals to help players with precision placement on the map.
MAP UPDATES
- The newly updated Bind rotates into Competitive and Unrated queues.
- Icebox rotates out of Competitive and Unrated queues.
KNOWN ISSUES
- We are aware of an issue modifying locale within the client. Locale updates will need to be performed through Riot Client (Riot Client settings).
- We’re aware of an issue where, in rare instances, audio cues are not playing for various sound effects. We are investigating at this time and will share as soon as we know more.
Prerequisites to be noted before reporting a bug
- A bug will ideally be accompanied with a screenshot or a video. This provides credibility to your report.
- Steps to recreate the bugs should be submitted if possible. This helps Rioters recreate the bug and helps them find the cause behind it.
Format when reporting a bug: When reporting a bug, please provide as much information as you can about your computer.
• Type of Bug: Client Bug, In Game Bug, etc.
• Description: Describe what was the bug that occurred.
• Video / Screenshot: Insert screenshot (F12 in game) or Video of the bug occurring.
• Steps to reproduce: Provide the steps necessary if someone else had to reproduce the bug.
• Expected result: What should have been the result when you follow the steps mentioned above.
• Observed result: What was the result you obtained when you followed the steps mentioned above?
• Reproduction rate: If you try to recreate the bug how successful are you in causing it to occur? (1/10 : Occurs once every 10 tries, 5/10 : Occurs 5 times out of 10, 10/10 : Happens every single time)
• System specs: Processor, Video card, Ram, HDD/SSD, everything you can provide, even drivers.
Example Bug:
• Type of Bug: Matchmaking
• Description: Matchmaking doesn’t work properly
• Insert Video / Screenshot of the incident
• Reproduction rate: 10/10 (happened 10 out of 10 times)
• Steps to reproduce: Try to launch a game
• Expected result: Match starting
• Observed result: Getting stuck in infinite queue
• System Specs: Intel i5 Processor, Windows 7, Nvidia Graphics card (insert model number) etc.
