HardwareFreaks

Tag: Developer trust

  • Open source game engine Godot will no longer accept AI-authored code contributions: ‘We can’t trust heavy users of AI to understand their code enough to fix it’

    Featured image Open source game engine Godot will no longer accept AIauthored code contributions We cant trust heavy users of AI to understand their c

    The world of open-source development often operates on principles of shared effort and human accountability. But recently, that delicate balance has been thrown into question by the rise of artificial intelligence, leading to an increasingly frustrating phenomenon known as “AI slop.”

    For years, maintainers of beloved open-source projects have grappled with a growing influx of contributions—pull requests filled with code and text generated by AI agents. This sudden flood has proven to be more than just an inconvenience; it has become “increasingly draining and demoralizing” for those responsible for code review and mentoring new contributors.

    The core issue isn’t the interest in Godot, the open-source game engine powering hits like Slay the Spire 2 and The Case of the Golden Idol, but the unsustainable burden placed on maintainers. While an increase in contributions signals growing community enthusiasm, the quality and source of these submissions are beginning to erode the essential human element of collaboration.

    Recognizing that this trend is draining the energy needed for mentorship, the Godot Foundation and its maintainers have decided it was time for a clear boundary. After months of internal discussion, they are drawing a firm line in the sand regarding acceptable contributions.

    In a recent announcement, the Foundation revealed that their guidelines will soon be amended to explicitly forbid code authored by AI, pull requests submitted by AI agents, and AI-generated text used in human-to-human communication.

    The philosophy behind this shift is simple: maintaining a healthy project requires trust. The Foundation stressed that machine output cannot take responsibility for the code it generates, nor can heavy users of AI be trusted to fully understand their work well enough to fix complex issues.

    To ensure the pipeline remains focused on developing future maintainers rather than reviewing automated content, the new policies aim to add barriers against low-effort contributions. Contributors will be encouraged to use AI only for “menial things” and must disclose its use transparently.

    The Foundation is moving toward a framework that demands human accountability: contributors must be accountable for their code, and this responsibility must be upheld if mistakes occur. While acknowledging that technology evolves quickly, the Foundation remains committed to continually re-evaluating its stance as the landscape of AI tools changes.

    Credit: PC Gamer

  • Epic boss Tim Sweeney blasts Steam for putting AI tags on games — says move is ‘irresponsible of Valve’

    The AI Dilemma: Why Game Developers Are Fighting Over Disclosure

    The future of game development is being built at an accelerated pace, powered by artificial intelligence. With major engine updates, like Unreal Engine 6, are integrating powerful AI tools, the conversation has shifted from if AI will change gaming to how we should handle its integration. At the center of this debate is a fascinating friction point between technological progress and community trust, specifically concerning how developers disclose their use of AI in creating games.

    Tim Sweeney, CEO of Epic Games, has weighed in on this dynamic, arguing that AI should be viewed purely as an efficient productivity tool. He believes that tools like generative AI are fantastic for streamlining the tedious aspects of development—tasks like reviewing code or performing repetitive rigging work—freeing up human talent to focus on the truly creative elements: the architectural design and the unique vision behind a game.

    Yet, despite the potential for efficiency, the industry is grappling with the stigma attached to AI-generated content among players. Titles that openly disclose their use of these tools often face significantly fewer reviews and tend to receive less favorable feedback than their competitors. This disparity raises a critical question: are we judging games based on their artistic merit or on the method used to create them?

    The friction intensifies when we look at platform requirements. While the Steam ecosystem does not mandate full disclosure of AI use in the development workflow, it requires transparency if AI-generated assets or content appear within the final game or marketing materials. This requirement stems from a desire to protect the integrity of the gaming experience.

    Sweeney suggests that forcing developers to attach an Scarlet Letter of AI to their products, while well-intentioned, might be counterproductive. He argues that focusing on the player’s experience—how the game feels and plays—should matter most. Instead, he contends that the negative impact stems less from the technology itself and more from studios substituting genuine creativity and proper development processes with AI shortcuts.

    Market research supports this observation. Data indicates that games with generative AI disclosures often receive substantially fewer reviews, making it harder for innovative titles to gain visibility and find their audience. This suggests that the concern isn’t just about the tool used, but about the perceived authenticity of the final product.

    Ultimately, the core challenge remains balancing innovation with accountability. As AI tools become seamlessly integrated into the creative process, the industry must determine how to foster a space where cutting-edge technology can be utilized for productivity without sacrificing the trust and reputation that define the gaming community. The debate is no longer about whether AI belongs in games; it’s about ensuring that its presence elevates the art form rather than casting a shadow over it.

    Credit: Tom’s Hardware