Clan x86
Technical (Development, Security, etc.) => General Programming => New Project Announcements => Topic started by: Networks on May 18, 2005, 01:16:56 pm
-
This is the code name for the bot itself mostly because we haven't thought of one but we wanted to call it something for now. Anyhow this project is a dual project between WiReS and myself and we are currently looking for ideas throughout the community.
This is just some of the stuff we have or are looking forward to currently:
- Full support of all clients through BNLS and a hashed connection. Our BNLS connection is a secure connection as we use BNCSutil.dll to hash all passwords and cdkeys while using BNLS' core features that require absolutely no hash files.
- Full MCP support
- Customizable colors for all chat events (There are limitations but it's overall pretty customizable)
- All the basic features of a chat bot. (Mostly optional stuff and settings)
- The ability to load multiple profiles and a multiple sockets for those profiles so only one executable is required for all your chatting needs.
Other features we wish to impliment are classified to some extent. This is hardly completed and only connects and shows events properly. This is somewhat of a branch of PiAnKA and I's "Mario Chat" however much more cleaner (10x). I'd love to hear what suggestions you have for things you've always wanted or think a chat bot SHOULD have. No suggestion will go unturned.
As for information about beta testing. We have agreed that it will only extend out to our clan (x86). Thus x86 members only will recieve a beta whenever it's due. A release date isn't known but probably in 3 - 4 weeks I am assuming as summer is coming.
-
You make me sad!! What language is this in?
Suggestions:
Add in a feature where I get to use it.
HTML logs of dom!
-
You make me sad!! What language is this in?
Suggestions:
Add in a feature where I get to use it.
HTML logs of dom!
It's in visual basic 6.0. This will probably be my last VB6 bot development project, it's really time to move on, don't you agree? Anyhow I haven't ran it over with WiReS but he'll probably agree that we make it private to people we know. I honestly don't care for for fame or public opinion anymore as may have used to, it's really quite useless. I've programmed publically for a couple of years and have had no satisfaction in it. We'll probably just open-beta and release it to people we know (yourself included Rabbit). If WiReS agrees I'll let you know. I am pretty sure he's the same way. HTML logs is a possibility if I figure out a way a extract colors from the RTB and output them.
-
Public Function HTMLFont(lngColor As Long, strLine As String)
Dim strColorCode As String
strColorCode = Hex(lngColor)
strColorCode = IIf(strColorCode <> "C0C0C0", _
StrReverse(strColorCode), _
strColorCode)
strColorCode = Left(strColorCode & "00000", 6)
strLine = Replace(strLine, "&", "&")
strLine = Replace(strLine, "<", "<")
strLine = Replace(strLine, ">", ">")
HTMLFont = "<font face=arial color=#" & strColorCode & _
" size=2>" & strLine & "</font>"
End Function
Add into the AddChat routine (or whatever you call it):
var = HTMLFont(CLng(vData(i)), CStr(vData(i + 1)))That's how I did it for MeBot, anyways.
-
HTML logging? Why not just add a webbot?
-
HTML logging is good.. but uhm, how about some uber-secure method of making sure it doesn't get leaked? :P
-
Fingerprint scanner!
-
I'd recommend following the pattern that Redchair Software does if this was a bigger project, but I don't think it'd be worth the work. The security measures would take longer than the actual project!
For HTML logging for XeroethBot, I used the same method Rabbit did, with different code (of course). I didn't have a dynamic method for the hex colors though, I just had a select case (eww, I know).
A little bit of a 'suggestion' (not really a correction) on rabbit's code though:
Public Function HTMLFont(ByVal lngColor As Long, ByVal strLine As String)
Dim strColorCode As String
strColorCode = Hex(lngColor)
strColorCode = IIf(strColorCode <> "C0C0C0", _
StrReverse(strColorCode), _
strColorCode)
strColorCode = Left(strColorCode & "00000", 6)
strLine = Replace(strLine, "&", "&")
strLine = Replace(strLine, "<", "<")
strLine = Replace(strLine, ">", ">")
HTMLFont = "<font face=arial color=#" & strColorCode & _
" size=2>" & strLine & "</font>"
End Function
The default in VB6 is ByRef, not ByVal. If you use ByRef here, you could end up getting yourself in trouble if you use the string to add to the RTB before it's actually added. :)
-
Haha, man I have had enough troubles with ByRef in the past, ugh...man those memories are swarming in...lol
-
I use a string for each of the log buffers (MeBot has HTML and plain-text logging), and I use manipulate the input array for the RTB. The buffers never reach the RTB :)
-
I use a string for each of the log buffers (MeBot has HTML and plain-text logging), and I use manipulate the input array for the RTB. The buffers never reach the RTB :)
That works too, but it never hurts to be safe. ^^;
-
Yes it does. IE: if you use a condom, but it's too small and it cuts off circulation to your dick, which then needs to be amputated. Owned.
-
Yes it does. IE: if you use a condom, but it's too small and it cuts off circulation to your dick, which then needs to be amputated. Owned.
I said safe, not too safe. A better analogy to my example (and related to your analogy) would be having your fuckbuddy on birth control pills/patches and wearing a condom. :)
-
FAG
-
Thats not too safe. Birth control doesn't protect against STD's.
-
Hence the condom -.-
-
What if it breaks? Best not to have STD's and a baby. :)
-
How about, best not to push so hard?
-
How about, best not to take topics this far off-topic?
-
How about, best not to take topics this far off-topic?
You're no fun at all.
-
Thus we shouldn't push so hard.
-
Thus we shouldn't push so hard.
Lmao. Although I hate off-topic, that was pretty damn funny.
-
I want a copy of Vanquish Chat RIGHT NOW, and I WILL push you hard if you don't give me it! =)
-
I'll just push you harder then.
-
O.o!
-
Any updates?
-
Yes. Networks left x86 and the project croaked. I'll have to talk to WiReS to see if he's done anything.
Hint: SeRiW! Get on AIM!
-
Any updates?
When I can get back in contact with Networks we'll start discussing on how we'll release it.
Yes. Networks left x86 and the project croaked. I'll have to talk to WiReS to see if he's done anything.
Hint: SeRiW! Get on AIM!
Just because Networks left doesn't mean it died. ;]
-
hrm...the project never croaked!
Anyhow, the release should expected fairly soon, I am just finishing up the last bit of features for the first release (expect more as we add-on new features and fix bugs -- oh there will be bugs I can feel it) We WERE expecting a release last monday (lol..) but school is always in the way. I finished a lot this weekend (feature wise) and I hope to finish all of them as well as the release stuff. So expect something around Thanksgiving or so.
A lot of bugs were fixed from previous builds so I am really happy about that. Also I conviced wires that we should do constant releases in an effort to keep the project alive. Also it contributes to less bugs due to less features. It's not complete at all but it will have the essentials in its first release plus more. I think it looks great so far stay anxious if you are already.
Edit: Also I think I am trying to get back into x86, funny how things change.
-
Message me when/if you want some help testing :P
-
Message me when/if you want some help testing :P
Will do. I think we may want some testers just to make sure we don't have any dumbass bugs before release. I hate overlooking things and having to make a new build right away.
***Update***
Global Options are completely finished.
Individual are next, only a few. Expect the release very soon. =]
-
You can always hit me up for testing, or just a look-through. I'm pretty interested.
-
Contact me, Mr. VanquishBot Easter Egg, when the beta is ready for me. =)
-
Update:
Currently the bot is officially going under release prerequisities. Also I am fixing any bugs so that it's capable of being stand-alone (with BNCSUtil.dll). It just helps fix the stupid user errors that may occur later on.
The first send out will be beta and that will be for 1-2 weeks depending on how good our beta testers are. Then we may add some more features and officially release the first public version.
-
Sounds good.
-
um...beta testing has started ><
-
It's a good bot, I haven't found a bug yet, totally customizable, mutliple profiles, all around good bot.
A+!
-
It's a good bot, I haven't found a bug yet, totally customizable, mutliple profiles, all around good bot.
A+!
Not to mention it's incomplete, we're still adding LOTS of things. WiReS and I are rather ambitious in the current stages it's at.
-
Nice! I'm interested in testing as well if you are looking for more.