[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.