-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Feature Request] Private Portals #67
Comments
Hi, thanks for your suggestion! In issue #58 someone asked for "password tags" - would that align with your request too? If so we can close this issue and you can comment there. |
Yes and no tbh. Id still want them to be open an easily to walk through, but on a busy server, with multriple portals the list gets quite long to scroll through, so if portals could be marked as "Open" so everyone can see them or "Private" so only you can see the portal in the list |
And by private do you mean only you should be able to see it? Or others too? How do you envision maintaining access control? Just fishing for ideas to better understand your request. |
Basically if the portal is marked Private, it dosent show up in the list of portals for anyone but the maker of the portal itself unless the portal is un-tagged as Private and then shows up for everyone in the list of available portals. |
If I understand correctly this is intended to work only when playing alone? I.e. if you play together with someone else, they wouldn't be able to use travel to your "private" portals. Is that a correct interpretation? |
Yes, in multiplayer, if your portal is set to Private nobody but the maker/owner would be able to see that portal name, so when the list of portals is shown, the portal marked Private will not show up in the list. If a player sets a portal down, they can mark it to PRIVATE, and its not accessible to any other players.. |
Basically have an option so that a portal can be set so only the individual who made the portal can see the connection or mak eit so anyone can see it.
The text was updated successfully, but these errors were encountered: