[Request] Player Object Creation Event

Is your feature request related to a problem?

Recent internal changes in Paper have altered when the Player object becomes available during login.

Libraries like PacketEvents depend on accessing the Player instance as soon as it’s created to attach handlers and initialize player-specific logic.

Currently, there isn’t a consistent point or event that guarantees when the Player object is first created. This makes it difficult to reliably detect that moment across Paper versions without using workarounds.

Describe the solution you'd like.

We would love to have a consistent event that fires the moment the Player object becomes available, regardless of whether that’s before or after login packets are sent.

For example, a PlayerAvailableEvent or PlayerInitEvent that is guaranteed to fire exactly once, as soon as the Player instance exists and is safe to access, would solve this problem completely.

Why this helps:

• Provides a consistent and predictable hook for libraries and plugins to initialize player object specific logic
• Removes the need for timing-based workarounds or delayed initialization
• Keeps compatibility stable even if Paper changes internal login behavior again in the future

Describe alternatives you've considered.

Previously, we relied on an early Paper event to access the Player instance as soon as it was created.
Since that event was removed, the first reliable point to get the Player object is now PlayerJoinEvent.

To work around this, we currently pause the packet encoder once the player has finished logging in and wait until PlayerJoinEvent fires before resuming.
If a new PlayerInitEvent (or similar) were introduced, it might allow us to remove that pause, but even if not, the main benefit would be having a consistent, guaranteed event to rely on across future Paper versions.

Other

No response

Start by reviewing the existing PlayerJoinEvent flow and the login path where the Player instance becomes available; the issue does not identify implementation files or tests. Compare that flow with the removed early Paper event and the packet-encoder workaround. Done means a documented event fires exactly once when Player is safe to access, consistently across login timing changes.