Plot / lair permissions

[Andrakhyn]

The way current plot / lair permissions work is like this.

At the plot level you can set permissions as:

• Deny All
• Allow All
• Guild Only
• Friends Only (can manage plot friends list here)

At the individual structure level you can set permissions as:

• Locked
• Open
• Guild Only

Any player attempting to access a structure needs to meet both the plot and structure permissions.

This works for some scenarios but not others. Many players - myself included - would like to leave a few silos public. My lair is very close to resources and I would like to leave most of the silos around my crafting chambers open for the convenience of other players.

But to do that I have to set the plot level permission to Allow All. This unfortunately isn't an option. I share the lair with another Dragon which means I use Friends Only as the plot level setting. I believe the Friends Only setting is also commonly used to allow a player's alts access to a plot.

A relatively small change to the permission system which would offer MUCH more flexibility would be...

At the plot level you can manage your plot friends list:

• Friends (can manage plot friends list here)

** removed Deny All, Allow All, Guild Only, Friends Only settings **

At the individual structure level you can set permissions as:

• Locked
• Open
• Guild
• Friends [NEW]
• Guild + Friends [NEW]

Any player attempting to access a structure need only meet the structure permissions [NEW]. Note, however, that a separate friends list would not be kept for each structure. A single friends list would be stored at the plot level (as now) and checked if that option was selected for a structure.

The only option lost with this scheme is using the plot level Deny All setting to instantly deny access to everyone but the owner. This could added as an extra setting / check if desired.

It would be even better if you could allow for two or three separate friends lists but that would probably require a redesign of the structure level permission UI - eg. adding multiple-select checkboxes. That might be difficult?

[Northwind]

Wouldn't be easier to make individual structure permissions to take precedence over general plot permissions while having the exact same set of permissions at both levels (Allow All, Deny All, Guild Only, Friends)?

Or, even better, to have the last setting to take precedence over previous: setting Deny All at plot level will set "deny all" to all structures, then you go to those structures you want to open and set them to Friends/Allow All/etc individually.
If you change your mind and don't want to reset permissions individually on structures, then you can go again at plot level and set Deny All again

This way you can set a global permission for the entire plot/lair, then customize the permissions at structure level if you want to set different permissions to certain structures.

[Andrakhyn]

Wouldn't be easier to make individual structure permissions to take precedence over general plot permissions while having the exact same set of permissions at both levels (Allow All, Deny All, Guild Only, Friends)?

At least in the current scheme every structure has a permission setting so it would always take precedence. Plot level permissions would be something you could set but would have no effect at all.

Or, even better, to have the last setting to take precedence over previous: setting Deny All at plot level will set "deny all" to all structures, then you go to those structures you want to open and set them to Friends/Allow All/etc individually.

For the game to determine which is the last setting it would need to record the date+time of every plot and structure permission every time you set it. That's do-able and date+time data is fairly small, but it would require database changes.

If I could suggest something simpler that seems functionally similar?

Have a permission setting at the plot level which lets you simultaneously change the permission setting for all structures at once. No extra data needs to be stored - when executed the code would just write the new permission settings directly to each structure.

[Northwind]

For the game to determine which is the last setting it would need to record the date+time of every plot and structure permission every time you set it. That's do-able and date+time data is fairly small, but it would require database changes.
.

no? why's that?
Every structure should have only one permission setting.
With plot setting you should set permissions to every structrure in the entire plot in bulk mode, while with structure permissions you should set them individually.

At least in the current scheme every structure has a permission setting so it would always take precedence. Plot level permissions would be something you could set but would have no effect at all.

No again.
In the current scheme you have 2 permission types (plot and structure) the most restrictive permission of those two is taking precedence.

But what is creating all this mess is the fact that structure permissions is lacking the Friends setting.
Add that and it will make the things less annoying.
If you also remove the "most restrictive permission takes precedence" you could have best granularity in permission settings.

[Andrakhyn]

no? why's that?
Every structure should have only one permission setting.
With plot setting you should set permissions to every structrure in the entire plot in bulk mode, while with structure permissions you should set them individually.

What you suggested was, and I'll quote for ease:

Or, even better, to have the last setting to take precedence over previous: setting Deny All at plot level will set "deny all" to all structures, then you go to those structures you want to open and set them to Friends/Allow All/etc individually.

For the game to determine what the "last setting" is it would need a date+time stamp on each permission setting for comparison.

That or a scary Skynet-like intelligence....

