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

feat: add simpleclans.other.clan-size.* permission node #443

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Tomut0
Copy link
Collaborator

@Tomut0 Tomut0 commented Oct 4, 2024

One of the problem that could happen here is when somebody changes the permission node number,
it wouldn't affect on previous clans. 🤔

That's why mods could have a command to modify the max-size flag.
If you agree, I'll make another PR about the command.

Or should it be commited here?

@Tomut0 Tomut0 requested a review from RoinujNosde October 4, 2024 17:32
@Nishikiyama
Copy link
Contributor

Would this be a global clan size or per-clan? I'm a little confused

@Tomut0
Copy link
Collaborator Author

Tomut0 commented Oct 4, 2024

Would this be a global clan size or per-clan? I'm a little confused

it's per-clan.
Config options are global ones used for clans creation.


if (maxMembers > 0 && maxMembers > clan.getSize()) {
if (plugin.getSettingsManager().getInt(CLAN_MAX_MEMBERS) > 0 && clan.getMaxSize() > clan.getSize()) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not use getMaxSize on both?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose that config value should have more effect than a dynamic flag

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

Successfully merging this pull request may close these issues.

3 participants