You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tell us what you want!
FactionsUUID already has buffer limits, which can help preventing players from creating unraidable bases. But Factions can still create huge claims, for example 100+ chunks in 1 piece to create unraidable bases.
I think it would be good idea to implement some kind of cap on how large each base can be, I think that could be based on no of connected chunks or maybe even height/width of one claim.
The idea is to force places to at least split their claims into smaller bases if they wanna claim a bunch of land, and required between bases should take care of proximity of those bases.
Details
Give some more information so we can get an idea.
Essentially... chunks that are from same faction and connected would be considered one claim, my suggestion would add limits on max height/width of each claim and maybe even/or max no. of chunks.
The text was updated successfully, but these errors were encountered:
Idea
Tell us what you want!
FactionsUUID already has buffer limits, which can help preventing players from creating unraidable bases. But Factions can still create huge claims, for example 100+ chunks in 1 piece to create unraidable bases.
I think it would be good idea to implement some kind of cap on how large each base can be, I think that could be based on no of connected chunks or maybe even height/width of one claim.
The idea is to force places to at least split their claims into smaller bases if they wanna claim a bunch of land, and required between bases should take care of proximity of those bases.
Details
Give some more information so we can get an idea.
Essentially... chunks that are from same faction and connected would be considered one claim, my suggestion would add limits on max height/width of each claim and maybe even/or max no. of chunks.
The text was updated successfully, but these errors were encountered: