When you add a Fruity Limiter to the Patcher plugin you see that it has just one audio input and one audio output great for using it as a limiter. (captain obvious) But there is no way you can connect two signals to that. If you connect both to the input you get a mess of both sounds getting limited. That’s not what we want. Download the file removeFLregistrysettings.zip to your pc. Unzip the file using Windows Explorer to get: REMOVEFLStudioLicense.reg. Double click the file REMOVEFLStudioLicense.reg to run it. Click the 'OK' to all pop-ups. I almost get the whole time this message that my plugins could not be found after loading some old projects in FL Studio 12.3. It's so weird, because I can open and use all the same plugins in a new project without any issues. Fruity Limiter.dll could not be found. Cannot find C: Program Files (x86) Image-Line FL Studio 20 Plugins Fruity Effects Fruity Limiter Fruity Limiter.dll. Cannot register Fruity Limiter.dll.
- Native Minecraft Version:
- 1.13
- 1.12
- 1.13
- 1.14
- 1.15
- 1.16
- Source Code:
- https://github.com/Spottedleaf/PacketLimiter
- Donation Link:
- https://www.paypal.me/spottedleaf
Spigot/Vanilla does not provide any level of protection against packet spam. As such, individual players can send as many packets as they want.
I found that while testing on 1.13, I could send about ~40,000 move packets to the server and either take it down or make it lag very hard due to the processing of the move packets on the server thread.
The solution was to limit the maximum packets/s a client could send.
Dependencies
Requires https://www.spigotmc.org/resources/protocollib.1997/
Configuration
The configuration is simple, containing a max packet rate and the interval that rate is measured over. The kick message is also configurable.
In general, raising the interval will allow higher peak packet rates, which will be better for players with very poor networking. Lowering will have the opposite effect.
The Fruity Limiter Plugin Could Not Be Found Yet
The defaults are targeted at preventing obvious packet spam, like my example, while still leaving good room for players with really bad networking.