Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Ribose

#1
You can now use the binaries in the source tree (may not work due to different distributions having different ABI versions of libgmp available!) on Linux, or if that doesn't work, I detailed a very simple 2-command process for compiling it on Linux (from what I can tell it works on both Fedora and Ubuntu both 32 and 64 bit), see here.
#2
Download
Get it on Google Code (link)

Install
To install for Windows/Pidgin users, just run the featured installer.

(Re)start Pidgin, and make a new account.

To install on Linux, you'll have to compile from source, see the Setup wiki page on Google Code.

I do not know whether it works on Adium, but it should!

Changelog
Quote
v0.8.0: SRP Version & Bug Fixes
  • Added: Warcraft III local SRP support. Requires libgmp (included in installer). You won't send your passwords to BNLS ever again!
  • Fixed: Non UTF-8 messages will not crash you.
  • Fixed: A crash that occurs when connection was lost or you were unable to connect to BNLS.
  • Fixed: CD-Key decoding issues.
  • Fixed crash on friend remove/buddy remove
  • Fixed: more issues than I can remember. Come on! Half of them were made months ago...
  • Changed: Use bnls.net as default BNLS server.
  • Updated the build system. I got around to actually writing my own Makefile that does everything you need for this small project... doesn't really affect users of the Windows installer though.
v0.7.2: "Unnamed Release"
  • It should now be compilable without modification on Linux.
  • Fixed a bug where the "hide mutual friend status-change messages" option didn't hide messages on other gateways.
  • Updated CD-Key error code and added an informative message for ghosting. If you get "CD-key in use" with your own username, you will get a different error and Pidgin will automatically reconnect you as if you had a network connection error.
  • Updated Windows installer.
v0.7.1: "Small Bugfix Release"
  • Fixed: A couple possible crashes during logon if BNLS connection fails or you are IPBanned from Battle.net.
  • Fixed: Now correctly reports NLS revision to BNLS servers. This fixes "incorrect password" when using a JBLS server for WarCraft III logon
v0.7.0: "Installer and WarCraft III Release"
  • Added: Warcraft III support.
  • Added: Do not disturb mode is now correctly updated by your Pidgin status.
  • Added: "User is away" warning and "User is unavailable" error on IM (whisper) are now correctly shown in the IM and not in the channel.
  • Added: EID_ERRORs in channels now appear red instead of black.
  • Added: "X is away (away message)" is now displayed as an auto-response! "X <AUTO-RESPONSE>: Away (away message)".
  • Added: Warcraft III and Diablo channel user stats are now parsed.
  • Fixed: From the room list window, if you click "Join Channel" you will crash.
  • Fixed: Jailout's RBNETD (uswest.bnet.cc) will give you a blank username on logon.
  • Fixed: 26-character keys will no longer IPBan you.
  • Fixed: Certain new StarCraft keys will no longer IPBan you.
  • Fixed: If you have a channel "persisted" or you are in it and Pidgin doesn't know and you reopen/"rejoin" it, the channel user list is emptied.
  • Fixed: If you are in channel A with user X and you move to channel B then do Buddies > Get User Info... on that user X, their user information and stats will be shown as if they are in the current channel.
  • Fixed: User ban, kick, and unban messages will now always appear in the channel and never in an IM.
  • Fixed: Whisper commands open a new IM and show your sent whisper.
v0.6.0: "Public Release 1"
  • This is the first release, so nothing "changed" since the last one.

Screenshots and Features
See this topic for screenshots and the current supported features.

Notes
  • Trying to create accounts does not function correctly at this time. You may make the account hard to use if attempted.
Usage notes
You will have to use a valid BNLS ("Logon Server") and CD-key for the selected client, see the Advanced tab.

Notice: WarCraft III support NO LONGER sends passwords to BNLS. I finally implemented local SRP!

To join a channel after logging on, use the Buddies -> Join a Chat. You can then make it your "home channel" (as termed by other bots) by adding the chat to your buddy list with the setting "auto-join" checked.

