Project ideas from Hacker News discussions.

Epic Games tells employees to use AI to get Disney game done

📝 Discussion Summary (Click to expand)

1. AI‑assisted development is becoming the norm
Many commenters note that relying on AI for code is already standard practice at large studios.
- “Having very little hand‑written code is quickly becoming the norm.” – Jcampuzano2
- “At my job it’s essentially the same. Everyone is actively encouraged to use AI to move faster and barely anybody writes code by hand.” – Jcampuzano2
- “Agreed, you've got to have had your head in the ground to be ‘stunned’ by what is largely ‘industry standard’ now.” – joshstrange

2. Fear that AI‑generated content will lower game quality and creativity
Several users worry that handing over art, mechanics, and effects to LLMs will produce “slop” and erode the artistic value of games.
- “Lots of tech folks will see an AI make a CRUD app and think that means the AI will be equally capable of making art … The end result will be a lot of mass market art is going to become noticeable worse …” – slg
- “The statement did include that all art should also be AI‑generated, which is a whole other thing.” – fabian2k
- “Any game mechanics and effects you want to make artistically represent your game will just turn into sloppa when generated by an LLM …” – Madmallard

3. Workplace pressure, surveillance, and employee pushback
Workers describe being forced to adopt AI tools, monitored closely, and even blamed for failures when the technology falls short.
- “Epic will blame the workers and say they sabotaged it, I predict.” – pfdietz
- “employees were reportedly ‘stunned,’ which many hoped the news was some kind of sick joke.” – Jcampuzano2
- “You have to use company provided tooling and they're sure to log every single thought of yours.” – avh02
- “its definitely a disruption, and a shocking one at that, for some C-suites to start mandating things like the disallowal of non‑AI code.” – tyromaniac


🚀 Project Ideas

Generating project ideas…

LocalAI GameDev Assistant

Summary

  • An offline, privacy‑first AI coding assistant that integrates with popular game‑dev IDEs (VS Code, Rider, CLion) to provide code suggestions without sending any data to external servers.
  • Core value: developers get AI‑boosted productivity while retaining full control over their codebase and avoiding corporate telemetry or unintended AI‑generated art/code.

Details

Key Value
Target Audience Indie and AAA game developers, especially those wary of data collection and AI overreach.
Core Feature Local LLM inference (e.g., using Llama.cpp or Ollama) with context‑aware completions, prompt templating for common game patterns (physics, input, rendering).
Tech Stack Rust/C++ for inference engine, WASM plugin for IDE integration, optional CUDA for GPU acceleration; model weights stored locally.
Difficulty Medium (requires setting up local LLM and IDE plugin).
Monetization Revenue-ready: subscription‑based pro tier ($5/mo) for model updates and premium prompts; free base version.

Notes

  • HN commenters expressed concern about “company provided tooling and they’re sure to log every single thought of yours” (avh02) and about AI replacing hand‑written code (Jcampuzano2, pfdietz); this tool runs entirely on the developer’s machine, giving them privacy and control.
  • Enables discussion about responsible AI use in game dev and could become a reference implementation for privacy‑first AI‑assisted coding.

SplitScreen Restorer for Fortnite

Summary

  • A lightweight utility/mod that re‑enables local split‑screen multiplayer in Fortnite by replicating the legacy login‑trick workflow or providing a LAN‑based co‑op wrapper.
  • Core value: restores the ability for families and friends to play Fortnite together on a single console/PC, addressing the frustration of lost split‑screen support.

Details

Key Value
Target Audience Fortnite players who want local co‑op (parents, siblings, roommates) and modders interested in preserving legacy features.
Core Feature Intercepts Epic’s online services calls, simulates the “login with one controller, log out with another, log back in” sequence, and launches two local player profiles in shared screen mode.
Tech Stack C#/.NET wrapper using Epic’s Online Services SDK or reverse‑engineered API; optional DLL injection for Windows; cross‑platform via Proton/Wine for Linux/macOS.
Difficulty Medium (requires understanding of Fortnite’s auth flow and handling updates).
Monetization Hobby (open‑source, donations via GitHub Sponsors).

Notes

  • User arealaccount said: “I haven’t been able to play split screen Fortnight with my son for the past several seasons… the trick … doesn’t even work.” This tool directly solves that pain point.
  • Could spark conversation about platform holders removing local multiplayer and the preservation of consumer‑friendly features; also serves as a case study in community‑driven compatibility layers.

Blueprint-to-Code Exporter & Learning Companion

Summary

  • A tool that converts Unreal Engine Blueprint visual graphs into clean, well‑commented C++ (or Python) source files, preserving functionality while exposing the underlying code.
  • Core value: lets developers keep the speed of visual scripting for prototyping, then examine, modify, and learn the generated code, reducing the black‑box feeling and improving understanding of game systems.

Details

Key Value
Target Audience Unreal Engine developers, technical artists, and educators who use Blueprints but want deeper code insight.
Core Feature One‑click export of selected Blueprint graphs to readable C++ classes, with automatic mapping of nodes to functions, plus inline comments explaining each node’s purpose.
Tech Stack Python parser using Unreal’s .uasset format (or via UE’s AutomationTool), Jinja2 templating for code generation, optional integration via Editor Utility Widget.
Difficulty High (requires parsing complex Blueprint asset format and handling edge cases).
Monetization Revenue-ready: one‑time purchase ($29) for pro version with advanced optimizations and team licenses; free community edition for basic export.

Notes

  • Commenter mycocola noted: “developers are in touch with the underlying systems … easily done through writing and modifying them”; this tool bridges visual scripting and source code, satisfying that desire.
  • Provides a practical utility for learning and code review, likely to generate discussion on HN about the trade‑offs between visual and textual programming in game dev.

Read Later