Configuration API

[Owen1212055]

Please provide feedback on naming, and general event consensis.

But my goal is to have the following:

• Full cookie getting/setting support in the login/config/play stage. This means you'll be able to disconnect players during LOGIN depending on sent cookies. (Bukkit only allows play stage, and PARTLY config stage) (CookieConnection)
• Allowing to boot players into the config stage/ out of it
• Allow to add custom configuration tasks, so for example being able to load player data. (AsyncPlayerConnectionConfigurateEvent)
• Allowing to load resource packs during config stage better
• Transfer the player in config/player
• send custom report details (shown in client debug log)

[Copilot]

Copilot reviewed 45 out of 46 changed files in this pull request and generated 1 comment.

Files not reviewed (1)

• paper-api-generator.settings.gradle.kts: Language not supported

Comments suppressed due to low confidence (3)

paper-api/src/main/java/org/bukkit/event/player/PlayerLoginEvent.java:22

• The deprecation version 'idk' is unclear; please update it to a proper version string to improve clarity.

@Deprecated(since = "idk")

paper-api/src/main/java/io/papermc/paper/event/connection/configuration/PlayerConfigurationConnectionEvent.java:8

• [nitpick] The field 'loginConnection' should be renamed to 'configurationConnection' to better reflect its purpose in a configuration event.

private final PlayerConfigurationConnection loginConnection;

paper-api/src/main/java/io/papermc/paper/connection/PlayerCommonConnection.java:3

• [nitpick] Consider clarifying the name of this interface to more clearly describe its purpose, such as 'PlayerSharedConnection' or a similar term.

// TODO: Naming?