Invitation System

[TptMike]

The Guild system now has creation and member addition functionality. The addition code needs an invite layer added to it so that invitees can accept or decline guild invites.

Requirements

Invites Table

In case of a shutdown or reboot, data needs to be persisted in the database and loaded in the onEnable() method

In memory hashmap

This data should be serialized and loaded into a hashmap in active memory so that it may properly resume the timeouts needed for invites to expire and so that players can be notified that they have an invite waiting when joining the game. This will be useful for sending multiple invites to the same player OR ensuring one invite is sent at a time

Roadmap

Invite class

Create

• Create the invite in the hashmap assigned to the player by uuid
• Store this invite in the invites table recording player_id, guild_id, expiry_timestamp, invited_by (leader_id), expired (0)
• spawn task thread to execute the update calls on expiry or accept/refusal and remove from hashmap

  Update (invite expired)

• If the expiry date has passed, the invite must be marked expired, update database record
• Remove the invite from the in-memory hashmap of active invites

  Load (onEnable())

• Helper method to load the hashmap with active invites from the database

  Events

• onPlayerJoin: send a message with all active invites with accept decline click event objects to execute the addmember method or the invite deletion methods.
• send a message right away if invitee is online at the time of the invite.

[TptMike]

Invites table scrapped in favor of in-memory singleton containing a hashmap of player UUIDs and a timer task to run at the end of the timer or be canceled on decline/accept. Players should be online when invited anyway.