The irc.js didn't support a password "override" (e.g. via command-line), i.e. it always sent to current user's password via the >IRC "PASS" message upon connecting to a server. I just committed a change to allow the sysop to override the password >sent via the '-p' command-line option to irc.js. Please let me know how that works for you.
!EXEC ?irc.js -p "IRCPASSWORD" but this returned some js variable type errors (and, considering my very poor coding attitude, I did not insist).
- the IRC Module 1.62 starts but it does return the error: !Javascript irc.js line 126: Error: can't convert irc-port to an integer
Nope, irc.js is untouched in the exec dir and this is the copy of the whole section:
Anyway, the error seems to imply there was an additional argument provided after the "-p <password>" on the irc.js command-line. I'll re-test the -p option myself and make sure I didn't introduce a bug there, but the code looks okay at a glance.
The error message you quoted said "can't convert irc-port to an integer" - was that error actually copy/pasted, literally, or did you retype it (possibly with a typo)? The reason I ask is "irc-port" does not exist in irc.js, but "irc_port" does (underscore, not dash).
I just ran the current exec/irc.js using the "exec" sysop command: "?irc.js -p password" and there was no error - ran as expected.
The error message you quoted said "can't convert irc-port to an integer" - was that error actually copy/pasted, literally, or did you retype it (possibly with a typo)? The reason I ask is "irc-port" does not exist in irc.js, but "irc_port" does (underscore, not dash).
Yes, a typo, since I rewrited the error shown in Syncterm.
Sysop: | Rusel |
---|---|
Location: | Colchester, Essex. UK |
Users: | 3 |
Nodes: | 4 (0 / 4) |
Uptime: | 58:31:36 |
Calls: | 51 |
Messages: | 9,710 |