Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Fastbreak Protection #63

Open
crimsonblod opened this issue Sep 13, 2019 · 0 comments
Open

Feature Request: Fastbreak Protection #63

crimsonblod opened this issue Sep 13, 2019 · 0 comments

Comments

@crimsonblod
Copy link

crimsonblod commented Sep 13, 2019

For the past couple years, there have been a few hackers using fastbreak for citadel every single time they log in. From what I understand (And have seen), it first requires them to break the block once at normal speed, and it proceeds to break the remaining durability of any reinforced block within a few seconds after the end of the initial break.

A sort of "global speed limit" could be helpful in at least mitigating this. A couple ideas are to either have a straight up global speed limit, or to limit the speed based on how many people are breaking the block.

For the global speed limit, some math would need to be done to calculate the exact maximum possible break speed for a reasonably sized group of players, then just enforce that as the maximum break speed for a given block.

For a live playercount based solution, I would think that at some point, either citadel or namelayer has to know who is breaking the block anyway, to know if they have CTB permissions, so perhaps this could also count how many people are breaking the block to make sure that it isn't excessive for a given playercount. This seems like it would be a better long term solution, because it would limit the hacking players to a much lower maximum speed limit, but I'd imagine also requires the most work of all the solutions.

Also, updating the devotion requirements plugin to work with the current state of civclassics would help throttle how many alts the hackers could get on in a day significantly. Even just an hour or two of work would help turn the 3-6 ish attempts they make in a given day when they decide they want to kick over elegos, down to 1-2 hacking attempts ish, given that they seem to be limited more by free time than availability of alts and vpn's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant