MSync v1.4.0 - SQL Update

With MSync 1.4.0 we are implementing various bugfixes and changes.

With this update we solved issue #75 where some of the database queries were incompatible to MySQL 8.0. The new SQL syntax is cross compatible between MariaDB and MySQL 8.

We also changed the ban behaviour of MBSync, now when editing a ban, the ban time of the edit always updates the ban length. This means when I edit a 2 hour ban 1 hour after creating it, the ban will be edited to be 3 hours long to last 2 hours since the edit.

Some minor fixes include:

• Fix indexing nil value when removing a rank ( MRSync )
• Update code style according to GLuaLint

Server Freeze

This release fixes an issue with the server freezing when no database is connected and a user attempts to join the game ( described in #72 )

MSync v1.3.1

Small bugfix update. Fixes #68 as well as some other not-reported bugs ( can be viewed at #69 )

Introduces MSyncModuleLoaded hook to load module data only after the module queries have finished successfully

MSync 2 v1.3.0

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 )

Feature Update and Bugfix

We added a feature to MSync to allow the addition of new users which never joined before. That way we can add ranks to users, ban users and do a lot more, without the requirement of said user already existing in our database.

Additionally we fixed some bugs that caused the MBSync console commands to not work, only issue is a ULX/ULib bug that happens when the console command msync.mbsync.banPlayer gets called without a player provided. This is sadly not fixable on our side without modifying ULX, which is what we wanted to avoid.

This is the error:

[ERROR] addons/ulib/lua/ulib/shared/player.lua:121: Tried to use a NULL entity!
  1. indexFn - [C]:-1
   2. getUniqueIDForPlayer - addons/ulib/lua/ulib/shared/player.lua:121
    3. parseAndValidate - addons/ulib/lua/ulib/shared/commands.lua:515
     4. __fn - addons/ulib/lua/ulib/shared/commands.lua:916
      5. execute - addons/ulib/lua/ulib/shared/commands.lua:1323
       6. unknown - addons/ulib/lua/ulib/shared/commands.lua:1351
        7. unknown - lua/includes/modules/concommand.lua:54

Please do not open bug reports regarding this error, we are aware of it but we sadly cant fix it as of now.

Feature update and Bugfix

We added a feature to allow real-time synchronization of ranks using MRSync. When you type the command or use other ways of adding someone to a rank using ULX, MRSync will instantly push changes to the database. That way we are able to prevent data loss when the server has been closed unexpectedly ( crashed ).

Additionally we fixed the SUP checks for the MRSync admin GUI, it now no longer is possible to add ranks with a leading whitespace, a whitespace at the ending or just containing whitespaces. It also is no longer possible to add empty fields as ranks to the list. Furthermore we fixed a bug causing the settings to not be avaiable at the client when he opens the MSync GUI.

Related: #37 #36

Bugfix release v1.0.3

This bugfix release implements a bugfix for the issues described in #31 and #32

Changes:

• Fixed a bug in MRSync causing it to be unable to synchronize ranks
• Fixed a bug in the database creation that caused the allservers group to not be created, when the user modified the server group beforehand

Bugfix #25

Fixed a bug described in #25

The bug caused MSync to be unable to connect to Database servers running on different ports then 3306.

Bugfix

Fixed a bug that caused a Lua error when opening the MSync menu with disabled modules. Bugfix for #22

Official MSync Release

Today is finally the day, that we are releasing MSync 2 to the Workshop

It took us almost two years but now we are finally able to release the successor of MSync. Version two has a lot of changes and is [b]not[/b] backwards compatible, because of the new database structure.

The new version of MSync brings a lot of advantages, for example the new module system which allows to easily enable and disable modules. This system allows us to easily add additional MSync 2 features without big re-coding. Additionally everyone is now able to develop modules for MSync 2, the only thing to keep in mind is the structure of the modules. for that purpose, we have provided a SampleModule to allow you to easily learn and understand our syntax as well as our API.

Additionally we provided a new rank synchronization module, as well as a new ban synchronization module. These modules have been re-coded from scratch, to fix old bugs and to improove the general user experience. These modules are shipped with MSync 2 by default. In the future, we planned to develop more modules to extend the functionalities. More informations regarding planned modules are avaiable on GitHub and on our Workshop page.

We also want to announce the end-of-life of MSync 1. MSync 1 won't recieve any future updates or support by us. Please note that due to the difference between MSync 1 and MSync 2, there currently is no possibility to import the data from MSync 1 into MSync 2. We plan to release a script for that very soon. We are sorry for any inconvenience.

The addon is avaiable at the workshop here:
https://steamcommunity.com/sharedfiles/filedetails/?id=1636008512
as well as on GitHub:
https://github.com/Aperture-Development/MSync-2

Have a nice day
~Maximilian Grüttemeier