Understanding the Carmine Suit Unlock Documentation
The official documentation provided by the developers of Brigador Killers—specifically a developer log titled "How the carmine suit is unlocked"—serves as the primary source for understanding how player-interactable items function within the game's Secret Alpha build. This document is highly relevant to the keyword "Brigador Killers suits" because it provides a technical breakdown of how specific suit components, such as the Carmine suit, are integrated into the game's map architecture and scripting systems.
By examining this source, players and modders can gain insight into the "ITEM_PICKUP" resource system, which is described as a new addition for Brigador Killers. The information is not merely a surface-level guide but an explanation of the underlying infrastructure that connects map-making tools like SJTiled with the game's engine through Lua scripting. Understanding these mechanics is essential for anyone interested in how the game manages reactivity, state changes, and the progression of unlocking items.
Confirmed Facts Regarding Suit Mechanics
Based on the developer log, the unlocking of the Carmine suit is a multi-step process that relies on the interaction between map objects and the game engine. The following facts are confirmed by the source:
- ITEM_PICKUP Resources: The suit components and the suit itself are classified as "ITEM_PICKUP" resources. These are defined as .json files organized by type.
- SJTiled Integration: The game utilizes SJTiled, a fork of the Tiled map-making tool, to place objects on an object layer.
- Conditional Logic: Objects in the game map use custom properties. Specifically, "disable_if" is used to prevent an object from appearing if it has been unlocked, while "enable_if" is used to ensure an object only appears once a specific state has been met.
- Lua Functionality: State changes are driven by Lua functions, which are self-contained modules of code. When a player interacts with a pickup, the "on_pickup" field in the data editor triggers a specific function.
- The Carmine Suit Process: To unlock the Carmine suit, a player must collect three separate suit parts. Each part is an interactive object. Once these parts are collected, the "UnlockItem" function is triggered.
- State Persistence: The game saves the unlocked status of these items to a local Lua file known as "gvar_data."
- Map Independence: While the parts and the suit can be placed on the same test map for demonstration purposes, the system is designed so that the unlock state is managed by Lua functions separate from the maps themselves. This allows the suit to appear in different locations, such as the "Fort" map, only after the prerequisites are met.
Interpreting the Documented Context
To fully grasp these mechanics, it is necessary to understand how the bridge between the map-making tool (SJTiled) and the game engine functions. The "scripting object" placed in SJTiled acts as a placeholder. When the map is exported as a .json file, the game engine reads the asset path and the custom properties assigned to that object.
For the Carmine suit, the process is sequential. The suit parts are configured with a "disable_if" property set to "IS_UNLOCKED". This ensures that once the player picks up a part, it disappears from the game world. Simultaneously, the "UnlockItem" function updates the global variable state in the "gvar_data" file. When the player later visits a map where the suit is located, the engine checks for the "enable_if" condition. If the "gvar_data" reflects that all three parts have been successfully collected and unlocked, the game renders the suit for the player.
This system represents a significant shift from the previous game, Brigador, where the unlock system was criticized for being disconnected from the active gameplay. By tying the availability of items to specific map-based interactions, the developers aim to provide players with tangible reasons to revisit locations.
Qualifications and Development Status
It is critical to note that the developer log explicitly states that the systems described are a "work in progress." The developers emphasize that the information provided is "not necessarily indicative of the final product." This qualification is vital for anyone analyzing the technical details of Brigador Killers. While the logic involving "ITEM_PICKUP" resources and Lua functions is documented as the current method, the developers reserve the right to change these systems before the final release.
Furthermore, the documentation mentions that these systems were being tested in the "Secret Alpha build." Therefore, the specific file paths (such as assets/data/pickups/kipple/pkp_braintape_01.json) and the specific Lua function names (such as "UnlockTape" or "UnlockItem") are snapshots of the development environment at the time of the post, dated April 24, 2024. Readers should treat these technical details as examples of the development methodology rather than rigid, finalized game code that will remain unchanged in the finished title.
Source Limitations and Missing Information
The supplied source material does not provide exhaustive information regarding every suit that may be included in the final version of Brigador Killers. It focuses exclusively on the Carmine suit as a case study for the game's new unlock system. Consequently, the following information is not established:
- Total Number of Suits: The document does not list or describe any other suits beyond the Carmine suit components.
- Final Gameplay Stats: There is no mention of the combat statistics, performance values, or specific attributes of the Carmine suit. The document focuses on the mechanics of unlocking the item, not its function or power level within the game's combat system.
- Platform Compatibility: No information is provided regarding which platforms the game will support or how the UI/UX will handle suit selection on different hardware.
- Release Timeline: The document does not offer any information regarding the game's release date or final development roadmap.
Readers should be aware that any details concerning the effectiveness of the suit in combat or the existence of other specific character outfits are currently unconfirmed by the official source.
Revisiting Official Documentation
For those seeking the most up-to-date information or further clarification on the development of Brigador Killers, the primary hub for information is the official itch.io page for the game. The specific developer log discussed here can be found at the following URL: https://stellar-jockeys.itch.io/brigadorkillers/devlog/708973/how-the-carmine-suit-is-unlocked.
This page remains the most reliable source for official updates. As the development progresses, the developers may publish additional logs that explain changes to the "gvar" (global variable) system, the refinement of Lua functions, or the introduction of new narrative-driven "storylets" that affect the game state. Monitoring this specific developer log feed is the recommended way to distinguish between the temporary mechanisms of the alpha build and the finalized features of the full game.
Related guides
For related source-limited coverage, see Brigador Killers weapons and Brigador Killers guns.
Source limits
The information contained in this article is strictly limited to the content provided in the official developer log dated April 24, 2024. Any mention of game systems, such as the use of Lua or SJTiled, is derived solely from the provided documentation. No external information, community speculation, or assumed knowledge about Brigador Killers has been included. The article does not make claims about the final state of the game, as the source explicitly identifies the discussed systems as a "work in progress." All references to technical processes, such as the "disable_if" or "enable_if" properties, are presented as they were described in the original text, and no conclusions have been drawn regarding features or mechanics not explicitly mentioned in the source material. Readers are encouraged to view the official developer log for any future updates or corrections to the information presented herein.