LimboAPI and FastMOTD support for Velocity

[UserNugget]

This pull request implements support for LimboAPI and FastMOTD.

Fixes Elytrium/LimboAPI#146
Fixes #873

[retrooper]

Does this actually work?

[UserNugget]

Does this actually work?

Yep, but require a bit cleanup.

[retrooper]

I'll happily add to the current progress, but getting some testers on this would be great.

[Bram1903]

I will give it a shot this evening.

[Bram1903]

Hello @UserNugget,

I attempted to test your branch with the latest Velocity build and your PacketEvents branch, but encountered an issue. Specifically, I'm receiving a read timed out error in my console and am unable to join the server. However, when I remove the LimboAPI plugin, everything functions as expected.

Is there a dependency I might be missing (I couldn't find any listed) or does this need to be tested on a Linux-based operating system instead?

Test Setup

• Proxy: Velocity 3.3.0-SNAPSHOT (git-9d25d309-b400) with PacketEvents (your branch, compiled) and LimboAPI
• Backend: Paper 1.21 (master@62ed302) with ViaVersion and ViaBackwards (5.0.1)
• Client: 1.20.6

Console Screenshot

Kind regards,
Bram

[UserNugget]

@Bram1903, you should use LimboAPI build from LimboAPI PR as it have some changes required for this PR to work.

[Bram1903]

@Bram1903, you should use LimboAPI build from LimboAPI PR as it have some changes required for this PR to work.

Ahh, now it makes sense. Thanks for your quick reply. I just went offline for today, but will give this another look tomorrow morning!

[UserNugget]

I've tried to rethink how this PR might be used in the future, and looks like there are still some issues:

1. While FastPrepareAPI is used, only one PacketEvents instance will work properly
2. While FastPrepareAPI is used, all packets that was send directly via PacketEvents will be ignored

So looks like this PR still require some changes.

[bobhenl]

It would be good if they can be made soon so it's in the next release, so we don't need to use old build 😅

[rafi67000]

this PR can be closed, it's not needed anymore. LimboAPI works on it's own with

     save-uncompressed-packets: true
     compatibility-mode: true