warrior player with clr bot.

[daerath]

Got it working as well. I went through every update and examined the changes to ensure I wasn't going to break anything.

It turns out that was a good idea because a number of the updates will cause tables to be dropped and recreated, but you'll lose a lot of data in the process that the patch won't put back.

Here are the patch files I had to run.

1723_required_sql_corruption - Added this one manually because one of the entries already existed.
1736_optional_sql_feral_swipe
1737_required_sql_rule_and_aa_update
1753_required_sql_healing_adept_aa
1754_required_sql_healing_adept_aa_fix
1755_required_sql_fear_resist_aas
1786_required_update_to_aas
1790_required_aa_required_level_cost
1793_resist_adjust <-- This is probably the root cause (thanks bad_captain)
1803_required_tasks_xpreward_signed
1804_required_ae_melee_updates
1802_required_doppelganger - Change IDs to 682, 683, 684 and then run. You have to do this or it won't run successfully, and if you do, you can ignore 1813_required_doppleganger_npcid_change.

Thanks to bad_captain and Congdar for the advice!