Recognized /add_admin_allowed_comand

[Erth Paradine]

Request:
Add support for /add_admin_allowed_command

Purpose:
Either allow an admin all commands, or allow only those in the list. Getting away from the current requirement to hunt down and list all non-permitted commands.

Rationale:
The current method of delegating admin access is error-prone, overly complicated, and perpetuates a negative reinforcement framework where roles/permissions are subtracted until reaching some lower threshold. Compounded by incomplete official documentation, this whole process is vulnerable to errors/omissions, and leaves an air of uncertainty primarily because the most recent relevant posting is over a year old.

Instead, if we delegated access by gradually allowing specific commands to various ranks, this perpetuates a positive reinforcement process that provides a more clear illustration of permitted tasks, it's a stronger future-proof means of role delegation and management: as new features/functions are added, risks of abuse or unintended authority, are minimized.

 

[Cheekiman23]

What are the specific commands that would be allowed per the various ranks of admin usage?

 

[Erth Paradine]

What are the specific commands that would be allowed per the various ranks of admin usage?

I imagine that would vary, at the discretion of each server owner. Although if the idea is to provide pre-structured ranks, hopefully adjustable by the server owner, then I imagine these would function similar to "groups" in traditional ACL implementations.

 

[Benevolent27]

This would be useful for more than just admins.

For example, on the server I play on, we have "BUILD" sectors. What the admins do is lock a person into a sector far away from the main universe and then give them creative mode. I imagine the admins may give the ability to /remove_entity, /remove_entity_dock, /clear_overheating, and /spawn_wave to these build accounts.

 

[Erth Paradine]

This would be useful for more than just admins.

For example, on the server I play on, we have "BUILD" sectors. What the admins do is lock a person into a sector far away from the main universe and then give them creative mode. I imagine the admins may give the ability to /remove_entity, /remove_entity_dock, /clear_overheating, and /spawn_wave to these build accounts.

That's exactly a scenario where an /add_admin_allowed_command would be very useful.

For instance, we're looking for a means to grant players permissions via a configuration as simple as:
#REMOVE_ENTITY,REMOVE_ENTITY_DOC,CLEAR_OVERHEATING,SPAWN_WAVE

