And your comment also counts for jackshit since you provided no evidence of your claims, not even your own experience.

So you can fuck right off, buddy.

I have worked on games, and have a good understanding of the workflows involved.

You’ll obviously still need to do the creative parts manually (and should!) but the majority of the work involving the engine core build and the specific game coding, that can all be sped up borderline exponentially.

But I’m glad that someone with absolutely no understanding of the topic does their best to call out those who do show some experience on the topic just because they don’t get a neatly pre-chewed and pre-digested reply detailing all the information they lack and are unwilling to look it up themselves. As a next step would you like me to cut your steak up and feed it to you byte by byte, or tuck you in at night?

My own fucking experience. Which I’ve already explained in detail above.

By improving the cadence of projects.

A project costs X amount because of the standard template of pay per time unit Y multiplied by timeframe in time unit Z.

Simply said if you have 100 people working on the project, that costs 100Y per hour. If the project takes 6 months (approx. 960 hours), you multiply the two and get that your costs are 96000Y.

Now the two ways to reduce this is to either reduce the number of employees, with AI you can get rid of maybe 2/3, reducing the expenses to 32000Y…

Or since AI speeds up almost every workflow by about 8 to 10 times, you can keep all the people, but cut down project time from 6 months to about 2 months, which doesn’t just reduce the expenses by the same 2/3 but also increases potential profits for the same 6 month period by 200%, as instead of one product you’re releasing three.

Cutting jobs ain’t the only way to reduce costs with AI.

Which is a different article about a (somewhat) unrelated topic.

Using AI for development is already out there, and you can’t put that genie back in the bottle. As an engineer I’m already using it in my daily work for tons of things - I’ve built separate agents to do a number of things:

• read work tickets, collate resources, create a work plan, do the initial footwork (creating branches, moving tickets to the right states, creating Notion document with work plan and resources)
• read relevant changes in UI design documents and plan + execute changes (still needs some manual review but e.g. with Android Jetpack Compose, it makes 90-95% of the needed work and requires minimal touch-up)
• do structural work - boilerplates, etc.
• write unit and integration tests, and already working out a UI test automation agent
• do code reviews on changes, document them, and write appropriate commit messages
• do PR reviews - I still review them myself but an extra eye is always helpful

guess what, AI didn’t replace me, it just allowed me to focus on actually thinking up solutions instead of doing hours of boilerplate stuff.

AI isn’t the enemy in software development. Companies who think they can replace engineers with AI. Middle managers will sooner be on that date, as they were mostly useless anyway.

Sorry but procedural generation will never give you the same result as a well tuned small LLM can.

Also there’s no “hoping”, LLM context preservation and dynamic memory can be easily fine-tuned even on micro models.

That’s… not what this is about?

The point of integrating AI into games is to provide further diversity within the game.

Think Skyrim. By default you’re limited to 3-4 discussion options, right? Imagine now, if you will, that you could just… type in anything, including emotional markers, and have the characters respond interactively to the statement and tone. No longer are you bound by limited dialogue in RPGs.

visual generative AI will just spice up the visuals - hopefully. Things like repetitive textures and such will disappear as the game generates brand new textures for each grid element. Or create tons of background characters without the need to specify them. The list goes on.