Loading...
benkimchi
April 26, 2026 at 02:06 AM
Expanded benkimchi developer profile with project profile table, public channels, stated influences, solo project scope, announcement reception, and unconfirmed details (2026-04-26)
benkimchi is the solo independent developer behind DREADNOUGHT TARTARUS. On the Steam store page, both the Developer and Publisher fields list benkimchi, meaning the project is a single-person indie effort built and self-published under the same banner. For a game-side overview, see the overview; for the central vessel benkimchi is designing the campaign around, see the TARTARUS battleship.
Field | Detail |
|---|---|
Role | Solo independent developer |
Project | DREADNOUGHT TARTARUS |
Status | In active development; Q3 2026 release window targeted |
Genre Direction | Semi-automated strategic simulation centered on a single colossal battleship |
The developer maintains an active presence on X under the handle @NAP_benkimchi, where regular development posts are shared as the project advances. Updates have included short clips of in-engine footage, work-in-progress UI screens, and devlog summaries. The X account, the Steam store page, and the trailers and devlogs released alongside the announcement form the entirety of benkimchi's public communications channels at this stage.
benkimchi has been explicit about the references that shaped the look and feel of DREADNOUGHT TARTARUS. The aesthetic frame is anime sci-fi, drawing on capital-ship-driven series rather than ground-level mech action. The cited reference points are Macross, Legend of the Galactic Heroes, and Gundam, which together inform the framing of large-scale aerospace combat, the dignity of capital-class engagements, the relationship between a colossal vessel and its smaller deployable units, and the hard-surface mechanical detailing of the ship designs.
On the interface side, the first devlog notes that part of the UI design language was inspired by PS3 and PSP interfaces. That choice gives the on-screen menus a chunky, deliberately tactile feel reminiscent of mid-2000s console front-ends rather than a modern flat overlay.
What makes the benkimchi credit unusual in context is the breadth of the systems being delivered by a single developer. DREADNOUGHT TARTARUS is not a small experimental piece. The publicly described feature set includes:
Modular battleship loadouts spanning hull structures, functional modules, main cannons, missiles, super weapons, carrier-based fighters, and support units.
A continuous strategic-map campaign with route planning, objective selection, and a battlefield that advances in real time rather than resetting between missions.
A reverse-engineering progression loop where intel from defeated enemies feeds new upgrades and armaments back into the dreadnought.
A deployable combat mech launched from the battleship's hangar bay, giving the game a second scale of engagement on top of the capital-ship layer.
Three weapon firing modes (Manual, Automatic, Focus Fire) configurable per hardpoint.
Delivering this combination as a one-person project is part of why the announcement attracted attention beyond the usual indie strategy circles. See the continuous campaign and reverse engineering pages for how those systems are intended to interlock.
DREADNOUGHT TARTARUS is benkimchi's first announcement to break out into substantial English-language coverage. The Steam wishlist count crossed ten thousand within roughly two days of the reveal. For a self-published solo project with no preceding hype cycle, that scale of immediate wishlist accumulation is unusually strong and has been the main signal that the project is being watched closely as it develops.
Out of respect for what has actually been disclosed publicly, the following items are not confirmed and should not be treated as fact:
Real name behind the benkimchi handle.
Country of residence, nationality, or specific city or region.
Prior released projects, prototypes, or jam entries credited to the same developer.
Studio affiliations, parent company, or any past or present employment history.
Whether contractors, freelancers, or collaborators have contributed to specific assets, music, code, or localization.
Educational background or professional training prior to this project.