Instead of the current requirement to use and maintain/update something like this:
#SPAWN_CREATURE,SPAWN_CREATURE_MASS,CREATE_SPAWNER_TEST,EXECUTE_ENTITY_EFFECT,LIST_ADMINS,FACTION_DELETE,FACTION_LIST,GIVE_RECIPE,LIST_BANNED_IP,PLAYER_LIST,GIVE_CREDITS,GATE_DEST,STATUS,LIST_BANNED_NAME,SECTOR_SIZE,GIVE_HEAL_WEAPON,CREATURE_GOTO,INITIATE_WAVE,DELAY_SAVE,TELEPORT_TO,GIVE_METAITEM,GIVE_MARKER_WEAPON,TP_TO,CREATURE_IDLE,LIST_WHITELIST_IP,FACTION_LIST_MEMBERS,TELEPORT_UID_TO,GIVE_LASER_WEAPON,CREATURE_ANIMATION_STOP,CREATURE_SIT,BAN_IP,SHIP_INFO_SELECTED,FACTION_ADD_MEMBER,GIVEID,LIST_WHITELIST_NAME,WHITELIST_IP,DESTROY_ENTITY,UNBAN_IP,GIVE_ALL_ITEMS,FACTION_SET_ENTITY,GIVE,GIVE_ROCKET_LAUNCHER,SPAWN_ITEM,FACTION_SET_ALL_RELATIONS,FACTION_MOD_RELATION,GOD_MODE,LOAD_SYSTEM,TP,SIMULATION_AI_ENABLE,KICK,REMOVE_ADMIN,LIST_SHIPS,KILL_CHARACTER,GIVE_SNIPER_WEAPON,GIVE_POWER_SUPPLY_WEAPON,STOP_SHIP_AI,LIST_SHIPS,KILL_CHARACTER,GIVE_SNIPER_WEAPON,GIVE_POWER_SUPPLY_WEAPON,STOP_SHIP_AI,LIST_CONTROL_UNITS,CREATURE_ENTER_GRAVITY,DAYTIME,SIMULATION_SPAWN_DELAY,FACTION_DEL_MEMBER,DEBUG_ID,CREATURE_ANIMATION_START,ADD_ADMIN_DENIED_COMAND,BAN_NAME,WHITELIST_NAME,SERVER_MESSAGE_TO,GIVE_CATEGORY_ITEMS,SET_DEBUG_MODE,UNBAN_NAME,REFRESH_SERVER_MSG,FACTION_POINT_GIVE,SHIELD_DAMAGE,FORCE_SAVE,STRUCTURE_SET_MINABLE,SERVER_MESSAGE_BROADCAST,SHOP_RESTOCK,CHANGE_SECTOR_FOR,GIVE_LASER_WEAPON_OP,SIMULATION_INVOKE,BAN_IP_BY_PLAYERNAME,BREAK_SHIP,CLEAR_OVERHEATING_ALL,INVISIBILITY_MODE,TELEPORT_SELECTED_TO,CUBATOM_RANDOM_FILL,TELEPORT_SELF_TO,CREATURE_STAND_UP,DECAY,ADD_ADMIN,LIST_BANNED_ACCOUNTS,START_COUNTDOWN,STRUCTURE_SET_VULNERABLE,REMOVE_ADMIN_DENIED_COMAND,START_SHIP_AI,FACTION_REINSTITUTE,FACTION_MOD_MEMBER,REMOVE_SPAWNERS,LIST_ADMIN_DENIED_COMMANDS,UPDATE_SHOP_PRICES,FACTION_EDIT,FACTION_JOIN_ID,CREATURE_ROAM,FACTION_POINT_SET,SHOP_RESTOCK_FULL,IMPORT_SECTOR_BULK,IMPORT_SECTOR,MISSILE_DEFENSE_FRIENDLY_FIRE,LIST_WHITELIST_ACCOUNTS,FACTION_CREATE,FACTION_CREATE_AS,REPAIR_SECTOR,CREATURE_RENAME,DESTROY_UID,CHANGE_SECTOR,JUMP,FACTION_POINT_TURN,SET_GLOBAL_SPAWN,CHANGE_SECTOR_FOR_UID,CREATURE_SCRIPT,SHIP_INFO_UID,SHIP_INFO_NAME,TERRITORY_RESET,DESTROY_ENTITY_DOCK,SECTOR_INFO,LOAD_SECTOR_RANGE,RESTRUCT_AABB,GIVE_LOOK,WHITELIST_ACTIVATE,IGNORE_DOCKING_AREA,SEARCH,PLAYER_PROTECT,CLEAR_OVERHEATING,CREATE_TRADE_PARTY,PLAYER_INFO,SAVE,SAVE_UID,LOAD,FACTIO_SET_ID_MEMBER,SPAWN_ENTITY,SPAWN_ENTITY_POS,EXPORT_SECTOR,SHOP_RESTOCK_UID,FACTION_POINT_PROTECT_PLAYER,FACTION_CHECK,DEBUG_FSM_INFO,SET_SPAWN,SET_SPAWN_PLAYER,SHOP_INFINITE,BAN_ACCOUNT,SPAWN_MOBS,FACTION_POINT_ADD,SHOP_RESTOCK_FULL_UID,SPAWN_MOBS_LINE,EXPORT_SECTOR_BULK,FACTION_RESET_ACTIVITY,PLAYER_UNPROTECTED,DESTROY_UID_DOCKED,SHIELD_OUTAGE,POWER_OUTAGE,TERRITORY_MAKE_UNCLAIMABLE,KICK_REASON,TINT_NAME,TINT,BAN_ACCOUNT_BY_PLAYERNAME,GIVE_SLOT,SHUTDOWN,WHITELIST_ACCOUNT,EXPLODE_PLANET_SECTOR,POPULATE_SECTOR,TELEPORT_SELF_HOME,DESPAWN_ALL,LAST_CHANGED,CHANGE_SECTOR_FOR_COPY,DESPAWN_SECTOR,EXPLODE_PLANET_SECTOR_NOT_CORE,CHANGE_SECTOR_COPY,SECTOR_CHMOD

 

[Benevolent27]

That's exactly a scenario where an /add_admin_allowed_command would be very useful.

For instance, we're looking for a means to grant players permissions via a configuration as simple as:
#REMOVE_ENTITY,REMOVE_ENTITY_DOC,CLEAR_OVERHEATING,SPAWN_WAVE

Instead of the current requirement to use and maintain/update something like this:
#SPAWN_CREATURE,SPAWN_CREATURE_MASS,CREATE_SPAWNER_TEST,EXECUTE_ENTITY_EFFECT,LIST_ADMINS,FACTION_DELETE,FACTION_LIST,GIVE_RECIPE,LIST_BANNED_IP,PLAYER_LIST,GIVE_CREDITS,GATE_DEST,STATUS,LIST_BANNED_NAME,SECTOR_SIZE,GIVE_HEAL_WEAPON,CREATURE_GOTO,INITIATE_WAVE,DELAY_SAVE,TELEPORT_TO,GIVE_METAITEM,GIVE_MARKER_WEAPON,TP_TO,CREATURE_IDLE,LIST_WHITELIST_IP,FACTION_LIST_MEMBERS,TELEPORT_UID_TO,GIVE_LASER_WEAPON,CREATURE_ANIMATION_STOP,CREATURE_SIT,BAN_IP,SHIP_INFO_SELECTED,FACTION_ADD_MEMBER,GIVEID,LIST_WHITELIST_NAME,WHITELIST_IP,DESTROY_ENTITY,UNBAN_IP,GIVE_ALL_ITEMS,FACTION_SET_ENTITY,GIVE,GIVE_ROCKET_LAUNCHER,SPAWN_ITEM,FACTION_SET_ALL_RELATIONS,FACTION_MOD_RELATION,GOD_MODE,LOAD_SYSTEM,TP,SIMULATION_AI_ENABLE,KICK,REMOVE_ADMIN,LIST_SHIPS,KILL_CHARACTER,GIVE_SNIPER_WEAPON,GIVE_POWER_SUPPLY_WEAPON,STOP_SHIP_AI,LIST_SHIPS,KILL_CHARACTER,GIVE_SNIPER_WEAPON,GIVE_POWER_SUPPLY_WEAPON,STOP_SHIP_AI,LIST_CONTROL_UNITS,CREATURE_ENTER_GRAVITY,DAYTIME,SIMULATION_SPAWN_DELAY,FACTION_DEL_MEMBER,DEBUG_ID,CREATURE_ANIMATION_START,ADD_ADMIN_DENIED_COMAND,BAN_NAME,WHITELIST_NAME,SERVER_MESSAGE_TO,GIVE_CATEGORY_ITEMS,SET_DEBUG_MODE,UNBAN_NAME,REFRESH_SERVER_MSG,FACTION_POINT_GIVE,SHIELD_DAMAGE,FORCE_SAVE,STRUCTURE_SET_MINABLE,SERVER_MESSAGE_BROADCAST,SHOP_RESTOCK,CHANGE_SECTOR_FOR,GIVE_LASER_WEAPON_OP,SIMULATION_INVOKE,BAN_IP_BY_PLAYERNAME,BREAK_SHIP,CLEAR_OVERHEATING_ALL,INVISIBILITY_MODE,TELEPORT_SELECTED_TO,CUBATOM_RANDOM_FILL,TELEPORT_SELF_TO,CREATURE_STAND_UP,DECAY,ADD_ADMIN,LIST_BANNED_ACCOUNTS,START_COUNTDOWN,STRUCTURE_SET_VULNERABLE,REMOVE_ADMIN_DENIED_COMAND,START_SHIP_AI,FACTION_REINSTITUTE,FACTION_MOD_MEMBER,REMOVE_SPAWNERS,LIST_ADMIN_DENIED_COMMANDS,UPDATE_SHOP_PRICES,FACTION_EDIT,FACTION_JOIN_ID,CREATURE_ROAM,FACTION_POINT_SET,SHOP_RESTOCK_FULL,IMPORT_SECTOR_BULK,IMPORT_SECTOR,MISSILE_DEFENSE_FRIENDLY_FIRE,LIST_WHITELIST_ACCOUNTS,FACTION_CREATE,FACTION_CREATE_AS,REPAIR_SECTOR,CREATURE_RENAME,DESTROY_UID,CHANGE_SECTOR,JUMP,FACTION_POINT_TURN,SET_GLOBAL_SPAWN,CHANGE_SECTOR_FOR_UID,CREATURE_SCRIPT,SHIP_INFO_UID,SHIP_INFO_NAME,TERRITORY_RESET,DESTROY_ENTITY_DOCK,SECTOR_INFO,LOAD_SECTOR_RANGE,RESTRUCT_AABB,GIVE_LOOK,WHITELIST_ACTIVATE,IGNORE_DOCKING_AREA,SEARCH,PLAYER_PROTECT,CLEAR_OVERHEATING,CREATE_TRADE_PARTY,PLAYER_INFO,SAVE,SAVE_UID,LOAD,FACTIO_SET_ID_MEMBER,SPAWN_ENTITY,SPAWN_ENTITY_POS,EXPORT_SECTOR,SHOP_RESTOCK_UID,FACTION_POINT_PROTECT_PLAYER,FACTION_CHECK,DEBUG_FSM_INFO,SET_SPAWN,SET_SPAWN_PLAYER,SHOP_INFINITE,BAN_ACCOUNT,SPAWN_MOBS,FACTION_POINT_ADD,SHOP_RESTOCK_FULL_UID,SPAWN_MOBS_LINE,EXPORT_SECTOR_BULK,FACTION_RESET_ACTIVITY,PLAYER_UNPROTECTED,DESTROY_UID_DOCKED,SHIELD_OUTAGE,POWER_OUTAGE,TERRITORY_MAKE_UNCLAIMABLE,KICK_REASON,TINT_NAME,TINT,BAN_ACCOUNT_BY_PLAYERNAME,GIVE_SLOT,SHUTDOWN,WHITELIST_ACCOUNT,EXPLODE_PLANET_SECTOR,POPULATE_SECTOR,TELEPORT_SELF_HOME,DESPAWN_ALL,LAST_CHANGED,CHANGE_SECTOR_FOR_COPY,DESPAWN_SECTOR,EXPLODE_PLANET_SECTOR_NOT_CORE,CHANGE_SECTOR_COPY,SECTOR_CHMOD

