Ticket #1039 (closed defect: fixed)

Opened 1 year ago

Last modified 7 months ago

auto commands result in "unknown command"

Reported by: jane Assigned to: timothy
Priority: high Component: Colloquy (GUI)
Version: Latest 2.1 Severity: major
Keywords: auto connect command Cc:

Description

certain commands performed on-connect result in "unknown command" errors from the server, hence not being executed. e.g. "msg" results in such an error, while changing the "msg" to "privmsg" doesn't.

http://rafb.net/p/rh7aWV25.html 

[01:22am] jane|mb: same prob
[01:23am] akempgen: ok :)
[01:23am] jane|mb: 421: msg Unknown command
[01:23am] jane|mb: weird
[01:23am] akempgen: good to know
[01:24am] • jane|mb tries one more time
[01:24am] jane|mb: works now
[01:24am] jane|mb: privmsg jane test
[01:24am] jane|mb: freenode-connect CTCP REQUEST VERSION
[01:24am] jane|mb: JOIN #colloquy
[01:24am] jane|mb: CTCP REPLY freenode-connect VERSION Colloquy 2.1 ...
[01:24am] jane|mb: 505: Private messages from unregistered users are currently blocked...
[01:25am] jane|mb: sorry for the flood :S
[01:25am] • jane eyes nightstalker
[01:25am] nightstalker: ?
[01:25am] nightstalker: what did you change?
[01:25am] jane: 'msg jane test' to 'privmsg jane test'
[01:26am] nightstalker: mkay
[01:26am] nightstalker: but thats not a fix :)
[01:26am] jane: i know

Change History

09/18/07 11:10:40 changed by akempgen

from #1100:

I used the Startup commands (hope you know what i mean, below the Auto-Join Channels) für my AUTH but since the Colloquy update the command /msg Q@CServe.quakenet.org AUTH yyyyyy xxxxxxx doesent work.

QuakeNet?? replays: msg Q@CServe.quakenet.org AUTH yyyyyyyy xxxxxxxx 421: msg Unknown command

The command is correct, if i copy&and past him it works. If Colloquy disconnects and reconnects automatically, the Startup Commands work successfully.

09/22/07 02:53:36 changed by Argon

PRIVMSG does not work.

privmsg Q@CServe.quakenet.org AUTH MyFakeAcc? ******** Q NOTICE Unknown command. Type "/msg Q showcommands"

(follow-up: ↓ 4 ) 10/01/07 04:54:30 changed by blind_io

This seems to be a case of a case problem. When using '/msg' I doesn't work, but '/MSG' works.

(in reply to: ↑ 3 ) 10/02/07 13:31:27 changed by blind_io

Replying to blind_io:

This seems to be a case of a case problem. When using '/msg' I doesn't work, but '/MSG' works.

Replying to myself here. It seems I was wrong. Testing yesterday suggested that the lower case was the problem, but today it won't work. Yesterday while testing, I just disconnected from the server, not quitting Colloquy as was the case today.

10/15/07 01:41:48 changed by timothy

  • status changed from new to assigned.

THis is only happening for connections that happen on launch. I think the standard commands plugin is not loaded in time to handle the /msg.

10/15/07 01:56:33 changed by timothy

  • status changed from assigned to closed.
  • resolution set to fixed.

Fixed in [3760].