Skip to content

Releases: TheCheatsrichter/Gw2_Launchbuddy

Gw2 Launchbuddy V2.3.5 Hotfixes

29 May 12:35
Compare
Choose a tag to compare

Additional hotfixes from the loginfile code overhaul.

  • Fixed a bug when String.Copy tried to copy a null hash
  • Fixed a crash when the refrence to the game process was lost

Gw2 Launchbuddy V2.3.4 Hotfixes

28 May 11:25
Compare
Choose a tag to compare

A few hotfixes reported by the first 2.3.3 users. Keep the crash reports coming!:

  • Fixed a crash when the process exited before closing
  • Fixed a bug when the MD5 Hash was calculated from empty loginfiles.

Gw2 Launchbuddy V2.3.3

28 May 10:46
Compare
Choose a tag to compare

Further hotfixes coming soon!

This updates includes a total Loginfilemanager overhaul. On Tuesday the 26th a big number of Launchbuddy users had some serious game updating problems. Loginfilles got corrupted did not successfully update or did overwritte one another. With this new version the backend code responsible for this function has been written completly new. This nowshould increase stability for thoes who were plagued by update / swapping loginfile problems. In addition some additional crashfixes have been made.

  • LoginfileManager code overhaul. (swapping / updating / creating / repairing loginfiles should now be more stable for the majority of users)
  • Improved CrashLogReporter to further narrow down remaining loginfile problems
  • Loginfiller (loginfile recreation) crash fixed when game client was closed / crashed.
  • Fixed a crash when the AddIcon dialog was canceled or an invalid path was given
  • Exception handling when the VersionSwitcher did not have permission to delete the old LB .exe file

Full list of changes:
2.3.2...2.3.3

Gw2 Launchbuddy V2.3.2

28 Apr 17:54
Compare
Choose a tag to compare
  • Minimized unnecessary file copy operations when swapping the login files. Depending on your local.dat file size launching clients should now be faster and more stable.
  • Fixed some timing issues when gameclient is launched from a HDD. ("xy is used by another Process")
  • Fixed an error when updating loginfiles on a target machine with HDD
  • Added buttons to remove Blish/Taco paths
  • Fixed an GFX file import error when gw2 was never initially launched on the target machine
  • Added filelock wait when the GFX file is restored to the default one to minimize fileaccess crashes

Full list of changes:
2.3.1...2.3.2

Gw2 Launchbuddy V2.3.1

12 Apr 19:56
Compare
Choose a tag to compare

This version features some bugfixes.

Patchnotes:

  • Fixed game updates which happened when the Gw2 API client version was not upto date yet.

  • Added workaround for a bug which was caused by the gw2 game client not updating its build number when run with -image. (always updated on startup)

  • Added FileLockWait and FileHandleClose function to reduce loginfile swap errors. Aka "An error occured while swaping the Login file."

  • Only display Add Blish/Taco button when game is running

  • Updated Crashreporter

Full list of changes:
2.3.0...2.3.1

Gw2 Launchbuddy V2.3.0

12 Feb 16:38
Compare
Choose a tag to compare
  • Added BlishHUD support by TheNasbit
  • Added option to disable Launchbuddy versioncheck by cyantheum
  • Fixed an TacO mumblelink error which caused errors on the first launched account
  • GameInstace UI now automatically starts when an active client is detected
  • Fixed a bug that caused crashed clients to be shown as active

File is allready send to microsoft for reviewing to keep antivirus false positives at bay.

Full list of changes:
2.2.1...2.3.0

Gw2 Launchbuddy V2.2.1

04 Sep 17:51
Compare
Choose a tag to compare
  • Updating Fody to 5.0 to reduce AV false positives

Previously: https://www.virustotal.com/gui/file/60b35b65e151a7113697c66c346a3464aabcae8b79451c4bd9dd1759caa9b298/detection

After Fody update: https://www.virustotal.com/gui/file/af14508eecaa20d0629b84c4f434ea3385e52e3a02c8eb217c63d7c3897205fb/detection

  • Only use custom mumblelink on multiboxed clients to further support software which does not support multiboxed mumble links
  • Version Labeling Change + Fixing Window Title
  • SelectedOnly Acc Update
  • Dispose of old settings. Using custom XML file in Appdata. Should resolve Launchbuddy startup crashes and crahes since windows update.

File is allready submitted to microsoft for reviewing. This hopefully removes the Antivirus false positive on their side. Fingers crossed!

Gw2 Launchbuddy V2.2.0

31 May 18:05
Compare
Choose a tag to compare

Well who doesn't like tacos? With the recent changes to the Gw2 client it is now possible to seperate each clients Mumble link! This has allready been adapted by BoyC the creator of Gw2 TacO and now is natively supported by Launchbuddy. Check out the new TacO tab to set everything up.

  • Added native TacO multiboxing support.
  • Fixed a bug when plugins UI were set before them being initialized.
  • External assemblies are now weaved with fody again, as the some of the AV false positives have been resolved.
  • Added Commandline support, currently non functional. Likely will be added by KairuByte in the future.

Full list of changes:
2.1.5...2.2.0

Gw2 Launchbuddy V2.1.5

20 May 22:00
Compare
Choose a tag to compare
Pre-release
  • Fixed Crashanalyser logfile read error
  • Revert all Loginfile logic back to release 1.9.3
  • Fixed Paypal support button
  • Added WindowHandle refresh functions to compensate gameclient process switch

Gw2 Launchbuddy V2.1.3

08 May 00:32
Compare
Choose a tag to compare
Pre-release

If you have issues with this version please use version 1.9.3.
Bugfixes and some loginfile changes to make 2.#.# versions accessable for more people:

  • Fixed which kept loginfiles in a update loop when compiling Launchbuddy in debug mode. (by jacob-keller)
  • Added a option to enable/disable loginfile autoupdates. (by DeltraEcho)
  • Fixed a bug when the instance manager GUI was closed while an account was starting
  • Reverted loginfile timing methods to better resemble timings of version 1.9.3.
  • Loginfile swapping will no try to swap with admin rights first and then try to use developer options if it does not succeed. (was the other way around in 2.1.2)