ValorLeaks asked players on X what they think about the new Abyss update, and the replies ranged from praise to frustration. Below is a concise recap of the changes and what the community is saying. For the full list of adjustments referenced here, see Riot’s official patch notes: Valorant patch notes 11.08
What changed on Abyss
Riot adjusted B site with added and moved cover to encourage on-site fights and make planting for B Main riskier. Mid was reworked to improve flow and give both teams more pathing options for takes and retakes. The goal is closer, more readable engagements and better defensive viability.
Community reaction
Sentiment in the thread leans cautiously positive, with recurring themes around B post-plant and A site.
Improved but still imperfect
@tpWeavile: “They gave Abyss the Lotus treatment… much improved. Now they just need to fix A site and Abyss will be a good map.”
Too easy for post-plant
@skytookie: “I feel like post plant is even easier now,” reflecting a common concern that attackers still have strong post-plant setups on B.
Mid changes divide players
@ExpiryYT: “I don’t think mid needed the changes, other stuff is nice though.”
@ValorantMarlin: “It gave Viper a buff for pushing up mid so I can’t complain.”
Nostalgic complaints
@NWNMHOODRICH: “I miss the old Abyss — this new one so ass.”
@Kevl4rrr: “No matter what they do to that map, it will always be crap.”
Tactical praise
@tarooofps: “Anchoring and retaking is easier… mid changes made it more CT-sided but still manageable for attackers.”
@SplitzHere: “The map is actually good. I enjoy playing in B because of the new layout.”
Summary
Players broadly agree Abyss flows better and feels more balanced, especially around mid and defender holds, but many still want further work on A site and safeguards against overly strong B post-plants. If Riot keeps iterating with this feedback, Abyss could finally shed its polarizing reputation.
Sources
- Original discussion thread: @ValorLeaks on X
- Patch details referenced: Valorant patch notes 11.08
- X.com community comments credited inline: @tpWeavile, @skytookie, @ExpiryYT, @ValorantMarlin, @NWNMHOODRICH, @Kevl4rrr, @tarooofps, @SplitzHere
