Added advanced setup script, and some other tweaks: #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- X2PG support is now integrated into X2MBC and can be enabled by toggling a flag in build.ps1. X2PG must still be installed to do anything, though. - X2MBC can now pick the Highlander up from the X2EMPT_HIGHLANDER_FOLDER environment variable, in addition to the previously documented options. - The advanced setup script can configure X2MBC to: - Build against the Highlander from GitHub (also initializes Git), or from a local copy. The local copy may or may not be configured to use X2EMPT_HIGHLANDER_FOLDER. - Use X2PG verification. - Cook the mod. - Build against any other mod of the user's choosing. - Proofread the readme a bit, cleaning up typos and punching up the grammar.
DaloLorn
commented
Nov 11, 2025
DaloLorn
commented
Nov 11, 2025
- Fixed my argument checks. - Removed defective ELSE-IF constructs in favor of GOTOs. *grumbles about batch scripting* - Git automation no longer picks up the setup scripts or the raw X2MBC script.
… the Highlander from GitHub. This means you no longer need to manually set up Git if you're building against a local Highlander (e.g. from environment variables!).
- Now properly finishes the initial commit. - No longer crashes halfway through because the scripts were deleted during execution.
…lessly stolen from) the LWotC repo.
…so added a reference to the advanced setup to ReadMe.txt.
- Fixed an issue where the advanced setup was no longer correctly passing parameters to regular setup. - Fixed an issue where the FART placeholders in the VSCode workspace weren't being properly cleared. - Fixed an issue where the VSCode workspace wouldn't know where the SDK source folder was, because you can't read environment variables in a workspace definition. (This also affected workspaces trying to grab the Highlander from environment. Fixed that too.) - Added optional SDK/game folder detection steps to advanced setup.
…figured for the build automation and VSCode workspace.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
X2EMPT_HIGHLANDER_FOLDERenvironment variable, in addition to the previously documented options.X2EMPT_HIGHLANDER_FOLDERas an alternative to being hardcoded into the build script.