EQoffline, bots and more..

[Congdar]

Originally Posted by BatCountry

I've been simplifying the interface for a lot of commands ("#bot raid order task attack"? really?) to a #bot, #bot group, and #raid command structure, and I've stuck all of the commands into two separate included .h files ("botcommands.h" and "botraidcommands.h") which can be included in "commands.h" to make merging a bit easier, etc.

#raid should be #bot raid
I think everything should be prefaced with #bot because eventually the emu is going to have it's raid stuff fixed and there may be gm commands like #raid and we don't want to preclude the emu from using them. Just my .02 on the commands.(unless it was just a typo... I see you have #bot group).

[cubber]

Now that it has stabalized some, maybe it might be ok, but since there is still some fluidity to the code, it seems easier to work on it this way than do code submission requests through the emu devs.

What about a separate release thread on these forums for the bot source and binaries, so it is easier for people to find them and know exactly when it has been updated. This thread is growing fast and sometimes it is easy to miss releases if you don't check every day.

Keep this thread as the discussion thread and only let the people working on the code post in the release thread.

[Davood]

is there an easy way to take the masters guild tag and slap it into the bots "last name"

because the "last name" currently is what it displays as the "guild tag" for the bot. with the default being "bot"

[Congdar]

I couldn't find an easy way to do that.

[Congdar]

Originally Posted by cubber

What about a separate release thread on these forums for the bot source and binaries, so it is easier for people to find them and know exactly when it has been updated. This thread is growing fast and sometimes it is easy to miss releases if you don't check every day.

Keep this thread as the discussion thread and only let the people working on the code post in the release thread.

That could make it easier... if the forum mods are reading this, could you add a new thread that could be updated with just the source locatios like he suggests?

[Aramid]

I was thinking that I would start working on the BOT Spells again, but WHERE are they going to be designated in the DB? I thought it was agreed on that the 600's were ok but other spells are showing up there now. Going to have to remove all the FEAR LINE of spells now that the Fear Fix is in. It will be easy to change what I have already in the 601 to 6xx to another number using GeorgeS's tools, but it would be good to have a designated area, yes?

[Congdar]

Originally Posted by Aramid

I was thinking that I would start working on the BOT Spells again, but WHERE are they going to be designated in the DB? I thought it was agreed on that the 600's were ok but other spells are showing up there now. Going to have to remove all the FEAR LINE of spells now that the Fear Fix is in. It will be easy to change what I have already in the 601 to 6xx to another number using GeorgeS's tools, but it would be good to have a designated area, yes?

Maybe 1001 on up? that would leave lots of room for some expasion? Don't remove fear line... but add snare/root line

[BatCountry]

Originally Posted by Congdar

#raid should be #bot raid
I think everything should be prefaced with #bot because eventually the emu is going to have it's raid stuff fixed and there may be gm commands like #raid and we don't want to preclude the emu from using them. Just my .02 on the commands.(unless it was just a typo... I see you have #bot group).

That's a really good point. I was just doing it that way to reduce the amount of typing with raid commands, but it seems like that sort of stuff is going to get macroed by players anyway.
I agree that compatibility should definitely trump brevity. I quit EQ far before they put in the raid interface (about a year before PoP), so honestly I'd forgotten there was one.