Starting Work on Bellum Imperii
In late 2023 Lofi Studios started Bellum Imperii on Roblox: internal large-scale conflict, readable stakes, progression built to survive player optimization.
At the end of 2023 we began Bellum Imperii, an internal Roblox project aimed at large-scale conflict, readable stakes, and progression systems that do not melt the moment players optimize them. This post is the public origin note: what we were trying to prove, what we optimized for on day one, and what we refused to treat as a substitute for depth.
For the studio thesis on systems-first design, read why we started Lofi Studios. For how ownership reshapes incentives compared with contract work, read why ownership changes everything in game development. For friction and social structure as design tools, read why Northwind is built around scarcity.
Why another internal title after Northwind
Northwind explores player-driven tension through exploration, logistics, and social roleplay with material stakes. Bellum was meant to explore a different slice of the same studio question: what happens when organized competition scales and players need to understand why they won or lost?
Contract work sharpened execution, but ownership is where you prove you can steward incentives for years. We acquired Northwind raised the bar for what "live stewardship" means. Bellum was a bet that we could build another internal laboratory without cloning Northwind's answers.
What we optimized for on day one
- Readable conflict: outcomes should make sense in principle even when they sting emotionally.
- Economy and crafting that feed the war: not a parallel hobby minigame that ignores the main contest.
- Live testing discipline learned from contract-era ships like Gym Trainers, where volume exposed convergence fast.
What we did not optimize for
We did not aim for a cinematic vertical slice that hid shallow systems behind lighting. Smoke machines are not a substitute for incentives. We also did not aim for a roadmap that only looked good in a launch trailer.
If you want the negative pattern in one link, what most games get wrong is still the cleanest summary of post-optimization flatness.
Roblox-specific constraints we planned around
Roblox audiences cross-train habits across many games. Dominant strategies spread through friends, groups, and clips. That means competitive systems need clarity and strong feedback loops, because confusion reads as unfairness faster here than in many standalone titles.
How this connects to immersion and world coherence
Large battles can become noisy quickly. We cared about whether players could still understand the world's logic under stress. What makes a game world feel alive is adjacent reading: coherence is part of believability, even in competitive contexts.
Convenience versus readability
Competitive games face convenience pressure too: faster respawns, easier logistics, softer penalties. We treated those requests as design forks, not as automatic upgrades. Why convenience kills immersion is useful here even for non-roleplay titles, because readability and stakes are still a kind of immersion.
What we told ourselves about scope
Internal projects can balloon when nobody is holding an external milestone line. We tried to keep scope honest by tying work to testable hypotheses about player behavior, similar to how we ran early stops on prototypes like Testing Boxing Titans.
Later chapters on this blog
Follow-up posts tracked live launch, scale tests, rebuild work, and the transition that eventually became Imperium. If you are reading chronologically, treat this note as the starting marker, not the final word.
Question we used in early reviews
If a new player watches a clip of a fight, can they understand what each side was trying to do? If not, the spectacle will not convert into players who stay.
Why "internal" mattered for learning speed
Internal development is not automatically higher quality. It is higher accountability. When the loop is wrong, you feel it in your own planning meetings, not only in a client's inbox. That accountability is what we wanted after seasons of contracting where the structural fix sometimes lost to milestone politics, as described in the hidden tradeoffs of building games for other people.
Technical foundations we refused to defer
Large-scale PvP-adjacent experiences need netcode realism, performance budgets, and tooling for diagnosing exploits. Deferring those as "phase two" is how you ship a trailer and collapse under real traffic. We aimed to build test harness thinking early, similar to the discipline we praised in postmortems like Strong Simulator.
The player skill spectrum problem
Competitive experiences have to serve new players and veterans without making either group feel the game is lying to them. That usually means strong onboarding clarity plus end-state systems that still reward planning, not only reflexes.
How Northwind and Bellum differ (on purpose)
Northwind emphasizes social material friction and exploration-forward stories. Bellum emphasized organized competition and large-scale readability. The studio learning goal was to deepen two different muscles rather than clone one successful template.
Partnership with our own roadmap
Starting Bellum while stewarding owned live titles forced explicit calendar honesty. Why we stopped building games for other studios is part of the same story: protecting senior attention for long-horizon work.
What success would have looked like in the first year
Not "big number once." Repeatable clarity: players understanding stakes, returning because competition still feels fair, and systems that could be tuned without rewriting identity weekly.
Bellum was a bet that we could pursue that clarity on purpose, not only inherit it from an existing community already shaped by years of culture.
We expected iteration to be noisy, public, and instructive. That was the point.
Thanks for reading, and for playing with us on Roblox.