All standard Battle.net commands are directed to Battle.net through libpurple's command processor. If you want to use a non-standard command (ex. PvPGN), you have to use libpurple's /say command, example: /say /ann sometext. You can also bypass it by sending multiple messages at once using CTRL+ENTER. I have left the command system there so that your libpurple or Pidgin plugins can then add commands without them being bypassed by the protocol. Also, it allows the plugin to do the proper modification to certain commands for Diablo II (ex. /whois user -> /whois *user).

Post comments and ideas, please.
#3
Suggestions / Re: Open Source?
February 17, 2011, 06:22:31 PM
StealthBot scripts are all in VBScript (definitely not VB6). Some people have occasionally made external DLLs that scripts could use to access more features (I've made one for a 2.7 beta before Winsock was available to scripts, but it was in VB6). I'm not sure why you'd want to program for that bot anymore, there is basically nobody developing it anymore. Also, why the talk of C++ at all when dealing with StealthBot?

StealthBot 2.7 had the best scripting system I've ever seen for a bot, if you ignore that it only supports VBScript (without some complex stuff). To be comparable, I think a bot should externalize everything and have it script-able or accessible via DLL plugin, and still be efficient (StealthBot had problems with speed and scripts, which I attribute to VB6 and VBs so I see no worry if this is done with C/C++ bot and DLL plugins).

By the way, I advocate free open source software, but you can go ahead and do whatever you want with your code.
#4
Quote from: Ribose on January 28, 2011, 10:39:32 PM
Download
Get it on Google Code (link)

Install
To install for Windows/Pidgin users, just run the installer.

(Re)start Pidgin, and make a new account.

To install for the many other configurations (OSX/Adium, Linux/Pidgin, Linux/Finch, etc), you'll have to compile it yourself at this time, since I have no idea whether they work yet.

Changelog
Quotev0.7.0: "Installer and WarCraft III Release"
  • Added: Warcraft III support.
  • Added: Do not disturb mode is now correctly updated by your Pidgin status.
  • Added: "User is away" warning and "User is unavailable" error on IM (whisper) are now correctly shown in the IM and not in the channel.
  • Added: EID_ERRORs in channels now appear red instead of black.
  • Added: "X is away (away message)" is now displayed as an auto-response! "X <AUTO-RESPONSE>: Away (away message)".
  • Added: Warcraft III and Diablo channel user stats are now parsed.
  • Fixed: From the room list window, if you click "Join Channel" you will crash.
  • Fixed: Jailout's RBNETD (uswest.bnet.cc) will give you a blank username on logon.
  • Fixed: 26-character keys will no longer IPBan you.
  • Fixed: Certain new StarCraft keys will no longer IPBan you.
  • Fixed: If you have a channel "persisted" or you are in it and Pidgin doesn't know and you reopen/"rejoin" it, the channel user list is emptied.
  • Fixed: If you are in channel A with user X and you move to channel B then do Buddies > Get User Info... on that user X, their user information and stats will be shown as if they are in the current channel.
  • Fixed: User ban, kick, and unban messages will now always appear in the channel and never in an IM.
  • Fixed: Whisper commands open a new IM and show your sent whisper.
v0.6.0: "Public Release 1"
  • This is the first release, so nothing "changed" since the last one.

Screenshots and Features
See this topic for screenshots and the current supported features.

Notes
  • Trying to create accounts does not function correctly time. You may make the account hard to use if attempted.
Usage notes
You will have to use a valid BNLS ("Logon Server") and CD-key for the selected client, see the Advanced tab.

Warning: WarCraft III support sends your passwords in plain text to the BNLS server at this time. Choose a server you trust until I finally get proper SRP support...

To join a channel after logging on, use the Buddies -> Join a Chat. You can then make it your "home channel" (as termed by other bots) by adding the chat to your buddy list with the setting "auto-join" checked.

All standard Battle.net commands are directed to Battle.net through libpurple's command processor. If you want to use a non-standard command (ex. PvPGN), you have to use libpurple's /say command, example: /say /ann sometext. You can also bypass it by sending multiple messages at once using CTRL+ENTER. I have left the command system there so that your libpurple or Pidgin plugins can then add commands without them being bypassed by the protocol. Also, it allows the plugin to do the proper modification to certain commands for Diablo II (ex. /whois user -> /whois *user).

Post comments and ideas, please.
#5
Download
Get it on Google Code (link)

Install
To install for Windows/Pidgin users, just run the installer.

(Re)start Pidgin, and make a new account.

To install on linux, find the libbnet.so file in the SVN trunk and place it in /usr/lib/pidgin/libbnet.so (for Pidgin) or /usr/lib/finch/libbnet.so (for Finch). I'll figure out a package for it later...

To install for the many other configurations (OSX/Adium, etc), you'll have to compile it yourself at this time, since I have no idea whether they work yet.

Changelog
Quotev0.7.1: "Small Bugfix Release"
  • Fixed: A couple possible crashes during logon if BNLS connection fails or you are IPBanned from Battle.net.
  • Fixed: Now correctly reports NLS revision to BNLS servers. This fixes "incorrect password" when using a JBLS server for WarCraft III logon
v0.7.0: "Installer and WarCraft III Release"
  • Added: Warcraft III support.
  • Added: Do not disturb mode is now correctly updated by your Pidgin status.
  • Added: "User is away" warning and "User is unavailable" error on IM (whisper) are now correctly shown in the IM and not in the channel.
  • Added: EID_ERRORs in channels now appear red instead of black.
  • Added: "X is away (away message)" is now displayed as an auto-response! "X <AUTO-RESPONSE>: Away (away message)".
  • Added: Warcraft III and Diablo channel user stats are now parsed.
  • Fixed: From the room list window, if you click "Join Channel" you will crash.
  • Fixed: Jailout's RBNETD (uswest.bnet.cc) will give you a blank username on logon.
  • Fixed: 26-character keys will no longer IPBan you.
  • Fixed: Certain new StarCraft keys will no longer IPBan you.
  • Fixed: If you have a channel "persisted" or you are in it and Pidgin doesn't know and you reopen/"rejoin" it, the channel user list is emptied.
  • Fixed: If you are in channel A with user X and you move to channel B then do Buddies > Get User Info... on that user X, their user information and stats will be shown as if they are in the current channel.
  • Fixed: User ban, kick, and unban messages will now always appear in the channel and never in an IM.
  • Fixed: Whisper commands open a new IM and show your sent whisper.
v0.6.0: "Public Release 1"
  • This is the first release, so nothing "changed" since the last one.

Screenshots and Features
See this topic for screenshots and the current supported features.

Notes
  • Trying to create accounts does not function correctly time. You may make the account hard to use if attempted.
Usage notes
You will have to use a valid BNLS ("Logon Server") and CD-key for the selected client, see the Advanced tab.

Warning: WarCraft III support sends your passwords in plain text to the BNLS server at this time. Choose a server you trust until I finally get proper SRP support...

To join a channel after logging on, use the Buddies -> Join a Chat. You can then make it your "home channel" (as termed by other bots) by adding the chat to your buddy list with the setting "auto-join" checked.

All standard Battle.net commands are directed to Battle.net through libpurple's command processor. If you want to use a non-standard command (ex. PvPGN), you have to use libpurple's /say command, example: /say /ann sometext. You can also bypass it by sending multiple messages at once using CTRL+ENTER. I have left the command system there so that your libpurple or Pidgin plugins can then add commands without them being bypassed by the protocol. Also, it allows the plugin to do the proper modification to certain commands for Diablo II (ex. /whois user -> /whois *user).

Post comments and ideas, please.
#6
Battle.net Pidgin (libpurple) Plugin / Google Code
February 06, 2011, 04:35:59 AM
Now hosting on Google Code. SVN is so much more suited for open source. Sorry Myst.

http://code.google.com/p/pidgin-libbnet/

Anyone is still welcome to post feedback in this forum (new topic button).
#7
Download
Windows Installer
Linux RPM - coming soon
Linux DEB - coming soon
Source - coming soon

Install
To install for Windows/Pidgin users, just run the installer.

(Re)start Pidgin, and make a new account.

To install for the many other configurations (OSX/Adium, Linux/Pidgin, Linux/Finch, etc), you'll have to compile it yourself at this time, since I have no idea whether they work yet.

Changelog
Quotev0.7.0: "Installer and WarCraft III Release"
  • Added: Warcraft III support.
  • Added: Do not disturb mode is now correctly updated by your Pidgin status.
  • Added: "User is away" warning and "User is unavailable" error on IM (whisper) are now correctly shown in the IM and not in the channel.
  • Added: EID_ERRORs in channels now appear red instead of black.
  • Added: "X is away (away message)" is now displayed as an auto-response! "X <AUTO-RESPONSE>: Away (away message)".
  • Added: Warcraft III and Diablo channel user stats are now parsed.
  • Fixed: From the room list window, if you click "Join Channel" you will crash.
  • Fixed: Jailout's RBNETD (uswest.bnet.cc) will give you a blank username on logon.
  • Fixed: 26-character keys will no longer IPBan you.
  • Fixed: Certain new StarCraft keys will no longer IPBan you.
  • Fixed: If you have a channel "persisted" or you are in it and Pidgin doesn't know and you reopen/"rejoin" it, the channel user list is emptied.
  • Fixed: If you are in channel A with user X and you move to channel B then do Buddies > Get User Info... on that user X, their user information and stats will be shown as if they are in the current channel.
  • Fixed: User ban, kick, and unban messages will now always appear in the channel and never in an IM.
  • Fixed: Whisper commands open a new IM and show your sent whisper.
v0.6.0: "Public Release 1"
  • This is the first release, so nothing "changed" since the last one.

Screenshots and Features
See this topic for screenshots and the current supported features.

Notes
  • Trying to create accounts does not function correctly time. You may make the account hard to use if attempted.
Usage notes
You will have to use a valid BNLS ("Logon Server") and CD-key for the selected client, see the Advanced tab.

Warning: WarCraft III support sends your passwords in plain text to the BNLS server at this time. Choose a server you trust until I finally get proper SRP support...

To join a channel after logging on, use the Buddies -> Join a Chat. You can then make it your "home channel" (as termed by other bots) by adding the chat to your buddy list with the setting "auto-join" checked.

All standard Battle.net commands are directed to Battle.net through libpurple's command processor. If you want to use a non-standard command (ex. PvPGN), you have to use libpurple's /say command, example: /say /ann sometext. You can also bypass it by sending multiple messages at once using CTRL+ENTER. I have left the command system there so that your libpurple or Pidgin plugins can then add commands without them being bypassed by the protocol. Also, it allows the plugin to do the proper modification to certain commands for Diablo II (ex. /whois user -> /whois *user).

Post comments and ideas, please.
#8
Known bugs (STATUS):
  • From the room list window, if you click "Join Channel" you will crash (FIXED).
  • Jailout's RBNETD (uswest.bnet.cc) will give you a blank username on logon (FIXED).
  • Certain new StarCraft keys will no longer IPBan you (FIXED).
  • If you have a channel "persisted" or you are in it and Pidgin doesn't know and you reopen/"rejoin" it, the channel user list is emptied (FIXED).
  • If you are in channel A with user X and you move to channel B then do Buddies > Get User Info... on that user X, their user information and stats will be shown as if they are in the current channel (FIXED).
  • User ban, kick, and unban messages will now always appear in the channel and never in an IM (FIXED).
  • Whisper commands open a new IM and show your sent whisper (FIXED).
Changes made (for v0.7.0):
  • Do not disturb mode is now correctly updated by your Pidgin status (COMPLETE).
  • "User is away" warning and "User is unavailable" error on IM (whisper) are now correctly shown in the IM and not in the channel (COMPLETE).
  • EID_ERRORs in channels now appear red instead of black (COMPLETE).
  • "X is away (away message)" is now displayed as an auto-response! "X <AUTO-RESPONSE>: Away (away message)" (COMPLETE).
  • Warcraft III and Diablo channel user stats are now parsed (COMPLETE).
  • Warcraft III support (COMPLETE)
#9
Battle.net Pidgin (libpurple) Plugin / This Forum...
December 29, 2010, 01:31:31 PM
This forum is for posting anything you want about this plugin: suggestions, bug reports, questions, anything. If you have one, make a new topic. I will be posting a new topic in this forum for each release. The "Preview" topic will contain overall progress and screenshots.
#10
Quote from: MystShould add a home channel option, ...
Currently you can Buddies > Add Chat... > and in the form select "Autojoin when account connects".

Though, I will consider it.

"further support for other battle.net pkts , which im sure you will do (0x26, 0x3d etc)."
Definitely.

"Ability to close tab when you join another channel."
I don't know of a good way to do this. A bad way would be to require the protocol plugin to have access to the UI and then it will become Pidgin-specific, which I do not want to do (Fun fact: Gfire requires Pidgin's UI).
#11
Download
Get it on Google Code (link)

