Skip to content

Releases: MolotovCherry/Yet-Another-BG3-Native-Mod-Loader

v0.2.0 - Major update

15 Dec 20:54
68fc326
Compare
Choose a tag to compare

Major rewrite

The entire codebase underwent a major rewrite, optimizing performance, user friendliness, and improving overall stability.

Debug profile problems are now a thing of the past

That's right! And that's because the previous mechanism of using launchers is now deprecated! A new, more efficient and reliable system takes its place.

Watcher Introduced

  • A new watcher binary has been introduced to replace the deprecated launchers.
  • The watcher binary runs in the background, seamlessly patching the game process whenever it starts.
  • You can exit the watcher by going to the system tray, right clicking on the mod loader icon, and clicking "Quit"

Injector Tool for Non-Persistent Patching

  • For users who prefer not to have a persistent program running in the background, the one-time-use injector tool remains available.
  • When the injector tool is opened, it will either wait 10 seconds for the game to launch or, if the game is already running, it will promptly patch it. If 10 seconds have passed, then it will timeout with an error.

Steam and GoG are both compatible

This is because we are no longer acting as a launcher. It's easy to patch the game process, no matter what store you bought your game from. Just start your game up as you normally would do, and the tools take care of the rest!


Note: The tools probably won't see a process if it requires greater permission access than the user it was executed under. For example, if you started your game as admin, but the watcher only as your user. This is a limitation of the winapi. If you need to run your game as admin, then run the tool as admin also.

Full Changelog: v0.1.3...v0.2.0

v0.1.3 - New injector tool

09 Dec 19:48
adef5ed
Compare
Choose a tag to compare

Added new injector tool which - instead of launching the game and injecting - will simply inject into an already running game instance.

It should ONLY be used on a game instance which has not yet loaded any native mods into it. And it should ONLY be used once, BEFORE loading any saves. Plugins generally expect that they are already loaded into the game on process startup, so it should be done as soon as possible.

Follow those instructions carefully. I am not responsible if something bad happens to your game (though it'll probably be fine even if you don't do it on process startup)

What's Changed

Full Changelog: v0.1.2...v0.1.3

v0.1.2-beta2

02 Nov 22:31
d1ef776
Compare
Choose a tag to compare

Main changes

  • Change config from json to toml. This will make it easier for users to use/configure (you will need to migrate your settings over). Most notably, file paths don't need a "\\" anymore, which was very troublesome for configuring. E.g. Instead of c:\\my\\path, it is now c:\my\path as you would expect
    • Run the launcher once, it'll generate the toml file for you, and you can re-edit it again if you need to
  • Gave common errors easy to read error messages to reduce user confusion when an error occurs
  • Fixed report url to point to correct repo
  • Added plugin specific logging (name and plugin version) if that plugin was compiled with bg3 plugin lib
  • Solved issue where if plugin contained non-ascii characters anywhere in the filepath, it could fail to load. Any unicode works now!

What's Changed

New Contributors

Full Changelog: v0.1.1...v0.1.2

v0.1.1-beta1

09 Oct 15:55
36ec0a0
Compare
Choose a tag to compare

Initial beta release of the mod loader