3.4 KiB
layout | title |
---|---|
page | Access Condition System (ACS) |
Access Condition System (ACS)
ENiGMA½ uses an Access Condition System (ACS) that is both familure to oldschool BBS operators and has it's own style. With ACS, SysOp's are able to control access to various areas of the system based on various conditions such as group membership, connection type, etc. Various touch points in the system are configured to allow for acs
checks. In some cases ACS is a simple boolean check while others (via ACS blocks) allow to define what conditions must be true for certain rights such as read
and write
(though others exist as well).
ACS Codes
The following are ACS codes available as of this writing:
Code | Condition |
---|---|
LC | Connection is local |
AGage | User's age is >= age |
ASstatus, AS[status,...] | User's account status is group or one of [group,...] |
ECencoding | Terminal encoding is set to encoding where 0 is CP437 and 1 is UTF-8 |
GM[group,...] | User belongs to one of [group,...] |
NNnode, NN[node,...] | Current node is node or one of [node,...] |
NPposts | User's number of message posts is >= posts |
NCcalls | User's number of calls is >= calls |
SC | Connection is considered secure (SSL, secure WebSockets, etc.) |
THheight | Terminal height is >= height |
TWwidth | Terminal width is >= width |
TM[themeId,...] | User's current theme ID is one of [themeId,...] (e.g. luciano_blocktronics ) |
TT[termType,...] | User's current terminal type is one of [termType,...] (ANSI-BBS , utf8 , xterm , etc.) |
IDid, ID[id,...] | User's ID is id or oen of [id,...] |
WDweekDay, WD[weekDay,...] | Current day of week is weekDay or one of [weekDay,...] where 0 is Sunday, 1 is Monday, and so on. |
AAdays | Account is >= days old |
BUbytes | User has uploaded >= bytes |
UPuploads | User has uploaded >= uploads files |
BDbytes | User has downloaded >= bytes |
DLdownloads | User has downloaded >= downloads files |
NRratio | User has upload/download count ratio >= ratio |
KRratio | User has a upload/download byte ratio >= ratio |
PCratio | User has a post/call ratio >= ratio |
MMminutes | It is currently >= minutes past midnight (system time) |
* Many more ACS codes are planned for the near future.
ACS Strings
ACS strings are one or more ACS codes in addition to some basic language semantics.
The following logical operators are supported:
!
NOT|
OR&
AND (this is the default)
ENiGMA½ also supports groupings using (
and )
. Lastly, some ACS codes allow for lists of acceptable values using [
and ]
— for example, GM[users,sysops]
.
Examples
NC2
: User must have called two more more times for the check to return true (to pass)ID1
: User must be ID 1 (the +op)GM[elite,power]
: User must be a member of theelite
orpower
user group (they could be both)ID1|GM[co-op]
: User must be ID 1 (SysOp!) or belong to theco-op
group!TH24
: Terminal height must NOT be 24
ACS Touch Points
The following touch points exist in the system. Many more are planned:
- Message conferences and areas
- File base areas
- Menus within
menu.hjson
. See Menu HJSON.
See the specific areas documentation for information on available ACS checks.