Understanding the Narrative Framework for Brigador Killers Missions
When researching the structure of Brigador Killers missions, the primary official resource is the developer log titled "LET'S LEARN ABOUT STORYLETS," published by Stellar Jockeys on September 29, 2023. This document is essential for understanding how the game manages mission design, player interaction, and narrative progression. While the term "missions" is often used broadly by players to describe objectives or levels, the developers focus specifically on the underlying systems that make these experiences possible.
The relevance of this document to the keyword "Brigador Killers missions" lies in its explanation of how the game moves away from the rigid, hard-coded objectives found in the original Brigador. Instead of relying on a linear progression system where players spend money in a menu outside of the action, the developers are introducing elements of progression that occur directly within the map. This shift in design philosophy fundamentally changes how missions are constructed, played, and experienced. By examining this source, players and modders can gain insight into the technical architecture that supports the game’s world, dialogue, and mission-based reactivity.
Explicitly Confirmed Facts Regarding Mission Systems
The official documentation confirms several key technical components that define how missions function in Brigador Killers. The game employs an overarching narrative architecture composed of four distinct, overlapping systems:
- Storylets: These are reactive chunks of content that respond to a player’s specific decisions and behaviors.
- Predicates: These serve as the conditions that must be met for a specific storylet to "play." They allow the game to check if a player has completed a specific action, such as speaking to a particular NPC or finishing a prior objective.
- Gvars (Global Variables): These variables track the state of the game world across different levels and missions.
- Lua Functions: A library of functions used to modify the game state, such as spawning units, setting or completing objectives, triggering sound cues, or pausing the game.
Beyond these four systems, the developers explicitly mention the use of "mvars" (map variables). When a level is loaded, the game engine evaluates both global variables and map-specific variables to determine the state of the environment. This allows designers to populate a map with various entities—such as building props or enemy squads—based on the current "quality" state of the game, rather than requiring the creation of multiple, separate versions of the same map to account for different outcomes.
Reading the Narrative Context and Design Philosophy
To understand the scope of mission design in Brigador Killers, one must view these systems through the lens of player reactivity. The developers, Stellar Jockeys, designed these tools to solve the criticism that the original Brigador lacked depth beyond its core combat loop. By implementing a system of storylets and qualities, the developers intend to provide a more flexible, reactive environment.
In this context, a "mission" is not merely a static list of tasks to be completed in a specific order. Instead, the game treats the mission space as a story-world where characters and environments react to the player's presence and actions. For instance, if a player is meant to steal intel on a "Betushka," the system tracks not only if the player succeeds, but also how they approach the task. NPCs within the mission are designed to respond to these "stolen Betushka" qualities.
This design extends to the physical presence of NPCs within the mission space. Because the system is reactive, a player is not forced to interact with specific NPCs to progress. If a player chooses to ignore a character, or if that character is killed or frightened away by combat or explosions before an interaction can occur, the narrative system is designed to account for those absences. This creates a more dynamic experience where the mission outcome is influenced by the player's immediate, tactical decisions rather than a pre-determined, linear path.
Qualifications, Timing, and Development Status
It is critical for readers to recognize that the information provided in the source material is explicitly identified as a "work in progress." The developers at Stellar Jockeys note that the narrative systems, the user interface elements, and specifically the debug panel are subject to change. The documentation serves as a glimpse into the development process during the creation of these tools, rather than a finalized manual for a released feature set.
The documentation also specifies the tools used in this process. The developers utilize the open-source program Tiled for map creation, where they assign names to NPCs in their properties. This labeling is what allows the storylets system to identify specific speakers, even when multiple instances of the same NPC type are placed on a map. Additionally, the developers use the imnodes extension to the Dear IMGUI library for their node graph editor, which serves as the visual interface for building dialogue storylets.
Furthermore, the developers clarify the nature of the Lua integration. While they are using Lua, they are not providing a full-blown, unrestricted programming environment, as this would pose security risks. Instead, they have implemented a system similar to Bethesda’s "Papyrus" scripting language—a set of predefined functions available to designers and modders that limits what can be modified while still providing significant control over the game state.
What the Source Does Not Establish
While the provided documentation offers a deep dive into the technical systems behind Brigador Killers, it is important to clarify what it does not establish. Specifically, the source does not provide:
- A List of Missions: There is no catalog, index, or description of specific missions that will be available in the final game.
- Gameplay Walkthroughs: The material does not offer advice on how to complete specific objectives, how to pilot mechs, or how to survive combat encounters.
- Release Dates or Platforms: The text does not confirm when the game will be released or on which platforms it will be available.
- System Requirements: There is no information regarding the hardware needed to run the game.
- Price or Merchandising: While the text mentions a painting contest and future merchandise, it does not provide pricing or availability details for the game itself.
- Finalized Mechanics: Because the systems are described as a "work in progress," the specific implementation of predicates, gvars, or Lua functions may differ significantly from the final product.
Readers should avoid assuming that the examples provided in the developer log—such as "Tester 1" or the specific dialogue snippets regarding "Norman"—will appear in the final game. These are presented as functional examples of the tools being built, not as confirmed narrative content.
Revisiting Official Sources for Future Confirmation
Because the development of Brigador Killers is an iterative process, readers who wish to stay informed about the evolution of these systems should monitor the official Stellar Jockeys communication channels. The primary source for the information discussed here is their official itch.io devlog page, which can be found at: https://stellar-jockeys.itch.io/brigadorkillers/devlog/613054/lets-learn-about-storylets.
Official development logs are the most reliable method for confirming details about mission structures, narrative tools, and general game design as development continues. Any information regarding "missions" in Brigador Killers should be cross-referenced with these official updates to ensure it reflects the latest state of the project.
Related guides
For related source-limited coverage, see Brigador Killers story and Brigador Killers characters.
Source limits
This article is based strictly on the content of the developer log "LET'S LEARN ABOUT STORYLETS," published by Stellar Jockeys on September 29, 2023. No external sources, player forums, community speculations, or prior knowledge of the Brigador franchise have been used to supplement or verify the claims made herein. All technical descriptions, including the use of Lua, Tiled, and the narrative systems (storylets, predicates, and variables), are limited to the specific context provided by the developers in the cited document. Any information not explicitly found in this source, such as specific mission names, total mission counts, or finalized gameplay mechanics, is not provided because it is absent from the official record. This text does not constitute a comprehensive guide to playing the game but rather an analysis of the underlying mission-design architecture as described by the developers at a specific point in time.