STARFIGHTER engine released on GitHub

Most small game teams do not struggle with drawing sprites or writing menus first. They struggle when the last 10 percent means packaging a web game into a desktop app, wiring in Steam achievements, and making the overlay work on Windows without weeks of native code debugging. (github.com, github.com, github.com) That is the gap this release is aiming at. INNBC has put its STARFIGHTER engine on GitHub, alongside a public GitHub profile that also exposes a custom Steamworks module for JavaScript and Electron projects. (github.com, github.com) JavaScript is the language behind a huge share of browser games, and Electron is the wrapper that turns a web app into a Windows, Mac, or Linux desktop program. A game built that way can reuse web tools, but Steam features usually still need a bridge into Valve’s native Steamworks software kit. (phaser.io, github.com, github.com) That bridge has existed for years, but it has usually meant stitching together third-party modules like Greenworks or Steamworks.js, then fixing platform quirks yourself. Even recent templates for Electron-on-Steam publishing still treat Steam setup as a separate job with its own build pipeline and credentials work. (github.com, github.com, github.com) INNBC’s own game shows the pitch in concrete form. The Steam store page for INNBC STARFIGHTER says the game is free to play, launched on March 21, 2026, uses unlocked 60-plus frames per second, and includes online co-op for two players. (store.steampowered.com) The store page also lists a very small install size of 1 gigabyte and minimum graphics hardware as Intel UHD Graphics, which suggests this is not chasing the usual giant-engine model of tens of gigabytes and heavy graphics requirements. It is closer to a lightweight shipping stack for arcade-style games. (store.steampowered.com) There is also a clue in INNBC’s GitHub account structure. One of its pinned repositories is a Rust project described as an “improved version of the original steamworks.js module” with added logs and expanded peer-to-peer networking, which points to the team solving Steam plumbing problems directly rather than only building game content on top. (github.com, github.com) That matters because Steam integration for web-based desktop games is often where the simple prototype stops being simple. The overlay, achievements, peer-to-peer multiplayer, and packaged builds all sit at the boundary between browser-style code and native desktop code. (github.com, github.com, github.com) The immediate audience is not a studio choosing between Unreal Engine and Unity. It is the smaller team that already likes JavaScript, already has a browser-friendly game loop, and wants a ready-made path to a Steam release without inventing its own launcher, native bindings, and deployment scripts. (phaser.io, github.com, github.com) The open question is how complete the GitHub release really is: engine code, tools, examples, build scripts, and license terms all decide whether this becomes a reusable engine or just a one-game code dump. But the public pieces already show the core idea clearly: a web-style game stack, wrapped with Electron, shipped on Steam, and now being offered as a product instead of kept private. (github.com, store.steampowered.com, github.com)