User Interface (UI) / User Experience (UX) · Maps · Created by
therandombadass
accepted
maps map testing useraccess user-access hide view who-can-see see
What functionality is missing? What is unsatisfying with the current situation?
I just want the ability to hide pins that are private on the map without having to inspect the website and manually hide stuff.
like no need to remove pins or do anything fancy with access, just some CSS magic like classing pins with access tags (like if access group "players" can access it you add "class: access_players" to the HTML element of the pin, and adding a toggle to override "display:[whatever]; to "display: hide;" for everything with that class.
to be fair, for this to work there would have to be made something that added the class to the pin when it is being created, but it really shouldn't be too much work.
How does this feature request address the current situation?
currently, I would have to log out and view the map unlogged or on a different account, or manually hide pin elements.
What are other uses for this feature request?
I don't know too many uses for it in its current state other than what I'm asking for. however, it might help with getting an overview of what the players might see, creating a sort of "pseudo player view" where you hide parts in the browser, without having to remove the elements with backend and user access stuff, the technique might be implemented elsewhere to give the same effect in articles, but that's not what I'm asking, just a sales pitch to catch the devs interest.
ps: sorry for any bad writing
The Team's Response
Yup
I think we can do something like that with the Atlas release
Current score
322/300 Votes · +47820 points