wetdry.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
We are a community focused on gaming, tech, entertainment, and more.

Administered by:

Server stats:

724
active users

YOU CAN NO LONGER DOWNLOAD MACOS COUNTER-STRIKE 2
I REPEAT
YOU CAN NO LONGER DOWNLOAD MACOS COUNTER-STRIKE 2

i found this out a few days after deleting my raw depot downloads i took a few months ago god fucking damn it man i hate valve

sweeping platform changes that are antithetical to game preservation is bad actually. one of the pros of Steam for me for so long was that you *could* download older versions of games, even if it was roundabout. an objectively pro-consumer thing (modders?!? hello?!)

so why did they get rid of it..?

UPDATE: Allegedly a "bug" that just so happens to have complex server-side logic wetdry.world/@ipg/113913249551

and it isn't Just Valve's games/apps

tried on a friend's game (who had no choice) and that didn't work

tried on Beat Saber, a game where downgrading versions is *key* to getting mods working if you update, didn't work

tried on GTA 4, a game where downgrading is almost required for most mods, nada

it's hard to really grasp the sheer amount of destruction Valve has done to game preservation and game modding with a single change to their platform

speedrunning is a huge impacted category here! you can't legally get older, faster versions of so many games now

and for what, Valve? what is the reason? because a big publisher got pissy at you and you ruined it for everyone? or because people were datamining for a VR headset you'll never release?

oh and another thing,

the sheer amount of people *still* giving Valve a slither of benefit of the doubt here. "a backbone server issue" wouldn't be causing a 403 access denied. "it was a mistake" you can't really code in logic to do this by mistake. "oh it might be tuesday maintainance" IT'S A WEDNESDAY

Valve employees have *claimed* on Reddit that this was a bug and a fix is rolling out - good! - however personally I do not believe that story because this *has* happened before and the backend logic behind the error is always the same. it feels like a semi-regular scream test rather than a bug

Source: np.reddit.com/r/Steam/comments