dominik48n / party-system Goto Github PK

Include a config entry that allows servers to be blacklisted so that if the party leader joins this server, the party is not pulled along.

It would make sense to support explicit server names, as well as the beginning of a server name. As an example, all servers whose names begin with "Lobby" are directly blacklisted.

Include a function to query players via the /party list command for party information from a party where the player himself is not inside.
Means, PlayerA can type /party list PlayerB and if PlayerB is in a party, PlayerA will get the same information as if PlayerB type /party list.

In order to read out the party information of other players, an extra permission should be required so that server administrators can optionally only make this function available to their moderators.

The advantage of the function could be that when the server moderators edit reports, they can see directly who a reported player is in a party with, e.g. to better identify teaming bans.

Implement configurations so that server administrators can customize the /party and /p commands and add aliases.

If a server uses another system that uses the /p command, for example, you can still use both systems if you change the /p command from the party system to /pc in the config, for example renamed. In addition, a config option for command aliases is also very useful.

Support Redis Cluster

As soon as the license from sadu finally changes to the planned LGPL-3.0, we will use sadu.

The library offers us many easy ways to extend our SQL database support.

It should be possible for a player to set whether he would like to receive party requests, whether he would like to receive notifications for party joins and leaves and whether he would like to be able to write or receive messages in the party chat.

It should also be possible to deactivate the function if you do not want to use the function.
If you do not use a function that requires a database, no connection to the database will be established when using the plugin.

Various database systems should be available for this. A few examples of database systems that could be supported:

• MongoDB
• PostgreSQL
• MariaDB

As a player, I would like the ability to disable and enable party invites.

For this we need an invite command:
/party invitation [enable|disable]

Staff member should have the ability to bypass this restriction.

An update checker that uses GitHub Releases to check if a new version of the party system is available. If this is the case, the administrators will be notified in-game as well as via the console.

Only a limited number of members should be able to join parties. The maximum number of members should be determined by the party leader's permission. In addition, there should be the possibility to generally issue the member limit in the config.

It should be possible, with a permission, that players can create public parties where any player can join without an invitation.

Of course, this feature should also come with the ability to ban and unban players from the public party.