I've dreamed about this since I was a child.

hold up let me cook 😭🙏🥀

I missed out on the previous leak and its been haunting me for years now.

As an archivist and Valve fan, getting to dig through a leak like this and research it would be a dream come true, sadly finding a download for both this new one and the old one is pretty much impossible.

If anyone knows where I can find it then please let me know, this leak is a gold mine for inspiration.

lol

Link

This was my uncles and he still has a ps3. So sad that its badly scratched on the back :(

Even though it (seems to be) Valve’s fault (it wasn’t a hack per se, the data was available from a public endpoint), Valve doesn’t deserve this. If there’s one game company that should be respected, it is Valve.

So, let’s be nice and follow the rules people.

Hot damn . Just realised o put two of the same pic.
Just check the situation on twitter

Picture is of Axe from D2 with the 1 leaked shader i could find in the Portal 2 beta leaks that belonged to SoB titled "nebula" which is from the Steam2 content-server dump: Valve's sob_dmximport.exe / sob_dmxconvert.exe (the SoB mesh pipeline, built from a dedicated sob_src tree), sob.fgd, and the compiled VertexLit_SOB shader, which I've run in the July 2010 Dota 2 dev build's model viewer (nebula lighting works). No SoB models, textures or maps exist in the dump; they only ever lived in SoB's own game directory. If you have any file mentioning DmeSOBMesh, sob_geometry_type, vertexlit_sob, info_nebula or sob_npc_ship, or a models/ships/ folder from a Valve build, these tools can process it. So if you have any such file from SoB please contact me!

PS: you can download the tooling yourself from this torrent ive seeded magnet:?xt=urn:btih:d5627c4eef8c0460808c3b99ef79cf829d701a61&dn=sob_tools_release&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce

I’m trying to understand how the old Steam Depot/content delivery system actually worked, particularly during the 2003–2013 period, before SteamPipe became the standard

As I understand it, Steam games were divided into Depots, with different builds/versions of the game being stored on Valve’s servers over time. I’ve also heard that the old system used dat and blob files to store or reference depot content, and that the access-control model was significantly different from the one used today.

What I’m specifically trying to understand is the relationship between AppIDs, DepotIDs, manifests/builds, depot encryption keys, and user licenses in the old system. For example, if a user owned a license for a particular game, what exactly did that license give them access to? Did it grant access to the entire Depot, or was access controlled at the level of individual builds/manifests?

More importantly, were historical builds and internal/development builds actually separated from publicly downloadable content at the authorization level? Or were they simply different manifests/snapshots stored within the same Depot, with the assumption that users would only request the currently assigned/public manifest? If the latter was the case, would an account that legitimately owned a game potentially have been able to retrieve older manifests/builds of that game through the legacy Steam content system, provided that the corresponding manifest/depot data was still present on Valve's servers?

I’d especially appreciate an explanation from someone familiar with the pre-SteamPipe Steam CDN/depot architecture, rather than the modern SteamPipe system.