Modcraft - The community dedicated to quality WoW modding!

Wrath of the Lich King Modding => Serverside Modding => Topic started by: Big Bad Bot on April 22, 2017, 12:19:17 am

Title: [Fixed] [3.3.5] [TrinityCore] "Forced" outfits
Post by: Big Bad Bot on April 22, 2017, 12:19:17 am
Hi,

An heavily modded 3.3.5 project I worked on hadn't had a single update to its core or DB in a long, long time. Recently, there came the need to apply some adjustments so I fetched and compiled a new fresh core from the TrinityCore GIT, set up a new MySQL database and then proceeded to port over tons of tables (creatures, gameobjects, items, there were a lot of customisations to take into account)!

When I first created the core, I tested it and everything worked just fine.
After porting over the database, everything works fine except that ALL characters are wearing some robe that I cannot unequip for the life of me.
The problem appears to be somewhere in the SQL database because that's the only thing that changed but I don't have the slightest clue of what's causing it.

As I stated above, I'm using the latest Core & SQL from TrinityCore and this bug wasn't there before migrating the old "World" database (The bug disappears if I replace the World database by a vanilla one, keeping the characters/accounts intact), although it also happens on newly created characters, but only after the creation is completed (so in the "Character Creation" screen they look fine but in the "Character Select" screen they're wearing the tunic).

If anyone has some clue of what's going on here, I'd love to hear it!
I'll keep trying to find a fix myself on the meantime.
Title: Re: [Help] [3.3.5] [TrinityCore] Can't remove "forced" outfit
Post by: Amaroth on April 22, 2017, 12:58:28 am
Make sure you don't have item with entry 0 in item_template (or in item.dbc). If you do, delete it from there (and avoid re-creating it). Its source to all kinds of similiar weird problems.
Title: Re: [Help] [3.3.5] [TrinityCore] Can't remove "forced" outfit
Post by: Big Bad Bot on April 22, 2017, 01:14:53 am
I was just about to comment about having found that the culprit was in `item_template`, but I swear I would've never been able to find this bug.
After removing an item with entry 0, everything went back to normal.

Thank you kindly, Amaroth!