some pics of my upcomming bot

[Banana fanna fo fanna]

I could spend a few days writing a scripting language...or

Code Select Expand


Class.forName(cfgfile.getProperty("pluginName"));


[Blaze]

Why would you need up to 1024 bots? You can only load 8 connections to b.net from one ip...

[DeTaiLs]

That is why they made little things called proxies

[LordNevar]

Why would you need up to 1024 bots? You can only load 8 connections to b.net from one ip...

I think I just got dumber from reading this statement.

[tA-Kane]

Kind've a late reply, but w/e

Assuming the bot is targeted for windows, if not then well then it wont apply to 90% of users around the globe

That number is dropping every day. In fact, I don't think it's even accurate anymore... I'd say it's closer to 80%

Then you have the potential for file format errors caused by the user entering the data wrong, as apposed to using a self validating user friendly GUI

Just because it's a gui, it doesn't automatically mean it's "self validating". It's just as easy to fuck up the GUI's load/save code as it is to fuck up a file manually.

If we follow your logic why does'nt windows or IE just use configuration files that the user must edit directly instead of a clean easy to use self validating GUI?

The biggest difference is the sheer number of options available in Windows and IE. If you don't know exactly the name of the preference you're looking for, it would take a while to find it, even using a text editor's find feature. With a good GUI, you should be able to find it simply by going through the type categories. For example, if you're looking to enter your CD key, you go to either the connection category (since it's a connection-time thing) or the general preferences category (since the programmer would then be too stupid to put it into a connection category).

[Blaze]

That is why they made little things called proxies

I know but, who in there right mind would need 1024 bots?

[MyndFyre]

That is why they made little things called proxies

I know but, who in there right mind would need 1024 bots?

If 1,024 is just an arbitrary limit, I would suggest *not* building it into your bot.

When I was originally designing my bot, I designed it to support three connections (you can see this with the screenshots at the bottom), selectable by a ListBox.

As I discovered *very* quickly, three simultaneous connections was a very inhibiting limit.  Suppose this --

1.) I run the channel moderation bot, AoA, for my clan.
2.) I want to idle in Op [vL]
3.) I want to run a channel web chat client (with a plugin for my bot) in AoA's channel.
4.) I want to idle in Op e1- on west.

There I am stuck. :/

I realize this doesn't necessarily apply to loaders.  However, what I'm trying to get at is if you want to use multiple connections, don't design those connections with an arbitrary limit in mind, because one day you may want to get past that limit, and sometimes that's not easy to do if you've been hard-coding that restriction at every turn.

[iago]

On mine, each bot is just an instance of my class so I can make as many bots as I want, technically:

BNetSocket []bots = new BNetSocket[100000];

for(int i = 0; i < 100000; i++)
 bots = new BNetSocket("profile" + i);

[iago]

Another advantage to console is I can run it like this:

iago@darkside:~$ java Main iago > ~/public_html/exile.txt &

And all the output will end up here:
http://iago.valhallalegends.com/~iago/exile.txt

Sexy, eh?