Point well made. lol

 

[Criss]

Yeah I bet AndyP has some input here. This would certainly help server owners.

 

[AndyP]

Correct, we are aware of the problem,
and plan to overhaul the command permission system at some point.
Adding a long list of denied commands is prone to errors (missing a new command)
and also hard to do in a human readable format.

We were thinking about different approaches for this.
Its not on high priority, but will be addressed, for sure.

- Andy

 

[Benevolent27]

Correct, we are aware of the problem,
and plan to overhaul the command permission system at some point.
Adding a long list of denied commands is prone to errors (missing a new command)
and also hard to do in a human readable format.

We were thinking about different approaches for this.
Its not on high priority, but will be addressed, for sure.

- Andy

It'd be nice too if there could be more than 1 type of privilaged user. Perhaps it could be configurable. Maybe the server admins add a group called "BUILD," which is set to add a + sign to the front of their name. We have "build" accounts on my server, StarSide, where players are given a sector far away from other players, locked into it, and then given creative mode. These "Build" accounts could then be given the permission to /remove_entity, /remove_entity_dock, etc. Think this might be viable too?

 

[Napther]

It'd be nice too if there could be more than 1 type of privilaged user. Perhaps it could be configurable. Maybe the server admins add a group called "BUILD," which is set to add a + sign to the front of their name. We have "build" accounts on my server, StarSide, where players are given a sector far away from other players, locked into it, and then given creative mode. These "Build" accounts could then be given the permission to /remove_entity, /remove_entity_dock, etc. Think this might be viable too?

