I got a couple suggestions for JavaOp!

[Berzerker]

1) Have the bot save window size/configuration on exit, or make an option to save it in a menu.

2) Fix the spam/drop protection. It really sucks. I have to wait literally 30 seconds for the 3rd line to spit out. I doubt 30 seconds is needed. Probably increasing it 1-1.5 seconds each time is enough...

[iago]

Regarding 2, a lot of thought and experimentation went into the algorithm. When you initially log in, you're more likely to flood out (because of all the login packets), so it's a bit slow.

[Camel]

Flood protection is a tricky thing with battle.net. My bot's flood protection is also slow, because it's designed to be able to get the maximum throughput, which is the safest way of throttling text. I give the user the option of disabling flood protection, because it's also used for chatting, where flood protection isn't much more than an annoyance. I think this is a much better solution than trying to squeeze convenience out of the algorithm.

[iago]

You can disable the flood protection in JavaOp2 as well (somewhere in the options), so life's good. :)