EQEmulator Forums - Tiny Companion and pets changing target

EQEmulator Forums (https://www.eqemulator.org/forums/index.php)

- Development::Bug Reports (https://www.eqemulator.org/forums/forumdisplay.php?f=591)

- - Tiny Companion and pets changing target (https://www.eqemulator.org/forums/showthread.php?t=26745)

Tiny Companion and pets changing target

Not sure if these were mentioned or not.

I'm an ogre beastlord. Casting tiny companion on my pet does nothting.

Also, I can't get my pet to change targets. In Live if you are attacking multiple targets you can target the one you want your pet to attack and click the attack button in the pet info window. He will then start attacking that target. He seems to just go off hate and ignore you.

Also, a minor bug, but my pet will try to attack a dead npc that has hit me with a dot until the dot wears off. He just keeps telling me that's an invalid target.

Just noticed my pett will try to attack dead npc's.

If I click a corps and click attack on my pet window he'll run over to the corps, try to attack it, tell me it's not valid then run back to me.

Tiny Companion has worked fine since Rev156.

http://code.google.com/p/projecteqemu/downloads/list

I take it the dowloads on here are out of date? (EQEmu-0.7.0-1129)

I tried to run the first script in revision189 (1_task_system.sql) figuring I just had to run them in order and they would update my DB but I got an error.

Script line: 118 Duplicate entry '1-TaskSystem:EnableTaskSystem' for key 1

Not sure if I made a mistake or I accidently ran it twice or something. Should I just move on to the next one?

You can ignore any errors relating to duplicate rows in the rule_values table, such as those, so yes, just carry on sourcing them in sequentially.

Problem is I'm not sure if it went threw the whole script or just stopped on that line.

I'm using Mysql Query Browser to execute the script. Should I be doing it a different way?

Thanks for helping me out with this.

I'm not familiar with the MySQL Query Browser, I use the command line interface which continues on after any errors.

If the tool you're using stopped when it encountered the error, that could be a problem.

Looking at 1_task_system.sql, after it has the inserts for those rule values, it creates a table called raid_details, amongst other things, so if you have that table, it looks like it carried on after the error. From the command prompt, I would check like this to see if I had that table.

Code:

mysql> describe raid_details ;

+----------+------------+------+-----+---------+-------+

| Field    | Type       | Null | Key | Default | Extra |

+----------+------------+------+-----+---------+-------+

| raidid   | int(4)     | NO   | PRI |         |       |

| loottype | int(4)     | NO   |     |         |       |

| locked   | tinyint(1) | NO   |     |         |       |

+----------+------------+------+-----+---------+-------+

3 rows in set (0.09 sec)

If it stopped at the first error, then you need to edit 1_task_system.sql and delete all the lines from the start up until and including the line:

Code:

Insert into rule_values values (1, 'World:AddMaxClientsStatus', -1);

Then source in the remainder of the file and carry on from there.

If you haven't already, I would back up your database before continuing.

I ended up using the command line interface and just ran each file. I didn't even know I could do that.

How often should I check that site for updates? And are there any other updates I needed to go from the 1129 version on this site?

Sorry for all the confusion on my part. It just seems (from my noob perspective) that there are files and info all over the place and finding exactly what I need seems to be a little bit of a scavenger hunt.

There are source code updates every few days at the moment, and new Windows executables appear every week or so.

If you got the Rev189 executables and sourced in all the SQL, then you should be up-to-date now with the latest code.

Great! I'll keep checking it for updates.

I ran into some perl error after updating so I'm installing build 822. Hopefully that will fix the problem.