AI adoption jumps From 51% to 85% among Japanese game developers

Generative AI has moved into everyday game development in Japan at remarkable speed. A survey of 1,349 developers found 85.8 per cent now use generative AI somewhere in their work, up from 51 per cent a year earlier. This isn’t limited to making artwork or producing chunks of dialogue. Developers are using AI for coding, debugging, paperwork, documentation and other jobs sitting behind the games people play. Daily use is already common. Around 63 per cent of developers who work with generative AI use it every day, with another 22.8 per cent turning to it from time to time. Those numbers paint a fairly clear picture. AI software has shifted from something developers experiment with into another tool sitting beside existing development software.

Generative AI has moved into everyday game development in Japan at remarkable speed. A survey of 1,349 developers found 85.8 per cent now use generative AI somewhere in their work, up from 51 per cent a year earlier. This isn’t limited to making artwork or producing chunks of dialogue. Developers are using AI for coding, debugging, paperwork, documentation and other jobs sitting behind the games people play. Daily use is already common. Around 63 per cent of developers who work with generative AI use it every day, with another 22.8 per cent turning to it from time to time. Those numbers paint a fairly clear picture. AI software has shifted from something developers experiment with into another tool sitting beside existing development software.

Generative AI use has climbed quickly

A jump from 51 per cent to 85.8 per cent in a single year is hard to miss. The figures cover a broad mix of generative AI software, ranging from ChatGPT and GitHub Copilot to tools built for content creation and production support. Developers aren’t using every service for the same purpose either. Some rely on AI for code. Others use it to draft documentation, spot bugs or deal with repetitive office work.

This makes the term generative AI rather broad in a games industry setting. Seeing an AI tool somewhere inside a studio doesn’t mean a game suddenly fills its levels with machine-generated art or dialogue. Much of the activity happens far away from anything players see.

Coding and debugging are a big part of AI use

Programming support has become one of the clearest uses. A developer can use an AI assistant to examine code, suggest possible fixes, explain an error or create a rough starting point for a routine. It can help with documentation too, especially during production where teams produce large amounts of technical material.

Administrative jobs are part of the picture. Generative AI can prepare rough text, organise information and speed up repetitive tasks. None of this sounds glamorous, but game development contains plenty of work outside character models, combat systems and level design.

Content creation still appears in the mix. Studios can use generative tools for images, text, localisation, testing and other production jobs. Adoption varies sharply between companies, though, and plenty of teams keep AI away from certain parts of development.

Developers report shorter production times and lower costs

Efficiency comes up frequently in the survey results. Among respondents, 837 said generative AI had opened up more creative options during development. Another 738 said it reduced technical barriers. Developers reported savings in both development time and production costs too.

The numbers become much smaller once the question moves to the player experience. Only 147 respondents said generative AI had directly improved what players experience in a finished game. For now, its strongest impact appears to sit inside production rather than on the screen.

It’s an interesting split. AI might help a programmer find a problem faster or save someone time preparing documentation, yet none of this needs to appear in the finished game. Players might never have any reason to notice.

Japanese game companies are writing AI rules

Studios aren’t leaving AI use entirely in the hands of individual employees. A separate survey of game companies found 74 per cent had introduced policies covering generative AI. Companies are setting their own boundaries around which tools staff can use, what material can enter those systems and where generated content can appear during production.

Company figures give a different view of adoption. Among participating businesses, 26 used generative AI in some form and 27 didn’t. Twelve companies used AI for visual assets, with smaller numbers applying it to story work, localisation, quality assurance or programming.

The difference between company and developer figures makes sense. A survey of individuals can include many developers working inside a single studio, each using the same approved tools under one company policy.

AI is settling into the game development toolbox

The headline figure is striking, but the details matter more. Generative AI use among Japanese game developers isn’t centred on one task. Coding assistants, debugging tools, documentation systems and production software share space with image and text generators. Studios are choosing different uses, with internal policies setting limits around how far AI enters each project. For many developers, AI appears less like a replacement for an existing discipline and more like another piece of software used during production.

With 85.8 per cent of surveyed developers now using generative AI in some form, experimentation has clearly moved into routine use. The bigger question for Japan’s games industry is no longer whether developers use AI. It’s where studios choose to use it, which jobs gain from it, and how deeply these tools become part of day-to-day development.

Spread the love
error: