While I can somewhat agree with this explanation I still have to point out the following:
If we still assume that user is:
test:Brax!*@*
Then considering that the user has this hidden general access level along with the specified named level the following should trigger as well:
ON 1:TEXT:*:#: { echo Level: $ulevel }
However this fails to trigger despite the user having this hidden general access level along with named level.
If I quote from help:
Named Levels
You can also used named levels which work the same way as a specific level but are easier to understand and read than a number.
If according to help the named levels are supposed to work same way as numbered levels then it should be safe to assume that one can use them the same way without having to take into account that some undocumented "feature" kicks in someplace.
User List
In the Users section you can specify a list of users and their access levels using the format: <level1,level2,...,levelN>:<useraddress>
3,5,6:nick!user@mirc.com
The first level is a general access level, which means that the user can access all levels equal to or less than 3. All the other levels are levels that an event must specifically have to allow a user to access it.
Continuing on:
Lets set user:
10:Brax!*@*
ON 1:TEXT:*:#: { echo Level: $ulevel } >> Level: 10
ON *:TEXT:*:#: { echo Level: $ulevel } >> Level: 10
If $ulevel returns the user level that was matched for the currently triggered event.
Then:
test:Brax!*@*
ON 1:TEXT:*:#: { echo Level: $ulevel } >> The user who typed something is not level 1 so it shouldnt match (with numeric levels it will match level 10 user since 1 < 10)
ON *:TEXT:*:#: { echo Level: $ulevel } >> The user who typed something is level test so it should say that $ulevel is test instead of saying that $ulevel is 1
/ulist <1
Returns all named levels (Less than 1)
Which means that 'test < 1'
---------
Maybe im wrong but considering that with numbered levels you can also use expressions like < > (less/greater than) then it sort of seems like the original intention was to keep the userlevels numbered only. But afterwards the named levels were also added and something just "broke".
Since its possible to use $level($fulladdress) in events (which will return the real levels as they are in userlist) it isnt really game breaker but still quite unexpected mess.
If current behavior is really not a bug and indeed an intended behavior then perhaps this should be documented better so there wont be any confusion.
----
As a sidenote... who knows maybe if I get some sleep I might see the logic in it and will be embarrassed about the long rant.
