Skip to content

Releases: voidpointer0x00/VoidWhitelist

Bug fixes update

10 Nov 14:18
Compare
Choose a tag to compare
Bug fixes update Pre-release
Pre-release
  • /wh remove command now actually saves whitelist changes;
  • fixed "UnsupportedOperationException: JsonNull" exception for non-temporal VwPlayer entities;
  • fixed "Plugin attempted to register task while disabled" issue.

Full Changelog: v0.4.0...v0.4.1

Architecture update, preparing to add database support

31 Oct 12:32
Compare
Choose a tag to compare

This version changes the format of whitelist.json file, it is not compatible to old builds and does not automatically convert it.
Previous format:

{"player_no1": 123456789, "player_no2": 123456789}

New format:

{
  ["name": "player_no1", "expiresAt": 123456789],
  ["name": "player_no2", "expiresAt": 123456789]
}

It's due to a new architectural decision that the plugin should manage whitelisted player objects, not just nicknames and dates.

Also, now after a player is temporally added to the whitelist, a kick task will be scheduled for this player and they will be kicked as soon as the time in the whitelist expires.

The JSON storage support update

28 Sep 12:27
Compare
Choose a tag to compare
Pre-release

The version was upgraded to 0.3.0: 0.2.0 was a locale update, this one is JSON update.

This update introduced a StorageMethod class that is now responsible for all the current and future storage implementations — serialization, JSON and further SQL storage.

Implementations are provided through the StorageFactory class.

The JSON storage implementation lies in the storage.json package and it's rather simple implementation using the provided Guava json library.

The new configuration property was added to the config.yml file that is now responsible for the storage method specification.

# default implementations allowed: serial, json
storage-method: json

Localization update

23 Sep 12:00
Compare
Choose a tag to compare
Localization update Pre-release
Pre-release

This small release adds locale features:

  • specify the language property in config.yml (provided translations: en, ru);
  • edit locale for multiple languages in locale-{language}.yml files;
  • locales for English and Russian languages are provided by default.

Now your config.yml file should look like

language: en

whitelist:
  enabled: false

After enabling the plugin should create a locale-{language}.yml file in the plugin's directory (server/plugins/VoidWhitelist/). If en or ru languages are set default files will be created otherwise, the plugin will create a new file with default translation (en), but a new name so that you can translate it on your own.

Public build for general testing and feature requests.

09 Aug 15:59
Compare
Choose a tag to compare

Implemented whitelist key features:

  • the ability to add to a whitelist temporarily or permanently using /whitelist add Player 1d2m command, where time (1d2m) is optional;
  • the ability to turn on/off the whitelist system on a server using the /whitelist on|off|enable|disable command;
  • the ability to check if is there a Player in the whitelist using the /whitelist is-whitelisted|iswhitelisted Player command.

Expected behavior:

  • whenever whitelist is enabled and there are players who are not on the whitelist, they must be kicked from the server;
  • whenever the player's time expires, they must be kicked;
  • not whitelisted players must not be kicked or disallowed to join when the whitelist is not enabled.

MD5 checksum: 762f27241a225bb545f82663c8fe287c VoidWhitelist-0.1.0.jar

Perhaps, I missed something obvious above, but it should be clear how the plugin should work from all above.