Commit Graph

122 Commits

Author SHA1 Message Date
ME1312
56f8d3dfba Remove package.xml requirement for SubServers.Host 2018-02-19 17:59:51 -05:00
ME1312
92c649eabe Make Name field optional for SubServers.Client
SubServers.Bungee can now link servers to subdata clients via connection address and port number.

Since this still has the chance to fail, the `Name` field will appear if no servers were found this way, and will be used the same as before. SubCreator made servers will still have the `Name` value present and filled out for assurance.
2018-01-29 01:04:36 -05:00
ME1312
754b418e7d Register SubServers.Sync Proxies to name for API access 2018-01-22 10:01:33 -05:00
ME1312
cc1f86c4d1 Update Dependancies 2018-01-21 21:49:18 -05:00
ME1312
e5ad3f55d2 Allow PacketIn to accept multiple oncoming packet versions 2018-01-13 16:22:13 -05:00
ME1312
b72103c0f0 Make Server API use existing fields from BungeeServerInfo 2018-01-12 16:56:22 -05:00
ME1312
7a5eac83fd Update Libraries 2018-01-05 17:30:01 -05:00
ME1312
00d56c1167 Add the SubData Cipher API
This adds a simplistic API for the encryption/decryption of incoming/outgoing packets, replacing the old Encryption enum.
2018-01-05 15:37:23 -05:00
ME1312
562072df3f Lang API Rewrite // Add TabCompletes to Sync 2018-01-02 17:29:25 -05:00
ME1312
b3a40311a1 Simplify YAMLSection methods 2017-12-21 18:37:39 -05:00
ME1312
6bb7b1ef17 Allow YAMLSection to be converted to Map<String, ?> 2017-12-21 11:02:47 -05:00
ME1312
c9afe48674 Correct config loading issue
This solves a 'file in use' error on windows
2017-12-14 19:50:39 -05:00
ME1312
36ee42a1ab Implement the proposed TabValidator API
This is how SubServers will implement the Validator API that I suggested. I had to make some assumptions though (like how I don't expect BungeeCord's api to have a setTabValidator() method).
2017-12-13 12:29:50 -05:00
ME1312
91ca559e4a Host & Server objects are now signed (prevents desyncs across apps) 2017-12-09 19:30:06 -05:00
ME1312
0bf5f16e09 /sub reload can now perform soft reloads
/sub reload - can now perform soft reloads
/greload - still performs hard resets

Soft Reloads mean that SubServers will load new data from the config and attempt to merge it with what is already in memory.

This is good if you need to make some quick changes, since it will only stop servers if a major change has been made to them.

However, this has the potential to cause issues, which is why the Hard Reset will continue to be tied to bungeecord command.
2017-12-09 03:43:29 -05:00
ME1312
556d947981 Add Proper RedisBungee Support 2017-12-08 02:35:50 -05:00
ME1312
5050baedf8 Assume 1.13 Material enum values // Correct Patched Signatures 2017-12-07 17:51:06 -05:00
ME1312
a8bbd09e9d Add some force quit padding // Rewrite group system internals 2017-12-06 17:34:47 -05:00
ME1312
a019383bc3 Preserve YAML element order 2017-11-22 16:58:33 -05:00
ME1312
9a219a7d0f Queue packets until subdata connection is authorized 2017-09-23 23:19:22 -04:00
ME1312
ba09bab93a Add Server Grouping 2017-08-26 01:19:59 -04:00
ME1312
41e77e124c SubServers, Host, Sync & Client v2.12.1d/2.12.1c/2.12.1a/2.12.1c 2017-08-22 09:02:23 -04:00