Beacon Permissions

[Havok40k]

@olliepurkiss Can you confirm this?

[Marrash]

I just want to say that I wasn’t really intending to open this up a thing that needs an overhaul, just a slight tweak. I think Havok’s suggestion (and possibly even the way it is intended to work that just got lost in it’s translation from english to Marrash) seems pretty good, and covers all the basic needs for personal beacons.

[olliepurkiss]

I’ve posted on this in the other thread, before reading this.

I think it’s a neat solution to need both permissions, but it might not be crystal clear to people. I’ve proposed the addition of a third permissions type:

Player Warning: Socal

You’ve identified a weakness in our current proposal, so I think we need a third permissions type. That will mean that you can give someone one or more of the following permissions: Builder – can place and break non-interactive blocks and props. Worker – can interact with things. Engineer – can place and break interactive blocks and props. (Doors may be counted as non-interactive for the purposes of permissions).

[olliepurkiss]

I agree that subdividing will be wanted within a big build (your middle suggestion). I’ve always thought that the way to do that though is to allow people to split new beacons off from an existing beacon, and then each beacon can have its own permissions. That seems to be the simplest way of doing it conceptually.

[Stretchious]

Colour coded beacon controls!?

@Stretchious

One thing I would like to see is colour coded beacon controls (with the ability to extend each specifically coloured beacons plot size using the current method).

This would allow you to have multiple separate beacons in the same area, which could be used to segregate different sets of permissions/restrictions among friends. Want to grant access to a single beacon where you can share resources with your neighbours? Just add them to your blue beacon control (etc.)

This would also allow you to essentially rent out space in your main building without people having access to your entire build (which would also help to circumvent the current vertical plot blocking restriction).

[Kawwak]

This class based permissions are the plan for 1.0 too? What about a checkbox-category system?

Like at the beacon control you have the permissions menu, where you can see the permission categories (like interactables), and within each category there are 3 checkboxes: ‘only me’, ‘add player/guild’ and ‘everybody’. The ‘only me’ is the default in each, and if you check the ‘add player/guild’ from the 3, there you can add players and guilds to access that category. ‘Everybody’ is obvious.
And the categories could be: (everybody can interact with non-locked doors and non-locked trading plinths, they are not on the list)

• Interact with locked doors
• Interact with locked trading plinths
• Access to non-locked trading plinths (so can put/withdraw items and coins, not just trade with it)
• Access to locked trading plinths
• Interact with non-locked machines
• Interact with locked machines
• Interact with non-locked storage
• Interact with locked storage
• Interact with portals (can fuel, close/open it)
• Warp in/out (so can build warp inside the beacon)
• Place/break non-interactive blocks and props
• Place/break interactive blocks, props and locks
• Interact with beacon control (who have permission in this, can access the permissions menu too)

[Heureka]

I like the idea of a checkbox that allow anybody to fuel beacon and portals without getting access to anything else, and without have to be added to the beacon.

[Kawwak]

So like an ‘- Add fuel’ permission category not listed above? Which allows the checked persons to access the beacon and portals fuel tabs but they can only add fuel to it and cant withdraw? If it is possible it could be default, so we dont need the checkbox category for it, cause who dont want free fuel? But if its not possible, with my categories only those could fuel a portal whose can defuel, and open/close, redestinate it, and only those could fuel the beacon whose can defuel it and have access to the permissions menu too. So if this is the case only trusted people can fuel portals/beacons, cause they could defuel it too.

[Heureka]

I mean, if i see a nice builds or a portal that soon run out of fuel, i can fill it without to be added to any beacon, or even know who it belong to.

[Kawwak]

Sure thats why (only) adding fuel to beacons/portals should be open to everyone, if its possible (from developer side).