Epic Games CEO Tim Sweeney has called Valve’s AI disclosure policy on Steam “irresponsible,” arguing that forcing developers to label games using AI could unfairly target smaller studios.
Sweeney believes AI will soon be a normal part of game development, so requiring developers to label games that use AI “makes no sense.”
"I think it's really irresponsible of Valve. They shouldn't do it, because it makes it much, much, much harder for a game developer to have a chance of success. You have to choose from either not using tools that can make you way more productive, and probably failing due to competition that does."
He also warned that these labels could make it easier for people to review-bomb games, especially those made by smaller studios.
Underground Beyblade leagues have started to appear in tattoo shops, parks, and malls across Asia
One tattoo parlor in Hong Kong has even started closing early to host community tournaments
Made another loaf of bread today. Many of you were asking to see the crumb of the last loaf, so here’s this one. I’m unsure how to keep it from spilling over the sides of the pan like this.
Hytale Shared Source - Our Plan:
We're releasing the full server source, the protocol, and all Hytale assets, even the stuff that never shipped! It will be on GitHub, with access modeled after Epic's Unreal Engine source: a valid game license and accepting the program terms will get you an invite to our GitHub org, where you can view, clone, and download the repo.
Updates ship with every release and pre-release. You'll see a branch for each, pushed automatically through our CI/CD pipeline. We strip individual commits and author data for two reasons: to protect the team's privacy, and to keep the constant churn of our trunk-based workflow out of the public history. Next up, we'll publish the sources jar to Maven so you can browse the code right inside your IDE.
On contributions: we won't accept PRs yet, but there's a path to opening them up. Honestly, we don't have the capacity to review them without tanking our own productivity, and in the age of AI we'd drown in volume. It's not that the contributions are bad. It's the sheer number.
We've spent years in open source, and nothing kills the passion faster than PRs that sit unanswered. That's how a repo turns toxic, and we won't do that to you. Keeping it semi-public and license-gated also helps us moderate and reduce spam access and keep our lawyer happy while still giving the community the ability to see and use the code with Hytale.
Here's the plan: we'll start with an invite-only contributor model for select community members. As that proves out, we'll promote the trusted ones to maintainers who can push PRs to the team. Once we have maintainers we trust, we'll open contributions to everyone, alongside a code of conduct.
The legal framework was the hard part. We wanted to give you maximum freedom inside the Hytale ecosystem while stopping competitors from copy-pasting our code.
It took far longer than it should have, but we're glad to ship it. This pulls the community out of the decompilation gray zone, for both the developer experience and the legal side.
https://t.co/WTZA4Z29G7