Brigand Oaxaca Beginner’s Modding Guide

If you’re interested in modding stories or creating your own narratives using the Brigand Scripting Language (BSL), this guide provides valuable information. While basic modding can be achieved by using the GUI editor accessed through the F1 key, a deeper level of customization requires proficiency in BSL. This powerful scripting language allows you to craft unique items, Fähigkeiten, dialogues, AI behaviors, und mehr. BSL commands can be utilized through the F2 command prompt or within *.BSL scripts, which can be conveniently edited using software like Notepad.

Erste Schritte

To gain a solid understanding of BSL, it is recommended to refer to the Builder’s Manual, which offers comprehensive coverage of the language’s fundamentals. Zusätzlich, the Extras DLC package includes a tutorial story named MOD TUTOR, which further explores BSL concepts. It is advisable to play through this tutorial story before diving into modding endeavors. Jedoch, there are certain aspects not addressed in either of these resources. This guide aims to fill those gaps and will continue to expand based on specific requests from modding enthusiasts.

Modifying the Original Story

In order to modify the BRIGAND – OAXACA story, you cannot directly overwrite it. Stattdessen, you must change the story’s name using either the F1 editor or the F2 command prompt. Verwenden Sie den Befehl „storyName=???“ und speichern Sie die Änderungen. Nächste, you’ll need to duplicate the Assets folder of BRIGAND – OAXACA and rename it to match your new story’s name. Indem Sie dies tun, all the scripts will remain intact. Jetzt, you can freely customize the scripts and resources within your mod by making modifications to the Assets folder of your newly renamed story. If a file is missing in your story’s assets folder, the game will default to using the files from the DEFAULT Assets folder.

Creating a New Story

To start an entirely new story from scratch, use the F2 command prompt and type „newStory=???“ (replace the question marks with your desired story name). If you choose not to create a new folder with your story’s name, it will automatically utilize the assets from the DEFAULT folder.

Importing/Exporting Models

Models are typically saved as *.X files, but you have the option to convert them to *.3DS format using the DBO Converter located in the „Stuff\Programs Redist“ Ordner (requires the Extras DLC). Although this conversion can enhance loading speed between maps, it is not mandatory. The original *.X model files can be found in the „Stuff\Objects X“ Ordner (requires the Extras DLC).

Most modeling software supports the import and export of *.X model files. For UV mapping, Wings3D is a recommended tool.

Animating Characters

For objects categorized as „sentient“ (refer to the Builder’s Manual), their animations are stored in five separate X files, each representing a different animation. These animations include idle, Angriff, fall, verletzt, und gehen. The idle animation is named after the object’s tag/folder (z.B., android.dbo or android.x). Remember to keep each animation in a separate file. The source code will combine these animations during gameplay.

While I haven’t personally animated my own models, Quadrajet has shared the following instructions: „Ich benutze Fragmotion to import the .X files and edit the animations, export the animated objects as a .Ms3d file. Then I import that file into Milkshape3D, and finally export each range of keyframes into Brigand.“ Hoffentlich, this guidance proves helpful.

Modifying Basics (Fähigkeiten, usw.)

To alter object properties, edit the INI script within the respective object’s folder located in your game’s assets folder. Keep in mind that changes to the INI script will not affect objects already loaded within the story. You can utilize the „resetStats“ Befehl (refer to the Builder’s Manual) to reload the INI scripts for all objects within a specific tag/folder.

If you wish to change the names of skills, Statusffekte, Fähigkeiten, und mehr, navigate to the globals.bsl script within your story’s Assets folder. Jedoch, remember to modify every instance where these elements are referenced in the scripts. To facilitate this process, you can use a tool like Notepad++ to find and replace skill names throughout all the *.BSL files within your story’s Assets folder. This is the approach used by the NIGHTMARE (ES) story translator to translate skill names effectively.