Anope Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001630Anope Stable (2.0.x series)[All Projects] Generalpublic2014-12-20 03:222015-03-12 14:05
Assigned To 
PlatformOSOS Version
Summary0001630: Changing flags causes chanserv to incorrectly change statuses in a channel
Descriptionnick1 has +qo in a channel (he is the founder). He and his team have @team/<nick> vhosts. If he does `/msg chanserv flags #channel modify *@team/* +H`, chanserv will +h-qo nick1 in #channel.
`/msg chanserv up #channel` immediately after that will give nick1 +qo as before.
On rejoin, nick1 gets +qo as normal.
Additional Informationnick1 is not on the access list, because he is the founder. I'm guessing that chanserv only looks at the access list when deciding which nicks to change status after flags are modified.

I have a pretty typical configuration, running Anope 2.0.1, build 0000002
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
Adam (administrator)
2014-12-20 05:36

No this isn't really a bug. I think sometime in the future we will split founder out to its own privilege instead of having the special case it is now.
emerson (reporter)
2014-12-20 05:25

Yea, you're right, he gets +h on rejoin.

That does make sense, now that you explain it, and I can always !up to get +qo back.

I guess that means it's not really a bug :) I'll let you close it, since I'm not familiar with this interface.

Thanks for your prompt response, too!
Adam (administrator)
2014-12-20 04:54

And, then if you really want the founder to be +qo you would explicitly add them to the access list with the appropriate privileges.
Adam (administrator)
2014-12-20 04:50

Are you sure that when nick1 rejoins he gets +qo? We have it set now so that if an access entry matches the founder, the modes on-join they receive are that of the access entry and not the default +qo because they are founder, because otherwise it wouldn't be possible to give the founder any other modes without disabling the levels which globally affects the channel. The intended behavior of this is to have *@team/* +H give the founder +h and also give them +h if they were to part and rejoin.

- Issue History
Date Modified Username Field Change
2014-12-20 03:22 emerson New Issue
2014-12-20 04:50 Adam Note Added: 0006687
2014-12-20 04:54 Adam Note Added: 0006689
2014-12-20 05:25 emerson Note Added: 0006690
2014-12-20 05:36 Adam Note Added: 0006691
2015-03-12 14:05 Adam Status new => closed
2015-03-12 14:05 Adam Resolution open => @100@

Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker