The new home for slackchat is www.javaop.com/~tmp/. Much thanks to iago.
No pictures :( and last time I tried it failed to run on my lappy :(
Sexy. slackchat_fbsd.tar.gz is missing! :p
Thats because he knew you would click it.
Thanks tmp! (For getting this back up, not for giving newby a 404, which I also thank you for =p)
EDIT -
Here, let me do some cross-platform reporting for you. =p
joe@JoeMomma:~/slackchat/src $ make
gcc -I./include -Wall -ggdb -c main.c
main.c:9:20: curses.h: No such file or directory
main.c: In function `main':
main.c:160: warning: implicit declaration of function `initscr'
main.c:161: warning: implicit declaration of function `has_colors'
main.c:162: warning: implicit declaration of function `endwin'
main.c:166: warning: implicit declaration of function `start_color'
main.c:166: error: `OK' undeclared (first use in this function)
main.c:166: error: (Each undeclared identifier is reported only once
main.c:166: error: for each function it appears in.)
main.c:172: warning: implicit declaration of function `init_pair'
main.c:172: error: `COLOR_WHITE' undeclared (first use in this function)
main.c:172: error: `COLOR_BLACK' undeclared (first use in this function)
main.c:173: error: `COLOR_BLUE' undeclared (first use in this function)
main.c:175: warning: implicit declaration of function `attrset'
main.c:175: warning: implicit declaration of function `COLOR_PAIR'
main.c:175: error: `A_BOLD' undeclared (first use in this function)
main.c:178: warning: implicit declaration of function `move'
main.c:178: error: `COLS' undeclared (first use in this function)
main.c:179: warning: implicit declaration of function `printw'
main.c:180: warning: implicit declaration of function `refresh'
main.c:181: warning: implicit declaration of function `attroff'
main.c:251: error: `LINES' undeclared (first use in this function)
main.c:260: warning: implicit declaration of function `keypad'
main.c:260: error: `stdscr' undeclared (first use in this function)
main.c:260: error: `TRUE' undeclared (first use in this function)
main.c:261: warning: implicit declaration of function `noecho'
main.c:263: warning: implicit declaration of function `getch'
main.c:271: warning: implicit declaration of function `clrtoeol'
main.c:370: warning: implicit declaration of function `echo'
main.c: In function `mystrcat':
main.c:472: error: `va_list' undeclared (first use in this function)
main.c:472: error: parse error before "argptr"
main.c:473: warning: implicit declaration of function `va_start'
main.c:473: error: `argptr' undeclared (first use in this function)
main.c:475: warning: implicit declaration of function `va_end'
main.c: In function `updatestatusbar':
main.c:494: error: `LINES' undeclared (first use in this function)
main.c:496: error: `A_STANDOUT' undeclared (first use in this function)
main.c: In function `pscr':
main.c:514: error: `va_list' undeclared (first use in this function)
main.c:514: error: parse error before "argptr"
main.c:515: error: `argptr' undeclared (first use in this function)
main.c:520: error: `COLS' undeclared (first use in this function)
main.c:540: error: `LINES' undeclared (first use in this function)
main.c:544: warning: implicit declaration of function `instr'
main.c:548: error: `A_BOLD' undeclared (first use in this function)
main.c: In function `ParseD2Stats':
main.c:1216: error: `bool' undeclared (first use in this function)
main.c:1216: error: parse error before "female"
main.c:1218: error: `female' undeclared (first use in this function)
main.c:1218: error: `true' undeclared (first use in this function)
main.c:1221: error: parse error before "expansion"
main.c:1252: error: `expansion' undeclared (first use in this function)
main.c:1258: error: `false' undeclared (first use in this function)
make: *** [main.o] Error 1
/emotear
EDIT -
Uh, yeah. Kinda forgot something really important. Thats Ubuntu 4.10: Warty Warthog
Quote from: Ergot on September 25, 2005, 10:44:28 PM
No pictures :( and last time I tried it failed to run on my lappy :(
He'd probably be happy if he was given more details
Like my post? =p
Ergot, you put the config in the wrong place I'm pretty sure. I remember newby telling me about your error. I'll have to take some new screenshots, last ones were lost. Sorry.
You're so right it's not even funny ^_~. I'll mess with that later.
What about the mIRC tunnel? If you don't have a backup, I can throw together one I think.
Oh, and you should be able to get x0r.ca synced, right? That domain man..
Ah the mIRC tunnel is gone. I made that a long time ago and I think mIRC has ssl support now. I'm pretty sure the domain is gone ;P It's all good, this place came with a door mat.
Quik get the domain! (Literally).
Nice job on the bot tmp. :)
<tmp> first cross platform tester!
<joe> Sweet, do I get an award or something?
<joe> lol
<tmp> maybe
<tmp> i'll look into plaques
<tmp> brb
<joe> haha
I just ran dist-upgrade on my box, but I doubt that affected anything. I installed libcurses-dev and it compiled just fine. I'm ransacking your site for the configuration format though. =p
EDIT -
Ok, so I was running Ubuntu: Warty Warthog. Then I dist-upgraded. I suppose I'm running Ubuntu: Hoary Headgehog right now. Anyhow, I installed libcurses-dev and it works. I didn't find the config on your site, but newby helped me out.
joe@JoeMomma:~ $ cat .slackchatrc
nick=Joe[e2]
password=haha no
server=uswest.battle.net
cdkey=133713371337137
cdkeyname=JoeTheOdd
home=Op x86
port=6112
There is a default config file in the tarball distributed on the site. The configuration file is located at slackchat/.slackchatrc upon extraction. You might not know that files prepended with a . are 'invisible' and are only viewed when passing the -a flag to ls ? (ls -a)
PS
this information is all in the README
*cough*
I skimmed the readme, saw nothing about configuration. I did see that it requires curses though. Anyhow, great bot. Got it working now.
Quote
At this point, a fully functional linked/compiled binary will be located at slackchat/slackchat. A default configuration file can be found at slackchat/.slackchatrc. Simply edit the configuration file to your liking, copy it to your home directory, run the slackchat binary to begin chatting! The binary will not connect unless you adjust the configuration file appropriately.
slackchat README
;P
I know you meant the slackchat readme =p. I just skimmed and didn't read it.
Anyhow, I'm working on some suggestions for it. =)SLACKCHAT SUGGESTIONS:
- Plugin system
- - Events raised in external files, such as
- - - UserInChannel
- - - UserJoins
- - - UserLeaves
- - - UserTalks
- - - UserEmote
- - - BnetError
- - - BnetInfo
- Internal commands
- - /quit - Quit the bot
- Verbosity
- - Current -v changes to -vv (very verbose)
- - New -v prints packet names, but not hexdumps.
- Commands:
- - !say
- - !yell (UCase say)
- - !extend (A d d s s p a c e s)
- - !quit
- - !xmms
- - !math (!math 3+5 :: 8 ) EDIT: Ugh. Stupid 8.) smily. Heh.
- - Moderation
- - - !lock (channel lockdown)
- - - !kick
- - - !ban
- Configuration
- - If variables are missing, prompt for them (I may write a shellscript to do this?)
- - For the commands, triger variable?
- - Alternate hash path
- - Alternate verbyte
- - Alternate verhash (or does CheckRevision find this?)
- Access system (for use with commands)
- - Flags system? (All levels inherit the commands from below levels)
- - - M = Master (All commands)
- - - O = Operator (operator commands, kick, ban, etc)
- - - T = Talker (don't laugh at me!) (say, yell, extend)
- - - S = Safelisted (Immune to kick, ban, except from M, and always lock)
- - Numerical access?
- - - 100: see M
- - - 80: See O
- - - 50: See T
- - - 10: See S
- GTK front end
- - HTTP server (streaming HTML output, like JavaOp1)
Enjoy!
EDIT -
Note: All of these but the verbosity (and the plugin system itself) could be implemented through the plugin system. =p
Note to self: I love double-posting.
joe@JoeMomma:~/dev/sh $ ./slackchatconf.sh
Enter your battle.net server:
tassadar.battle.net
Enter your username:
x86
Enter your password:
haha no
Enter your CDKey:
haha no
Enter your home channel:
Op x86
Finished configuring slackchat. Put this in ~/.slackchatrc
nick=x86
password=haha no
server=tassadar.battle.net
cdkeyname=x86
home=Op x86
port=6112
Source:
#!/bin/sh
# slackchat configuration script
# author: joe[e2]
echo "Enter your battle.net server: "
read server < /dev/tty
echo "Enter your username: "
read username < /dev/tty
echo "Enter your password: "
read password < /dev/tty
echo "Enter your CDKey: "
read cdkey < /dev/tty
echo "Enter your home channel: "
read homechannel < /dev/tty
echo " "
echo "Finished configuring slackchat. Put this in ~/.slackchatrc"
echo " "
echo "nick="$username
echo "password="$password
echo "server="$server
echo "cdkeyname="$username
echo "home="$homechannel
echo "port=6112"
Be sure to chmod +x slackchatconf.sh (or whatever you name it). This doesn't print it to the file. Get unlazy and do it yourself. =)
EDIT -
Newby's being like microsoft again and discouraging people other than professionals to even attempt to write code. He wants me to make it write to the file but refuses to help me. Expect a "fixed" version from him by tomorrow morning, because hes godly like that.
Thanks, Joe. Most of those sound like good ideas. I don't think I'd ever implement /quit though. Have you tried ctrl+c ? IMO (and probably most unix users) ctrl+c is more standard and instinctive.
Also, it is open source. If you learn some C you could probably add a lot of that functionality on your own. I wouldn't mind giving you pointers on where to start with what and if you actually got the ball rolling you could maintain the project/website for all I care.
PS
Probably the closest thing to what you want for that script would be something like this:
echo "nick="$username >> ~/.slackchatrc
Quote from: mynameistmp on September 28, 2005, 03:25:06 AM
echo "nick="$username >> ~/.slackchatrc
You'd end up with 2 "nick=" lines, though. You might need to pipe it through sed then back to the file.
Although it's an ugly way of doing it, I asume his parser will load the second value (which is same as the first anyhow) as the nick. I'll see if I have time to look into it tomorrow after school.
But yeah, I guess Ctrl+C works too. I don't even know why I suggested that. =p
And what do you have to say about the plugin system? I thought that was a little bit out of the question, considering the slackchat principles (barebones, it works, nothing more), but I thought I'd suggest it.
Also, STAR. People might not want SEXP. =p
I actually wrote a script today to edit a line out of /etc/hosts. It could also be applied to this:
cp /etc/hosts /etc/hosts.bak
sed "s/.*# added by fixhosts.sh//g" /etc/hosts.bak | uniq > /etc/hosts
That's not totally perfect, but it works for my purposes. Grep would have worked better, but I had a mind blank. The uniq is to remove duplicate entries/blank lines.
Quote from: iago on September 28, 2005, 11:42:16 PM
I actually wrote a script today to edit a line out of /etc/hosts. It could also be applied to this:
cp /etc/hosts /etc/hosts.bak
sed "s/.*# added by fixhosts.sh//g" /etc/hosts.bak | uniq > /etc/hosts
That's not totally perfect, but it works for my purposes. Grep would have worked better, but I had a mind blank. The uniq is to remove duplicate entries/blank lines.
Don't you mean my purpose ^^ <3.
Quote from: iago on September 28, 2005, 03:37:45 PM
Quote from: mynameistmp on September 28, 2005, 03:25:06 AM
echo "nick="$username >> ~/.slackchatrc
You'd end up with 2 "nick=" lines, though. You might need to pipe it through sed then back to the file.
I think you mean he'd have a duplicate of every line if the file already existed. Otherwise I don't understand what you mean. He could do:
echo "nick="$username > ~/.slackchatrc
echo "whatever="$whatever >> ~/.slackchatrc
That should work fine.
I know this topic is long dead now but I was just playing around slackchat compiles on debian etch, so i'm currently re-adding the d2 cdkey decode functions and am shifting the client over to login on d2 for some practice on linux in c/c++..
If this is something anyone would want when it's done, I can post it just ask.
I'd like a copy of slackchat's source code. I'd be interested in updating stuff, cleaning stuff up, and somewhat maintaining a VC++ fork of it. I know it's not slackchat if it's build to Win32, but eh.
Quote from: Joe[ix86] on December 15, 2007, 06:49:58 PM
I'd like a copy of slackchat's source code.
http://www.javaop.com/~tmp/slackchat.tar.gz ::)