<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Game Dev on fyvo1d's Blog</title><link>https://fyvo1d.cybercarrot.net/en/tags/game-dev/</link><description>Recent content in Game Dev on fyvo1d's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 20 Jun 2026 13:00:00 +0800</lastBuildDate><atom:link href="https://fyvo1d.cybercarrot.net/en/tags/game-dev/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Native in Games</title><link>https://fyvo1d.cybercarrot.net/en/posts/2026/06/ai-native-in-games/</link><pubDate>Sat, 20 Jun 2026 13:00:00 +0800</pubDate><guid>https://fyvo1d.cybercarrot.net/en/posts/2026/06/ai-native-in-games/</guid><description>&lt;p&gt;Translated by AI Translation Assistant&lt;/p&gt;
&lt;p&gt;AI for Gamedev is essentially a software engineering problem—game development is perhaps one of the most complex fields in software engineering—this year, the rapid pace of Agent development has already made people worry about what will happen to jobs. As for art, it has already been hit by a wave of AI, and planners are now basically inseparable from AI. QA, due to the relatively high cost of vision models, still appears relatively safe for now.&lt;/p&gt;</description></item></channel></rss>