Desarrollador de Dust Front RTS: rtsDimon, en solitario

It is rare for a strategy game with a global map, four factions and a full campaign to have one name attached to it. Dust Front RTS is that rarity: every system, patch note and store page line comes from a single person. Understanding how that person works explains most of the things players find unusual about the project — the silence between posts, the refusal to name a date, and the firmness with which certain design decisions are held.

Who rtsDimon is

rtsDimon is credited as both developer and publisher on Steam. He is a solo developer: there is no studio, no team credit and no publisher logo on the store page. His news posts are signed "rtsDimon (Dmitry)", which is the only personal name he has published in an official channel.

Scale matters here because it sets expectations for everything else. A one-person project does not have a community manager, a roadmap or a marketing calendar, and it does not answer questions on a schedule. It ships patches when they are ready and posts when there is something worth the effort of posting. Russian-language coverage places him in Chelyabinsk; his own posts do not state a location, so treat that detail as reported rather than confirmed by the developer.

The design ambition is large for one person. He has described the target as C&C-style RTS combat, a campaign in the spirit of Dawn of War: Dark Crusade, and a global mode more complex than either — closer to Total War in the strategic layer. That is the benchmark he is measuring himself against, and it is a fair explanation for why the game is taking as long as it is.

Solo, self-funded, and the Boosty page

The project is self-funded. There is no publisher money, no crowdfunding campaign and no early access revenue behind it — the game has not released, so there is no sales income either.

He has opened a Boosty donation page, and the way he framed it is worth quoting precisely: donations are described as maintaining pace rather than speeding up development. That is an unusually honest framing. Money is not being offered as a way to buy a faster release, and readers should not treat donating as a way to move the date.

This also explains the pacing of everything else. A self-funded solo developer cannot hire his way out of a bottleneck, and every hour spent writing a translated news post is an hour not spent on the game.

The feedback policy: bugs welcome, opinions filtered

The developer has been explicit about how he handles feedback, and the split is clean.

Bugs are objective and welcome. He has said the best form for a bug report is a gameplay recording rather than commentary — a clip showing the problem is worth more than a paragraph describing it. The D-30 changelog is the evidence that this works in practice: it lists 38 fixed entries, many of which read like direct responses to player-submitted clips, including a spotter bug that caused artillery to fire on itself and a selection bug triggered by alt-tabbing.

Subjective feedback is filtered through his own vision. He has stated plainly that he does not run the project by poll. Suggestions are read, but they do not become design by vote. If you have ever wondered why an obvious community request has not been implemented, that is the answer, and it is a stated position rather than an oversight.

One concrete example of a request that missed the demo: auto-repair and mass repair autocast were planned before the demo but were not finished in time. That is a feature he wanted too and simply did not land, which is a useful reminder that unfinished work is usually a capacity problem, not a disagreement.

Why he posts rarely on Steam

Infrequent posting is a deliberate choice, and he has explained the mechanics behind it.

• Steam news posts have to be long, translated and formatted before they are worth publishing.
• Steam has no embedded video player, so showing anything moving means hosting elsewhere and linking.
• There is a 5 MB limit on GIFs, which rules out the clip-heavy posts the game's systems deserve.
• He has said he will not create artificial news cycles before release.

The result is that each post carries real information — campaign length, faction scope, patch lists, FAQ answers — and the gaps between them are long. Silence between posts is not evidence of a stalled project; the demo's patch history is a better indicator of active work.

Two decisions he defends: the camera and modding

On the camera, he has said some thoughts exist but he is not ready to share them. What he has committed to: the camera angle will most likely not change, and the zoom level is undecided. He also notes that the camera is already higher than in many classic strategy games, which is the context for why he is unmoved by requests to pull it back further.

On modding, his answer is "probably not." Some functionality with the map editor was planned, but not for release. This is consistent with the rest of the project's posture: there is no console, no built-in cheat system and no mod support, so community modifications are not a planned part of the game's life.

The soundtrack: composed by EDLISE

The music is not stock. The soundtrack was composed specifically for the game by EDLISE, and the developer published a link to it on YouTube in his "End of fest" post. That is the whole of the official credit: one composer, one project, written for this game rather than licensed into it.

Beyond that, published information about the audio is thin. The store page lists full audio for English and Russian, and the demo is text-only English with voiceover planned for the release version. How much of the soundtrack ships at release, and whether it will be released separately, is not stated by the developer.

Related pages

• Dust Front RTS on Steam: store page, demo page and news
• Dust Front RTS release date: what is actually known
• What the full game adds over the demo
• Dust Front RTS demo: what is in it
• Official Dust Front RTS YouTube channel