Install
To install for Windows/Pidgin users, just copy the dll from plugins/ to either %APPDATA%/.purple/plugins/ (you might have to make a new folder) or PIDGIN INSTALL DIR/plugins/ (may be removed by future Pidgin installs).

If you want to use the protocol icon on Pidgin, just copy the pixmaps/ folder into your PIDGIN INSTALL DIR, merging contents. Note that you may want to keep the ZIP around because when you update Pidgin, the pixmaps folder is replaced, deleting the protocol icons.

(Re)start Pidgin, and make a new account.

To install for the many other configurations (OSX/Adium, Linux/Pidgin, Linux/Finch, etc), you'll have to compile it yourself at this time, since I have no idea whether they work yet. The ZIP contains the entire source.

Changelog
Quotev0.6.0: "Public Release 1"
  • This is the first release, so nothing "changed" since the last one.

Screenshots and Features
See this topic for screenshots and the current supported features.

Notes
  • Trying to log in with WarCraft III at this time will not work.
  • Trying to create accounts does nothing at this time.



Usage notes
You will have to use a valid BNLS ("Logon Server") and CD-key for the selected client, see the Advanced tab.

To join a channel after logging on, use the Buddies -> Join a Chat. You can then make it your "home channel" (as termed by other bots) by adding the chat to your buddy list with the setting "auto-join" checked.

