Anope Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001295Anope Development (1.9.x series)Otherpublic2011-07-31 02:212011-08-08 06:30
ReporterRobby 
Assigned ToLEthaLity 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformLinux, i686OSFedoraOS Version10
Product Version 
Target VersionFixed in Version1.9.x-GIT 
Summary0001295: Non-existant SET commands/parameters produce wrong/non-uniform output
DescriptionFor example in NickServ:
<Robby> SET BOGUS ON
-NickServ- Unknown SET option /msg BOGUS.

The same goes for ChanServ:
<Robby> SET #Dotcom BOGUS ON
-ChanServ- Unknown SET option /msg BOGUS.
-ChanServ- /msg ChanServ HELP SET for more information.

And also MemoServ is affected by this:
<Robby> SET BOGUS ON
-MemoServ- Unknown SET option /msg BOGUS.
-MemoServ- /msg MemoServ HELP SET for more information.

"/msg" Should be removed from the line that says it is unknown.

OperServ says this:
<Robby> SET BOGUS ON
-OperServ- Unknown option BOGUS.

Perhaps to be uniform with NickServ, ChanServ and MemoServ it should also say this instead:
-OperServ- Unknown SET option BOGUS.

Also not that ChanServ and MemServ suggests to do:
/msg ChanServ HELP SET for more information.
and:
/msg MemoServ HELP SET for more information.
whereas NickServ and OperServ do not, perhaps that should also be added to be uniform.

Perhaps even HostServ and BotServ have these problems if they have a SET command, but I don't know because I don't have those two services enabled.

Anope version: 1.9.4
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0005912)
LEthaLity (manager)
2011-08-08 06:30

Fixed in 286a9edb1ec

Also fixed some of the BotServ set options giving the wrong param eg. botnick instead of channel.

All of them should now respond with the Syntax, and the help command, as NickServ and ChanServ were already doing since this bug was posted.
(0005888)
Robby (manager)
2011-07-31 06:03

I did some further testing with 1.9 head (f29c88b) and in that version (in which the syntax has changed), MemoServ and OperServ is still behaving like in 1.9.4, but NickServ and ChanServ spit out messages like this now:
<Robby> SET BOGUS ON
-NickServ- Syntax: SET option parameters
-NickServ- /msg NickServ HELP SET for more information.
<Robby> SASET BOGUS Robby ON
-NickServ- Syntax: SASET option nickname parameters
-NickServ- /msg NickServ HELP SASET for more information.

<Robby> SET BOGUS #Dotcom ON
-ChanServ- Syntax: SET option channel parameters
-ChanServ- /msg ChanServ HELP SET for more information.
<Robby> SASET BOGUS #Dotcom ON
-ChanServ- Syntax: SASET option channel parameters
-ChanServ- /msg ChanServ HELP SASET for more information.

As you can see, they don't mention anymore that the setting is incorrect. If this is intended, ok, but to be uniform... :P

- Issue History
Date Modified Username Field Change
2011-07-31 02:21 Robby New Issue
2011-07-31 06:03 Robby Note Added: 0005888
2011-08-08 04:02 LEthaLity Assigned To => LEthaLity
2011-08-08 04:02 LEthaLity Status new => assigned
2011-08-08 06:30 LEthaLity Note Added: 0005912
2011-08-08 06:30 LEthaLity Status assigned => resolved
2011-08-08 06:30 LEthaLity Fixed in Version => 1.9.x-GIT
2011-08-08 06:30 LEthaLity Resolution open => fixed


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker