it does not require either.izusaga wrote:I'm not a huge fan of autobot because it requires either IRC plugins or emulation
Moderator: MacroQuest Developers
it does not require either.izusaga wrote:I'm not a huge fan of autobot because it requires either IRC plugins or emulation
I consider myself to be fairly versed in MQ2 and it's terminology and structure. I won't use a IRC plugin so ModBot is out of the question, and even following the Wiki for autobot I still can't even make a beastlord assist the MA and attack. Perhaps it's a dependency issue because I don't load exchange, but that really shouldn't be causing the level of trouble I have simply getting a functional autobot.Canadian_Cowgirl wrote:Modbot requires IRC/BC etc, but autobot doesn't as far as I know
-C_CG.
Specifically lack of familiarity/comfort with IRC in general. I'd rather simply give commands with tells or more specifically, in a channel.jacensolo wrote:Is there a reason you won't use an IRC plugin?
Also, I believe modbot runs with EQBC as well, which isn't IRC.
I've been playing with both mods for the past few hours. Modbot seems to require advcombat which is part of the old advbot, which I no longer have. For example, my beastlord will engage if he's in melee range and facing the right way, but if he's turned or out of range he just chain jumps with an error because the files listed in the most recent Modbot does not include advcombat.jacensolo wrote:If you check out EQBC, that is about as basic as possible as far as commands go. To use it, I just run the exe, and then do "/bccmd connect" on each char.
Then you can use it to send messages which can be interpreted by macros, or you can just send raw commands. For example, if I did "/bca //sit", all of the chars connected would sit. It's a very effective way to connect groups of bots. When combined with MQ2NetBots, it even lets you grab data like CurrentHPs, TargetID, and PctMana from your other bots on the fly.
It's very easy to setup and use. No offense, but part of the reason more and more bot macros are using EQBC or IRC is that they're immensely helpful for connecting groups together without depending on EQ's chat channels for communication.
Hmm. Running the server and then loading the eqbc plugin, when doing /bccmd connect I get an invalid command error.jacensolo wrote:If you check out EQBC, that is about as basic as possible as far as commands go. To use it, I just run the exe, and then do "/bccmd connect" on each char.
Then you can use it to send messages which can be interpreted by macros, or you can just send raw commands. For example, if I did "/bca //sit", all of the chars connected would sit. It's a very effective way to connect groups of bots. When combined with MQ2NetBots, it even lets you grab data like CurrentHPs, TargetID, and PctMana from your other bots on the fly.
It's very easy to setup and use. No offense, but part of the reason more and more bot macros are using EQBC or IRC is that they're immensely helpful for connecting groups together without depending on EQ's chat channels for communication.
Recompiled and applied and I can not use the /bccmd connect to connect to the local server.jacensolo wrote:If it's giving you the red "invalid command" error, it's not a EQBC error. Are you sure the plugin loaded? Try just "/bccmd".

Regardless, I'm getting errors, and I've posted said errors, and this forum appears to be rather dead so help isn't easy to comeby. I can accept that just fine.toomanynames wrote:izusaga, so you are clear, modbot doesn't use IRC, only eqbc. All macro code is available in the zip, there are no requirements from advbot. The only requirements are the plugins listed in the wiki and the modbot zip itself. If you are getting errors then you've got something wrong.