Game dev lists 8 real-world AI uses, says he'll never hand-write A* again
draginol · x · 2026-10-01
Game studio developer draginol shared his concrete uses of AI in game development: importing art assets into a custom engine, debugging odd linker errors, adjusting heightmaps, batch-converting textures to DDS formats, mass-balancing game numbers, mining crash logs to find the code that actually has the bug, and editing changelogs.
On classic tasks like writing an A algorithm, he says he won't hand-write one again — having Claude do it versus digging through cpp files and copy-pasting differ only in tedium. His takeaway: AI's value is offloading the mechanical drudgery of development, not replacing core creative decisions.
Related event: Stardock Founder Shares Practical AI Workflow for Game Development(4 posts)→
More from coding & agent
- Eve agent tool cuts build time 8x to 6.9s by reusing compiler module graph — evilrabbit_ · 2026-11-19
- Dev shares NL-driven testing UI: 'the best interface is chat' — KlausCodes · 2026-11-19
- Devs flag GPT's defensive programming for hiding bugs; OpenAI asks for /feedback cases — pvncher · 2026-11-19
- Flutter ships A2UI 1.0: agents respond with real interactive widgets, not chat text — rseroter · 2026-11-19
- Skills vs MCP vs RAG vs Memory: the four context mechanisms AI agents actually need — MaryamMiradi · 2026-11-19
- Anthropic details agent memory: 'dreaming' lets Claude organize its experience — daniel_mac8 · 2026-11-19