Development transparency and production workflow

The recording presents Scars of Honor as a project developed with unusually public production discussion. Internal planning, unfinished assets, known bugs, and scheduling logic are all shown or described directly, with an emphasis on exposing work in progress rather than hiding it behind polished marketing.

Transparency about unfinished work

The build shown is repeatedly identified as a development build. Crashes, missing links in talent setups, unstable maps, shader issues, and placeholder or outdated environments are acknowledged openly while being demonstrated.

The recording also clarifies that some trailer footage uses in-game assets presented through cinematic shots or cutscene-style staging, and should not be read as raw gameplay in every case.

How the playtest date was chosen

The 30 April playtest date is described as the result of internal production planning rather than a symbolic or marketing-driven choice. The studio is said to work from a development plan divided across departments, with weekly tasks mapped toward the point where a public test becomes feasible.

The date is therefore presented as a coordination outcome between teams rather than an arbitrary announcement.

Development pace and system creation

A major point of emphasis is the speed at which systems were built over the previous year. The recording attributes this to the team's workflow and tooling, especially the proprietary backend technology used for MMO systems.

Systems said to have been developed within roughly the last year include combat, dungeons, the scar system, the talent system, gathering, professions, questing, and arenas. Combat is described as having gone from absent to publicly demonstrable in a short period before a Brazil game show appearance.

Internal tools and live iteration

The recording describes a workflow in which new spells and features can be added quickly because of the studio's backend architecture. A healing spell with an aura is said to have been created from scratch in about 12 minutes as an example of this speed.

There is also interest in showing development live in future streams, including programming sessions focused on building or fixing a feature in real time.

Team structure and studio culture

The studio is described as operating through multiple departments working toward shared milestones. The team is characterized as highly committed, with members staying late when needed to deliver on goals.

This production framing is used to support confidence in the public test: the argument is not that the build is bug-free, but that the team can respond quickly to issues once they are identified.

Source

• Recording: Scars OF Honor - First PLAYTEST Date Review | Final Stance on Bag Space | Playtest Discussion
• YouTube: Watch on YouTube
• Published: Sunday, March 8, 2026 at 9:00 PM UTC