All standard Battle.net commands are directed to Battle.net through libpurple's command processor. If you want to use a non-standard command (ex. PvPGN), you have to use libpurple's /say command, example: /say /ann sometext. You can also bypass it by sending multiple messages at once using CTRL+ENTER. I have left the command system there so that your libpurple or Pidgin plugins can then add commands without them being bypassed by the protocol. Also, it allows the plugin to do the proper modification to certain commands for Diablo II (ex. /whois user -> /whois *user).


Post comments and ideas, please.
#12
Battle.net Pidgin (libpurple) Plugin / Preview
December 26, 2010, 10:27:50 PM
I've found that libpurple is really good about being cross platform and extendable, so why not extend it to where I chat most?

I'm making this plugin for libpurple (Pidgin) that allows you to connect to and chat on Classic Battle.net.




Current functionality:

  • Log in (STAR, SEXP, D2DV, D2XP, W2BN, WAR3, W3XP)
  • Chat (appears as Chats)
  • Whisper (appears as IMs)
  • Friend list support (uses buddy list)
  • Away/DND states
  • User info and statistics (getting whois and getting profile and record, setting profile)
#13
Looks like that's supposed to be Protoss\Zerg\Terran (but instead became Scourge\Zerg\Terran), though I would personally love it if it was StarCraft\Diablo\WarCraft for the three big universes of Blizzard.
#14
Introductions / Ribose
January 17, 2010, 11:30:58 PM
Hi, apparently Myst liked my bot so he made me a "developer" on this site.

Anyway, I'm a hobbyist programmer, and I'm going to college for CS starting in the fall (idk where yet, but I know what). I *like* C# the most, but I know PHP & associated web languages (HTML, CSS, SQL, JS), Java, VB6, VBS, very basic C and C++, and very basic Python (this list was sort of in order from preferred -> not preferred).

My laptop is really old and a piece of crap but it still works. :D

I'm usually on Ribose on USEast, Azeroth, USWest, Lordaeron (BNET), freenode (IRC) in various channels.

That's all.