Skip to content

MSync 2 v1.3.0

Choose a tag to compare

View all tags
@ApertureDevelopment ApertureDevelopment released this 10 Oct 14:23
· 20 commits to master since this release
v1.3.0
264f776
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

The new MSync version brings a lot of features and bugfixes, you can read a list of all changes below.

You can now enable and disable modules in-game without needing to restart the server.

If you have a old MSync settings file you wont get a error anymore, but rather the old file gets updated to the new file format.

As requested with #56 I have improoved the logging of MSync, you can now set log levels using the convar msync_debug which defaults to Errors only. The new log levels are set like this:

0 = Errors only
1 = Errors and Warnings
2 = Errors, Warnings and Info
3 = Errors, Warnings, Debug and Info

The MBSync module now responds to ULX bans, meaning if you ban someone using ulx ban the ban will automatically be added to the MBSync database as a server-group based ban ( Allserver bans have to be made using the MBSync command ) same with ulx unban and ulx banid.

The MSync GUI has been improoved slightly, such as clickable links to the Aperture Development services and showing the current database connection status.

We added a possibility to import and export bans from/to ULX. The command to import bans is msync.mbsync.import [true, if all bans should be bans on all servers] and to expot bans is msync.mbsync.export

Bugfixes:

  • Added 64bit MySQLoo binaries to check if mysqloo is present
  • GUI: Module description is not selectable anymore
  • Modules don't load on the clientside if the database isn't connected
  • GUI: Modules update with enable and disable status immediantly
  • Fixed by default enabled module list
  • Fixed Database error when rank name is too long ( It soft errors now )
Assets 2
Loading