← BACK TO INSIGHTS FEED

Fireshine Games makes 'no generative AI art' a binding condition in all publishing deals

Summary
Fireshine Games CEO Brian Foote declares generative AI art a hard "red line" in publishing partnerships.
The policy is a contractual gate, not a preference.
AI art disqualifies a partner; code tools like Copilot remain permitted.
Hooded Horse extended its ban to placeholder AI assets in January 2026.
Two major indie publishers now enforce similar standards, reshaping deal criteria for studios.
"We don't work with partners that are relying on generative AI or generative art, and I think that's the red line we are very clear on"
— Brian Foote, CEO, Fireshine Games
01

Foote draws a precise line: AI art is out, productivity tools are not

Fireshine's policy functions as a binary pass/fail for partnership eligibility.
A studio using GitHub Copilot for scripting remains signable.
One using Midjourney for concept art or UI assets does not.
"If AI means code completion or means using Copilot in Word, that's an entirely different set of scenarios"
— Brian Foote, CEO, Fireshine Games
The burden falls on developers to demonstrate which category their tools occupy.
02

Player sentiment and ecosystem health drive the policy, not ideology

Foote grounds the ban in two risks: player perception and developer community impact.
"That is not something that we think players are interested in at this point in time, and not something that we think is healthy for the development community"
— Brian Foote, CEO, Fireshine Games
The "at this point in time" qualifier signals a reactive stance, not a permanent one.
Publishers distributing games absorb unresolved copyright liability around AI-generated assets.
The ban functions as IP risk mitigation for Fireshine's own catalog.
03

Hooded Horse's stricter standard bans AI even in placeholders

Hooded Horse CEO Tim Bender went further in January 2026, covering every pipeline stage.
"We recommend they don't use any gen AI anywhere in the process"
— Tim Bender, CEO, Hooded Horse
Bender's rationale: placeholder AI art can migrate into shipped builds undetected.
Two major indie publishers reaching the same policy independently within months forms a pattern.
Studios cannot treat this as a niche preference from a single gatekeeper.
04

Studios must treat asset provenance as a due diligence deliverable

The compliance gap is documentation: studios must trace the origin of every visual asset.
Without toolchain records for concept art, UI, textures, and marketing materials, compliance is uncertifiable.
The emerging standard: human-authored assets at every stage of core creation.
Generative AI tools are tolerated only for non-visual, non-shipped development support.
Pipeline documentation now ranks alongside build stability and revenue terms in publishing conversations.
Events
Companies
Games
—
Locations
—

COMPILED BY

RELATED ARTICLES
EXPLORE MORE

Comments (0)

No comments yet. Be the first to share your thoughts!