Esc
IP / CopyrightEscalating

Dolphin dev deletes human SMG port after AI backlash

Is this a scandal?

Not yet — activity is spiking. Noise 42/100, holding steady, across 1 source.

SCAND-327162as of Methodology
Cite this incident"Dolphin dev deletes human SMG port after AI backlash." SCAND.Ai incident SCAND-327162, noise 42/100 as of October 28, 2026. https://scand.ai/scandal/dolphin-dev-deletes-human-smg-port-after-ai-backlash
FORECASTForecast, not fact

Community forks of the deleted port will likely emerge quickly because emulation preservation culture prioritizes archival continuity over individual developer grievances.

42

Noise 42/100 — louder than 99% of tracked AI controversies.

AI-assisted analysis · How we work

Why it matters

Highlights how AI integration disputes can destroy community preservation projects and alienate user bases.

Key points

  1. Developer icebitez deleted a functional human-coded Super Mario Galaxy port for Dolphin emulator.
  2. Deletion followed community backlash against the developer's AI-assisted Super Mario Galaxy 2 port.
  3. The original port offered native controller support without requiring extensive Dolphin configuration.
  4. Community critics opposed the use of generative AI tools in emulation preservation efforts.
  5. The removal eliminates a significant accessibility improvement for Super Mario Galaxy players.
  6. Incident highlights volatility of volunteer preservation projects amid AI ethics disputes.

The story

A prominent Dolphin emulator developer has deleted a functional, human-coded port of Super Mario Galaxy following intense community backlash over an AI-assisted Super Mario Galaxy 2 release. The developer, known as icebitez on Bluesky, reportedly rushed the SMG2 port using artificial intelligence tools, prompting criticism from emulation enthusiasts who value manual preservation efforts. In response to the negative reception, the developer removed the original non-AI port of the first game entirely. This incident underscores growing tensions within open-source communities regarding generative AI usage in software development. The deletion eliminates a significant accessibility option for players seeking native controller support without complex configuration. Community members have expressed frustration that valid preservation work was discarded due to controversies surrounding adjacent AI-generated content. The event raises questions about sustainability in volunteer-driven emulation projects when ideological disputes override technical utility.

Who's involved

Critic
Emulation Community

Opposed AI-assisted ports and criticized the deletion of functional human-coded preservation work.

Defender
icebitez

Defended use of AI tools for SMG2 and subsequently deleted the human-made SMG1 port amid backlash.

How the conversation shifted

the split has narrowed

Polarity (0–100) from the noise pipeline, sampled over time.

Join the Discussion

Discuss this story

Community comments coming in a future update

Be the first to share your perspective. Subscribe to comment.

Noise Level

Buzz42?Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
Decay: 100%
Reach
40
Engagement
99
Star Power
10
Duration
1
Cross-Platform
20
Polarity
50
Industry Impact
50

The timeline

  1. Human-made SMG1 port available

    Functional port with native controller support existed before being deleted in response to criticism.

  2. AI-assisted SMG2 port released

    Developer rushed out a Super Mario Galaxy 2 port utilizing AI tools, triggering community backlash.

  3. Developer confirms deletion of human SMG port

    icebitez posted on Bluesky acknowledging the removal of the original port following AI controversy.

The full record

Sources & methodology

Every claim above traces to these primary items. How we score →

The forecast

Community forks of the deleted port will likely emerge quickly because emulation preservation culture prioritizes archival continuity over individual developer grievances.

Forecast, not fact — an editorial estimate we score when this resolves.

You're up to date

That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.

Follow this story

We keep this page current — no need to check back. We'll send the next real change to your inbox, nothing else.

Tracking this story since October 19, 2026.