Bots crash EQ client
 

Every time I try to give one of my bots an item, my Everquest client gives a message sayig the the client has stopped working and then the program ABENDS to my desktop. Has anyone seen this before???

What item?

I've seen items with non-existent script files cause issues when equipped - like keeping a client from logging in.

I've tried a bunch of different items on different bot. One of them was the Bracers of the Reverent for a cleric.

I could be wrong, but I thought I saw this issue somewhere before,
and if I remember correctly, although the cause was not determined,
the player deleted both the bots AND the toon, then created a new
toon, with new bots and problem wasn't there. Not positive on that.

Thanks Grumpy! I'll give it a try!

Well... I tried that and it didn't work

Did you try to manually run any update scripts for bots?

no... where would I find the update scripts??

If you haven't, then that's a good thing.

Without a 100% understanding of what you're doing, you can create a condition where the db tables are older than required - which can, at a minimum, cause errors and/or data loss.


I just tested on my local server - 100% up-to-date - and had no problems with my bot cleric and the Bracers of the Reverent.


Are you using the RoF2 client? build: May 10 2013 23:30:08

You are referring to actual bots and not mercs or boxed clients, right?

I'm using the Titanium edition of EQ. Yes the bots.. What's the best way to make sure to do an update straight across the board? I really don't have anything worth saving so maybe I should just blow out the server and reinstall everything.

If you have another client version, can you test it on that client? (pref: RoF2 - easy to find)

Well... I wiped the server, reinstalled it and the same thing happened! El crashamundo!
Not sure If this client is bugged or what! Let me find the a Rof2 otherwise I'll just write a SQL script to equip the bots automatically. I mean it's what I do for a living anyways. Of course I'd rather deal with MS SQL server 2016 than MySQL.

I don't have any issues with using the built-in trade system (for tradeable items) or the ^invgive command.

I don't test too much on Titanium any more since peq start recommended RoF2.

Ok... Good advice! I ordered Rof2.. Should be here in a fwe days.. One part of me is saying ..."Fu## it just go play World Of War Craft with my son." But the engineer in me is saying "Oh I will get this working!" Lets see who wins out!

There is a server called The Prime Healer on the list. Supports Titanium, with bots.
Did you try logging on to that server with your Titanium client, and see if you get
the same problem ?

I possibly just ran into this issue while testing some new inventory code.

Traded a burlap shirt to an empty bot and the client itself crashed.

Came back in and the bot had the item, I didn't have a copy on my toon and I was able to keep playing.

Will keep an eye on this...

there's a wowemu too. trinity or trinitycore? is one to google, for example. not sure who has the newest and best anymore. you'd have to readup on a forum.

there are alternative methods of obtaining rof2, and you need a specific client version. wiki probably lists it somehwere.

... lots of fun servers here, check out their forums for good 'random' info. maybe one that prefers rof2. nudge nudge, wink wink

I've personally got a wow server and EQ server running and I found that the eq server was a little easier to set up. On a side note if you need a copy of rof2 I can get it for you just private message me.

I think I found the issue with trading to bots in the window..need to commit the fix and push it now.

I must of missed that ability to use the trade window with bots somewhere. I always thought it was purely ^ingive ? lol

Yeah, even though they are treated as NPCs on the server, we bit-hack the out-going spawn packet to make the client think they are other clients..

..and can use the standard client trade window :)

Clever Uleat =)

Oh ho, I gotta check this asap :D thank you Uleat !

Someone else came up with that bit-hack long ago :)