No again.
In the current scheme you have 2 permission types (plot and structure) the most restrictive permission taking precedence, be that at plot or at structure level.

Take a moment to think about this.

What I've said is right - for a player to access a structure they need to meet BOTH plot and structure permission settings.

The logic / test is:

IF Player meets plot permission AND player meets structure permission THEN allow access

What you're saying is a more convoluted alternative logic that would always produce the same result as the simpler test above.

First you'd need to store ratings for each permission setting and it's level of restrictiveness.

The logic / test would be:

1) Grab plot and permission restrictiveness rating
2) IF plot permission rating > structure permission rating THEN use plot permission ELSE use structure permission
3) IF player meets (plot or structure permission depending on stage 1+2) THEN allow access

If you don't believe me, grab a pencil and paper and run both tests through a few scenarios.

[Northwind]

You really like to twist things up and make a mess out of them, aren't you?
Let's see:

For the game to determine what the "last setting" is it would need a date+time stamp on each permission setting for comparison.

That or a scary Skynet-like intelligence....

Seriously? No.
Actually it only needs a single place to store the permissions (at structure level), not two, and that place obviously will store only the LAST SETTING.
You came to the same conclusion at the end of post #3 but using a different phrasing

What I've said is right - for a player to access a structure they need to meet BOTH plot and structure permission settings.

The logic / test is:

IF Player meets plot permission AND player meets structure permission THEN allow access

What you're saying is a more convoluted alternative logic that would always produce the same result as the simpler test above.

First you'd need to store ratings for each permission setting and it's level of restrictiveness.

The logic / test would be:

1) Grab plot and permission restrictiveness rating
2) IF plot permission rating > structure permission rating THEN use plot permission ELSE use structure permission
3) IF player meets (plot or structure permission depending on stage 1+2) THEN allow access

If you don't believe me, grab a pencil and paper and run both tests through a few scenarios.

That makes no sense whatsoever.


You said in your initial response that:

At least in the current scheme every structure has a permission setting so it would always take precedence. Plot level permissions would be something you could set but would have no effect at all.

So Plot level permissions could be set but would have no effect at all? Wrong.
Try to set Deny all at plot level, then see if it matters
Or keep reading this post

I said that we currently have two permission settings (plot and structure) and the most restrictive permission takes precedence. I invite you to test it.
Plot has: Allow All, Deny All, Guild Only, Friends
Structure has: Open, Locked, Guild only
Note: The owner always has access, no matter what permissions he set.

Scenario1: Deny All at plot level.
It doesn't matter what you set at structure level, Deny All is the most restrictive setting and it will deny access to everyone.
Conclusion: No one has access bar the ower, no matter structure permission

Scenario2: Guild Only at plot level
Now if you set Open at structure level, the Guild only will be in effect as it being the most restrictive.
If you set it to Locked, then it will be locked to everyone else since Locked is more restrictive than Guild Only
Conclusion: Either the entire guild or ONLY the owner will have access to a structure based on structure permission

Scenario3: Friends at plot level
Set the structure to Open, then Friends list will take precedence since is more restrictive and only Friends will have access
Set the structure to Guild only, then Friends list will take precedence since is more restrictive
Set the structure to Locked, then it will be locked since Locked is more restrictive
Conclusion: Either the Friends list or ONLY the owner will have access to a structure based on structure permission

Scenario4: Allow All
Structure to Open: means the structure is Open to all - that is Public.
Structure to Guild: means the structure is open to Guild only, Guild setting being more restrictive and taking precedence
Locked: means the structure is locked to all, Locked setting being more restrictive and taking precedence.
Conclusion: Structures can be Public, open to Guild or only to owner based on Structure permission settings.

So, as it is now, we cannot have on a plot both Public and Friends structures NOR Friends and Guild structures. Which is a rather harsh limitation.

How can that be corrected?

1. Keep the current system but add Friends setting on structure level.
If we would have that, then we could set the plot to Allow all, then set permissions on each and every structure to be either Public, open to Guild, open to Friends list or Locked. The Friends list could be common to both Plot and Structure.

2. Drop the current system, have the Plot and Structure having the same permissions (Allow All, Deny All, Guild, Friends) and make the Plot settings to make bulk settings to all structures. You could then go and customize each structure individually. That's what I said in post #2 and also Andrakhyn "translated" it at the end of post #3

[fashionever]

You can not have a silo open to a few friends and another silo open to everyone