Releases: Zingabopp/BeatSaberModdingTools
Releases · Zingabopp/BeatSaberModdingTools
BeatSaberModdingTools 0.9.5
- Fixed 'Index out of bounds' error when opening settings window
BeatSaberModdingTools 0.9.4
- Project templates have been removed from this extension
- Templates are available separately on the Visual Studio Marketplace
- Compatible with Visual Studio 2019 and 2022
Beat Saber Modding Tools 0.9.2
Recommended for VS2019: Download and run BeatSaberModdingTools.vsix
(you don't need the zips if you're installing the extension, they are included)
Read the Wiki: https://github.com/Zingabopp/BeatSaberModdingTools/wiki
- Revamped build targets
BuildTargets.targets
replaced withDirectory.Build.targets
which is automatically imported by the build system (no need to explicitly import it in thecsproj
file).- Now uses the BeatSaberModdingTools.Tasks nuget package to provide the build tasks.
- Templates can now be built in a CI environment fairly easily.
- Updated templates (and they specify BSIPA as a dependency by default 😄)
- Improved
Reference Manager
- Ability to specify how to reference Beat Saber references (
BeatSaberDir
(default),BeatSaberReferences
(better CI compatibility), andNone
(to use the full path). - Added
Game
filter
- Ability to specify how to reference Beat Saber references (
- Partial support for SDK-style projects (
Reference Manager
is unable to set theHintPath
, so all added references will use absolute paths). - Bug fixes
Beat Saber Modding Tools 0.8.1
- Added Bare template (Thanks @Auros )
- Refined BuildTargets.targets
- Now will copy output to the
Plugins
folder. - Copies to
IPA\Pending\Plugins
if Beat Saber is running.
- Now will copy output to the
- Added BSIPA Manifest ItemTemplate
Beat Saber Modding Tools 0.8.0
- Updated with templates for BSIPA4 (Beat Saber 1.8.0)
- Template tweaks and fixes
Templates for BSIPA4 (RC3)
- Updated for latest version of BSIPA4
Templates for BSIPA4 (RC2)
- Templates for BSIPA 4 mods
- These must be placed into "%userprofile%\Documents\Visual Studio 2019\Templates\ProjectTemplates\Visual C#"
- They should be deleted if you install Beat Saber Modding Tools once it includes the BSIPA4 templates.
- These templates can coexist with the BSIPA3 templates.
Fixes:
- Removed Harmony using from Disableable template.
- Fixed Core and Disableable MonoBehaviour singleton.
Templates for BSIPA4
- Templates for BSIPA 4 mods
- These must be placed into "%userprofile%\Documents\Visual Studio 2019\Templates\ProjectTemplates\Visual C#"
- They should be deleted if you install Beat Saber Modding Tools once it includes the BSIPA4 templates.
- These templates can coexist with the BSIPA3 templates.
Beat Saber Modding Tools 0.7.4
- Small fix so the BSML file template makes it an EmbeddedResource on creation.
Beat Saber Modding Tools 0.7.3
- Added BSML ItemTemplates (Add > New Item > Beat Saber)
- Will now set both BeatSaberDir and ReferencePaths in the .user file to account for projects that have mixed reference path styles.
- Split the custom MSBuild Targets and Tasks into their own file for easier maintainability.
- Fixed bug where the Beat Saber install path setting wasn't being saved if a location wasn't auto-detected.
- Other bug fixes.
Please create a GitHub issue or ping me on the BSMG Discord @Zingabopp#6764 if you find any bugs or issues