Witchbrook's development history reaches back to a 2016 internal concept pitch, making it roughly a decade-long project by October 2026. That is a span of development history, not an exact count of continuous full-team production. It includes early prototypes under the working name Spellbound, a change in visual direction, an engine transition, a growing simulation, and extensive later testing. The game is currently scheduled to launch on January 28, 2027.
Several dates answer different versions of the question. The 2016 pitch explains the origin of the idea. The public discussions in 2017 show an early project already being worked on. The 2018 naming established Witchbrook as the title. Later milestones describe the game taking its current form. Keeping those stages distinct makes the long wait easier to understand without inventing a single precise production start day.
The milestones that define the development span
| Period | What was happening | What that date establishes |
|---|---|---|
| 2016 | Rosie Ball and Abi Cooke proposed the magic-school concept during an internal pitch process | The origin of the project idea |
| 2017 | The team discussed prototypes, systems, characters, and the Spellbound working title | Active early development and public discussion |
| 2018 | The project received the name Witchbrook | A naming milestone rather than the start of all work |
| 2019 | The current overhead visual perspective was adopted | A significant change in the game's presentation |
| 2025 | The team explained its simulation and engine change, then reported internal balancing tests | The current world's foundations and later refinement work |
| 2026 | Full-year and end-game testing continued alongside translation, porting, and polishing | Work on the whole experience and launch preparation |
| October 27, 2026 | The January 28, 2027 launch was announced | The current release target |
The concept came before the final title
The game began with an internal process for choosing projects after Starbound. Team members pitched ideas and the company voted. Wargroove was selected as a shorter project, but the idea of a magic-school game also attracted enough interest that the team decided to pursue both.
Rosie Ball and Abi Cooke's 2016 concept did not yet carry the final Witchbrook identity. It established a setting and a direction that could then be developed into systems, characters, and a world. The early project was referred to as Magic School Game and later publicly discussed through the working name Spellbound.
That working name also has a specific history. Before Wargroove had its own title, it had been called Warbound internally. Spellbound followed the same naming joke after Starbound, and the temporary label stuck. It was not a separate released game that later became Witchbrook, nor does the eventual naming date indicate that all development began then.
What existed during the 2017 stage
By 2017, the team was already prototyping several parts of the game: magic, crafting, potion-making, and farming among them. The stated approach was to make those individual activities satisfying before connecting them. This explains why an early version could contain recognizable elements while still being far from a complete release.
The world and characters were also taking shape. At that point, much of the world was described as explorable, and the cast had detailed personalities and surrounding lore. The remaining work was not simply drawing a place to walk around. The activities and situations that would make that place function as a game still required development.
Around nine or ten people were working on Spellbound during the later 2017 discussion. The project was described as early and relatively long-term, with a contemporary estimate of roughly three to four years in total. That estimate belongs to the plans of that period. It was not an announced retail release date or a guarantee that the later, expanded game would be finished on the same timetable.
An early view of the project during its Spellbound stage.
Naming in 2018 did not freeze the design
The move from Project Spellbound to Witchbrook gave the project a public identity. At the time of the naming, no release date had been announced. The distinction matters because people can remember the name reveal as if it were a launch announcement, even though it supplied a title rather than a calendar deadline.
The early concept already contained the appeal of school life, relationships, and an inviting place to inhabit. That continuity explains why older screenshots remain recognizable as part of the same project's history. It does not mean every system described in the early years survived unchanged through later development.
For example, early discussions included possible combat influences and a particular approach to relationship drama. Those statements describe the design being explored then. They are useful for understanding the project as it developed, but they cannot substitute for the present game's systems or turn an old development aspiration into a current feature guarantee.
The current perspective arrived in 2019
The visual direction changed during development. The team placed its adoption of the current overhead perspective in 2019, describing its appeal through the depth and detail possible in a dollhouse-like view. That is a significant milestone in the history of what players now recognize as Witchbrook.
A change of presentation can affect more than the appearance of a single screenshot. The town, buildings, and people have to work together within the chosen view. The later development explanation specifically described the move to a new engine as part of fulfilling the project's increased ambitions, while retaining the larger concepts behind it.
The available milestones do not assign an exact duration to every part of that transition. They do establish that the project evolved after the early public discussions. Treating the final game as merely the 2017 prototype waiting to be released would miss that documented change in direction.
A larger simulation became central to the project
By June 2025, the team explained the world simulation in detail. Mossport's residents had individual appearances, names, homes, and routines, and continued to be tracked away from the player. Seasons changed resources, jobs, clothing, schedules, and the appearance of the town. Traffic added another persistent system to the same place.
The engine supporting this work was Halley. The simulation used a detailed level near the player and a lower-fidelity level elsewhere, retaining important information while avoiding unnecessary animation for things currently out of view. That gives a concrete example of the foundations behind the lived-in town described throughout development.
At this stage, the team described itself as fewer than twenty developers and acknowledged that the game had grown in ambition. The combination of a new engine, changed presentation, and expanded systems was described as a substantial undertaking. This supports a specific explanation for part of the long development: the project being completed had become more involved than its original outline.
The same setting presented through different visual directions.
Internal testing continued beyond having the foundations
The existence of the simulation did not end the work of shaping a full playthrough. By the end of 2025, the team had completed internal playtesting aimed at balance and planned to implement feedback, add content, continue console porting, and refine the overall loop.
The June 2026 update described repeated playtests examining features, balance, and the pacing of the in-game years. The first year could take around forty to fifty hours depending on playstyle in that testing context. Running through a long year more than once was therefore itself a substantial part of the work being described.
Feedback also led to additions such as spells, pedestrian gossip, creatures, resources, animations, and music. These examples show testing influencing what was in the game, rather than serving only as a final check after every creative decision was fixed. They do not establish a separate calendar delay for each addition.
Translation, console work, and end-game refinement in 2026
The August 2026 update reported a final large batch of text going to translators and an internal end-game balancing playtest underway. Console porting, quality assurance, polishing, and bug fixing were continuing at the same time. These were several strands of launch preparation progressing alongside each other.
By September, the final internal playtest was described as wrapping up, with the team working through feedback while localization and console porting continued. Those statements are more specific than a general claim that the game was almost ready. They describe both completed milestones and work still being carried forward.
The team had also explained why it had been cautious about sharing a specific release date. Platform submission, difficult bugs, work with external porting or localization teams, and further feature polish could affect a schedule. Those were examples of possible scheduling factors, not a disclosed list of incidents that had all actually occurred.
Where the long development stands now
The current endpoint of the timeline is the October 27, 2026 announcement of a January 28, 2027 launch. The game remains unreleased, so the full concept-to-release span is still awaiting that planned endpoint. What can already be said is that its history reaches from an internal idea in 2016 through prototypes, naming, a visual and technical evolution, and increasingly complete rounds of testing.
That is the useful answer behind the roughly decade-long description. Witchbrook has not spent the entire period in one unchanged state. Its early identity, the systems supporting its current world, and the work required to refine a lengthy student life belong to different stages of the same project. The documented milestones explain the progression without pretending to measure continuous staff hours or account for every month between announcements.