Posts: 977
Threads: 63
Joined: May 2011
Staff roles: Coding Developer King of FLServer
Hello, it's me, Aingar: Everyone's Friend.
With tomorrow's restart, there will be a rather big overhaul of POB access management. Aim of those changes is to stop ooRP behavior of supplying bases with straight up hostile IFF'd ships, while leaving a way to allow such 'unorthodox' docking permission via POB Requests.
Whitelisting Hostile Ships
With this rework, making a ship dockable on a POB via adding to a whitelist will no longer be possible. If you're red to Outcasts on your Samura transport, adding your ship to the whitelist will still result in the base flashing red. Such behavior will still be possible, but only via 'SRP Whitelist', which will be governed by Admins via POB requests. Provide adequate roleplay, and there will be no issues
Defense Modes
There will now be three defense modes, down from five.
Command Syntax
All base access related functionalities will now be part of the /access command.
/access list <srp|whitelist|blacklist>
/access clear <srp|whitelist|blacklist>
/access add <name|tag|faction> <srp|whitelist|blacklist> <entry>
/access remove <name|tag|faction> <srp|whitelist|blacklist> <entry>
Yes, we will now allow Exact Shipnames to be added to POB config. No more do you need to worry about Jason.Bourne2 getting unauthorized access to your base!
A few examples:
/access remove faction blacklist fc_c_grp - remove corsairs from the blacklist
/access add name whitelist Steve - Adds Steve to the name whitelist. A ship named Steve2 would not be let in
/access add tag blacklist [XxX] - blocks access for ships with names starting with "[XxX]"
Another QOL improvement is that factions no longer are added/removed via numerical hash you had to generate, but now accept their nickname, such as br_m_grp for BMM. Those are easily findable using DarkStat or FLStat.
As mentioned previously, "/access add X srp" will only be available to Server Admins.
Limitations
Each of the whitelist and blacklist access lists will have a limit of 20 entries to avoid bloating the POB configs that means up to 20 whitelisted names, 20 whitelisted tags, 20 blacklisted names etc etc. Existing stations with more than 20 entries of a given kind will keep them, but you will be unable to add more until you go below the limit.
TL;DR: New command syntax, it will be no longer possible to enable docking for hostile/nodock rep ships without Admin Intervention. For example, no more Bowex ships docking on Molly bases, except for approved "SRP" docking requests.
During transition to the new system, bases with Defense Modes 2 and 4 will be moved to Defense Mode 1, those with Defense Modes 1 and 5 will move to Defense Mode 2, bases with Defense Mode 3 will remain as is.
EDIT: Almost forgot, dockable POBs will now always show as green, undockable POBs will show as white or red.
Quote:Command Syntax
All base access related functionalities will now be part of the /access command.
/access list <srp|whitelist|blacklist>
/access clear <srp|whitelist|blacklist>
/access add <name|tag|faction> <srp|whitelist|blacklist> <entry>
/access remove <name|tag|faction> <srp|whitelist|blacklist> <entry>
So, as an example:
/access add <name|tag|faction> <srp|whitelist|blacklist> <entry>
Actual use would be:
"/access add BAF|Theodore whitelist"
Would this be correct?
(Great to see flaws being filled in,, this makes PoBs docking like it was always intended to be.)
It's a shame a few have to ruin it for the rest of us but this sounds like a good idea, if you weren't the problem then it won't affect you. Some fines/sanctions would have been good too.
Posts: 977
Threads: 63
Joined: May 2011
Staff roles: Coding Developer King of FLServer
(09-05-2024, 11:53 PM)Lord Chaos Wrote:
Quote:Command Syntax
All base access related functionalities will now be part of the /access command.
/access list <srp|whitelist|blacklist>
/access clear <srp|whitelist|blacklist>
/access add <name|tag|faction> <srp|whitelist|blacklist> <entry>
/access remove <name|tag|faction> <srp|whitelist|blacklist> <entry>
So, as an example:
/access add <name|tag|faction> <srp|whitelist|blacklist> <entry>
Actual use would be:
"/access add BAF|Theodore whitelist"
Would this be correct?
(Great to see flaws being filled in,, this makes PoBs docking like it was always intended to be.)
Correct form would be /access add name whitelist BAF|Theodore, the <entry> in the command syntax is either a name, a faction tag, or the faction nickname.
I will edit a few examples into the first post.
Posts: 977
Threads: 63
Joined: May 2011
Staff roles: Coding Developer King of FLServer
(09-05-2024, 11:57 PM)Hawksmoor Wrote: It's a shame a few have to ruin it for the rest of us but this sounds like a good idea, if you weren't the problem then it won't affect you. Some fines/sanctions would have been good too.
As I mentioned in the post, if you produce valid roleplay explaining why an exception to this system should be made, it can be done via the SRP Wishlist system.
(09-05-2024, 10:54 PM)Aingar Wrote: TL;DR: New command syntax, it will be no longer possible to enable docking for hostile/nodock rep ships without Admin Intervention. For example, no more Bowex ships docking on Molly bases, except for approved "SRP" docking requests.
Long story short, this is a positive change and it will be good to be done away with the inappropriate 5k alts. I don't remember agreeing to be your friend though.