Tiny Companion and pets changing target

[Slingshot]

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.

[Derision]

Tiny Companion has worked fine since Rev156.

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

[Slingshot]

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

[Slingshot]

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?

[Derision]

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.

[Slingshot]

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.

[Derision]

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.

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:

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.