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

[Suggestion] Ability to restrict frequency jammer numbers owned by the same group #287

Closed
MGTDB opened this issue May 17, 2015 · 6 comments

Comments

@MGTDB
Copy link
Contributor

MGTDB commented May 17, 2015

I propose that a limit can be put on the amount of frequency jammers that can be owned per group. Maybe make the amount a variable set by server admins.

This would stop large(r) established groups creating too many frequency jammed bases thus making it harder for newer players to get established.

@ravmustang
Copy link
Contributor

I agree group based limit would counteract those issues.
however a new set of players without a group could exploit that and setup multiples then create the group to bypass this or

This should be two config settings, one for player and one for group.
however,

Then you run into the problem of adding a new individual who already has a base within the limits but then can't join the group because it would put them over the limit or it would just bypass the limit anyways, leading us back down the same road as we started with.

@MGTDB
Copy link
Contributor Author

MGTDB commented May 17, 2015

Then maybe if a new set of players exploit that with multiple jammers they get locked out of creating a group together?

@bacchus101
Copy link

In conjunction with a configurable and/or much higher per peice default maintenance cost, I think a group + per user frequency jammer limit would be a major step forward in keeping the world limit in check on high population servers.

@MatijsVDG
Copy link

Would love to see this.

@Alexandre-S
Copy link

+1

Maybe add it confirgurable on epochconfig.hpp with a variable like

"jammer_number_per_group" and set it to 0 or -1 to no restriction, and then like 1 / 2 / 3 / .... like admins wants !

@vbawol vbawol added this to the 0.4 milestone Jul 28, 2015
@vbawol
Copy link
Member

vbawol commented Jul 9, 2016

Thanks to @Ignatz-HeMan this has been added since b563

@vbawol vbawol closed this as completed Jul 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants