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
{{ message }}
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.
The feature could work like this:
epicguard.accountlimit.x (x = nr of accounts that ip can use)
if the player doesnst have the permission it would use the default permission node.
Would also be nice with a bypass permission node (any player with this permission node would not be counted towards the account limit).
Could look something like this:
epicguard.accountlimit.bypass
Tobi
The text was updated successfully, but these errors were encountered:
The problem is that during checking the player is not connected yet, so it's not possible to check their permissions. But maybe I'll find a different way...
I see hmm I thought about it & maybe a way to go is that the plugin keeps a list of what accounts have connected with what ip (I assume you have access to ip at least) & then you could perhaps based on that give some sort of permission?
Or maybe not have it work on first join but then after that it would know what what account is linked to that ip & can check its permissions?
Just some ideas not sure if they would actually work out :)
Tobi
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey,
The feature could work like this:
epicguard.accountlimit.x (x = nr of accounts that ip can use)
if the player doesnst have the permission it would use the default permission node.
Would also be nice with a bypass permission node (any player with this permission node would not be counted towards the account limit).
Could look something like this:
epicguard.accountlimit.bypass
The text was updated successfully, but these errors were encountered: