Dust 2 B skybox opened, other huge map changes in CSGO update

By Nick Johnson

|

Jan 30, 2020

Reading time: 3 min

Tactics just got a whole lot more important on Dust 2. With changes to the skybox between B site and upper tunnels, there are now more executes on B than just the mid-split on the famously popular map. Mirage and Train also saw huge changes that could alter their balance significantly.

Today’s CSGO patch brought a groundbreaking change for Counter-Strike: Global Offensive’s most famous map. Developers have opened the skybox between T Spawn and B site, finally allowing executes on one of Counter-Strike’s most difficult bombsites to attack.

Train received a similar update. Now, grenades can be thrown from Ivy over onto the A site, giving players more opportunities to pressure Ivy during an execute. A full A execute no longer require three players outside T main, meaning a wrap through CT is now a seriously powerful option on T side.

Shaun “FMPONE” Snelling continued his work on Cache, with improvements to visibility across the map and an updated radar. To the relief of many, Cache’s changes come with optimizations that should help the map run better on all systems.

Studio saw the smallest changes, with a bug fix to bomb damage, clipping improvements and some visual tweaks for each side’s respective streets on their side of the map. Studio did recently receive an overhaul in Counter-Strike’s last patch, so it’s not surprising that it has fewer changes this week.

CSGO January 29 patch adds tactical options to Dust2, Mirage

On Mirage, one change could switch up strategies for everyone. Players can now boost into sniper’s nest from bottom mid on their own, eliminating the need for a second player’s assistance. A mid lurk underpass is now very powerful for an A execute.

It’s also fast. A heavy mid take can allow the entire team to take control of snipers in seconds.

A bench at the bottom of the connector allows a nifty jump into what used to be a CT paradise, making a B site player control catwalk even more important.

Those cat players will have to be careful. When standing on the bench, players now have a headshot angle on anyone holding from bricks. The same is true for the cat player though, so the new position adds another tactical dimension to the map.

Dust 2’s changes are the ones we never thought would come. The map has always rewarded teams that can aim better than they can strategize. Now, the meta is about to change. From inside upper tunnels, smokes and flashes can be thrown by Ts onto the B Site. For example, this quick smoke isn’t perfect, but it covers the cross and allows a plant.

Flashes are also insanely powerful now that they can be thrown from inside tunnels to catch out a CT playing close car.

Valve’s changes today opened up stale maps to new strategies ahead of BLAST Premier. We don’t know yet if BLAST will use the new patch, but fans can be sure that both Mirage and Dust 2 just got a whole lot more interesting.

CSGO January 29th update full patch notes

Here are the patch notes in full.

[ MAPS ]
Cache:
Various visibility improvements
Optimizations
Various minor bug fixes
Updated radar

Studio:
Fixed players not taking damage from bomb detonation
Clipping improvements
Improved visuals of CT / T streets
Various minor bug fixes

Train:
Opened up skybox over building separating Ivy/A site
Various visibility improvements
Various minor bug fixes

Dust2:
Opened up skybox from B halls towards site

Mirage:
Added AWP wallbang spot from palace to scaffolding close corner, A site
Added bench in mid allowing jump up to window boost spot/peek towards cat
Widened T entrance to mid
Lowered trim around B site balcony
Blocked a jump-peek from middle of B site towards cat

[ MISC ]
Increased the size of HLTV broadcast server info message, controlled by a new setting “tv_broadcast_server_info_message_size_kb”.
Added a setting spec_xray_dropped_defusers to show xray outlines on dropped defuse kits.
Added a setting spec_xray_dropped_unoccluded to always xray dropped C4 and defuse kits.
Game state integration now allows to control precision of reported floating point values using an additional configuration section:

“output”
{
“precision_time” “1”
“precision_position” “2”
“precision_vector” “2”
}