Hello, so far i think how the inheritance should work is that all ranks should inherit from Residen however the ranks above it should not inherit each other...

Current system: Elder -> Inviter -> Builder -> Resident

What the system should be: Elder -> Resident, Inviter -> Resident, Builder -> Resident

This way should be way way simpler for players who has no idea how inheritance works or it should be a lot easier for players to really just comprehend how the permission works

Remove this toggleablecommands /s perms: (for the sake of simplifying what they can edit)... I don't want to bombard players with too many toggleable commands that they probably will never touch.

/s bank deposit
/s bank balance
/s bank
/s transfer
/s deposit
/s leave
/s reslist
/s materials
/s outpost list
/s outpost
/s upkeep
/e create
/e join
/s disband

add a toggleable perm where they can be exempted from /s tax
for the /s setrank,,, they should only be able to set the ranks below them.. EVEN THOUGH the inheritance system has change, the heirarchy inside the plugin should still be the same.. We are only changing the inheritance system for player's convenience.

Currently, the big issue on the settlement ranks are the rank names, like on /s perms, they're on assistant and all that but when they do /s setrank command, it shows "duke, noble, greeter".... So currently players want a customizable settlement names that will alter their own settlement ranks (this is very important feature for role playing players)

/s rank
- the name should not exceed 16characters
- the name should never have color codes in it
- it also shouldn't have a curse word in it, we can incorporate the censored words on /s chat swear on this
the  will be based on what they have set...

The universal default names on the ranks should be Assistant, Elder, Inviter, Builder, Resident just for the sake of simplicity.
Besides the issue above, the organized s perms is the only thing left on this feature (categorized) like the one issue i wrote up.