Psssst, The COMMUNITY is Starside, the SERVER itself is called Shattered Skies; this distinction will become important soon...
Anyway, I agree. Unfortunately we need a way to allocate the Tab+F8 function too as, if this user has pirates spawn outside his sector, then sudddenly 1 Tab+F8 jump means there is an unlocked creative mode account running around with the ability to destroy homebases with 1 command.

There are upsides, and inevitable downsides to giving "standard (build) players" of the server the ability to do that. The least exploitable would be to give them the ability to admin-load ships in their OWN catalogue (IE, No need to buy blueprint), allow them to spawn pirates, and allow them to clear nearby pirate simulations/overheating ships.

Otherwise, better off heading over to single player, or to the NFD-B Server where all "players" are given creative mode and Admin rights and entrusted to not delete eachothers works and creations, since, its a BUILD server after all.

 

[Erth Paradine]

Psssst, The COMMUNITY is Starside, the SERVER itself is called Shattered Skies; this distinction will become important soon...
Anyway, I agree. Unfortunately we need a way to allocate the Tab+F8 function too as, if this user has pirates spawn outside his sector, then sudddenly 1 Tab+F8 jump means there is an unlocked creative mode account running around with the ability to destroy homebases with 1 command.

There are upsides, and inevitable downsides to giving "standard (build) players" of the server the ability to do that. The least exploitable would be to give them the ability to admin-load ships in their OWN catalogue (IE, No need to buy blueprint), allow them to spawn pirates, and allow them to clear nearby pirate simulations/overheating ships.

Otherwise, better off heading over to single player, or to the NFD-B Server where all "players" are given creative mode and Admin rights and entrusted to not delete eachothers works and creations, since, its a BUILD server after all.

If it's a build-only server (e.g. no PVE), set the following in server.cfg:
ENEMY_SPAWNING = false

You could also /sector_chmod noenter, noexit & peace on a player's immediately surrounding sectors to hinder both unplanned pirates spawns, and any unauthorized departures. Granting the ability to spawn and destroy spawns is possible, especially if you already have a build server config running; just adjust relevant permissions.

As for blueprint theft, I do wonder if something combined with the ACL change-ups suggested in this thread, and an expanded version of Read by Council - Hinder design theft would help you there.

 

[Benevolent27]

Psssst, The COMMUNITY is Starside, the SERVER itself is called Shattered Skies; this distinction will become important soon...
Anyway, I agree. Unfortunately we need a way to allocate the Tab+F8 function too as, if this user has pirates spawn outside his sector, then sudddenly 1 Tab+F8 jump means there is an unlocked creative mode account running around with the ability to destroy homebases with 1 command.

There are upsides, and inevitable downsides to giving "standard (build) players" of the server the ability to do that. The least exploitable would be to give them the ability to admin-load ships in their OWN catalogue (IE, No need to buy blueprint), allow them to spawn pirates, and allow them to clear nearby pirate simulations/overheating ships.

Otherwise, better off heading over to single player, or to the NFD-B Server where all "players" are given creative mode and Admin rights and entrusted to not delete eachothers works and creations, since, its a BUILD server after all.

About the difference between the community and server name. Pfft, whatever, everyone knows what I mean, don't be pedantic. :p

But yeah, I agree with your detailing of how permissions can be handled, also the caveats with TAB + F8.

I think one solution is to provide all of this functionality within a person's test sector. Allow admins to turn on certain commands and creative mode while they are within that sector (and by default for all players, so there would be no manual edits necessary, unless an admin decides to revoke these permissions for certain players). This would make things a lot easier for everybody. But I still think allowing groups with set permissions would be ideal, to allow multi-level admins, mods, and VIP's on servers. This is common in many games for a reason, because it works well.

 

[Chckn Wildstyle]

This needs to be implemented soon if there is to be any effective delegation of duty for any servers. Having server admins do anything and everything that comes up on the server is a quick way to have admins quit because of exorbitant amounts of time being poured into the server doing menial task. This, on top of an improved chmod system, is very much needed.

 

[spocklin]

Yes more admins please.