Improving The ExtensionFloodFilterConfig

[tropyw]

I’ve been exploring the "ExtensionFloodFilterConfig" class in SmartFoxServer 2X and found its functionality quite limited for my use case. As it currently stands, the class doesn’t provide the flexibility I need to effectively manage flood attempts in my game. To address this, I would like to suggest the following improvements:

1. Add a "Kick" Option: The system currently defaults to banning users who trigger the flood filter, but this can be too extreme for certain situations. A "kick" option would be a much better fit in many cases, allowing for temporary removal without a ban, giving users the chance to rejoin without being permanently blocked.

2. Add a "Callback" Option: To further enhance flexibility, I suggest implementing a callback option that triggers when a flood attempt is detected. This would allow developers to handle the event with custom logic, such as issuing warnings, tracking incidents, or applying dynamic rate-limiting based on behavior. Being able to manage these situations through custom code would significantly increase the utility of the flood filter.

I believe these additions would provide much-needed flexibility and make the system more adaptable to a variety of use cases, including mine.
Thank you for your consideration, and I look forward to your response!

Best regards.

[Lapo]

Thanks. Good ideas, in particular the callback function.
We'll likely add these to the next major release.

Cheers