Valve releases Team Fortress 2 code
Scope of the Release
- Only the TF2 game layer is released, not the underlying Source engine.
- You cannot port TF2 to new platforms without either re‑implementing Source or using leaked engine code (which would be legally risky).
- Engine features like physics (Havok/VPhysics) and some rendering backends remain closed.
Why Source (and Source 2) Stay Closed
- Major reason cited: third‑party middleware (Havok, Scaleform, audio/video codecs, console SDKs) under strict NDAs and non‑OSS licenses.
- Untangling or rewriting these components would be a large, low‑ROI legal and engineering effort.
- Some argue Valve also avoids support burden and public scrutiny of a messy, legacy codebase.
Comparisons to Other Engines
- Debate over Source’s relevance: some call it outdated and technically poor compared to Unity/Unreal/Godot/O3DE; others note it “worked” and still ships popular games (Apex, older Valve titles).
- Source 2 is seen as substantially more modern (PBR, volumetrics, better tools, Rubikon physics), but its ecosystem is tiny compared to Unreal’s.
- Godot is praised for indie‑scale 2D/3D, but multiple commenters say it’s not yet a serious replacement for AAA‑class engines.
Modding, Forks, and Community Maintenance
- Strong optimism that this will supercharge mods and derivative games (e.g., TF2 Classic, other TF‑like projects, potential Steam releases).
- Many see it as Valve unofficially handing TF2’s evolution to the community while keeping servers/economy centralized.
- Some hope for similar treatment for GoldSrc and HL1/2; legal and licensing tangles are cited as blockers.
Cheating and Security
- Concern that access to TF2 code could aid cheat authors; counter‑argument is that Source and TF2 code have leaked multiple times, so serious cheat makers already had what they needed.
- Anti‑cheat is viewed as more a design/service problem than a “source secrecy” one.
Valve’s Priorities, Platforms, and Business Model
- Repeated reminder: Valve is ~400 people; limited staff constrain how many engines/ports they can support.
- Mac support is seen as low‑priority: Apple’s historic hostility to games, 32‑bit deprecation, Metal‑only APIs, and tiny Steam share make ports hard to justify.
- Discussion of Steam’s 30% cut, its much lower effective cut for mega‑publishers, and the contrast with engine royalties; many argue Valve makes far more from store + lootboxes/skins than from anything engine‑related.
Ethics and Legacy
- Several threads criticize Valve’s skin‑based lootbox economy and its role in underage gambling and money laundering, especially in CS.
- Others emphasize Valve’s positive legacy: idTech‑style source releases, strong Linux/Proton support, and the likelihood that TF2 will live on for decades through community efforts.