[3.3.5a] Items and NPC's.

[Angerpull]

I have no idea what is going on, at first I thought it was the Repack but it's not. So I tried to reinstall the game but that didn't help.

The Problem is: Every single item in the game is a red questionmark in my backpack. No, not custom ones but normal ordinairy items, like the Hearthstone. I can't right click to equip items, I have to drag them right over.

Another Problem is: No NPC's are wielding weapons, Illidan Stormrage is punching me, and so is The Lich King. Guards don't bear weapons either.

[Angerpull]

Wow, you don't know so you close it? Classy...

[DDuarte]

Your issue report does not comply with any of our rules.

http://collab.kpsn.org/display/tc/The+TrinityCore+issuetracker+and+you
https://github.com/TrinityCore/TrinityCore#reporting-issues

[Kinzcool]

We do not support repacks.

[Angerpull]

So you guys, post an issue forum about your repack, but you don't support repacks? Well then, why have an issue forum about your repack when you don't support repacks?

[Kinzcool]

Can I have the link of this repack of ours that you are mentionning?

[Angerpull]

http://jeutie.info/releasenotes/release-revision-1/

Right at the bottom it asks if I've found a bug, so I clicked it. I make the issue, and then it's taken down...

[Kinzcool]

It's not our repack, Jeutie and anyone else redirecting people using repacks to our tracker are woefully wrong.

[Angerpull]

But you do know the answer to my problem, right? But since it's about a repack you won't support it and take it down?

How about this: I recreate the exact same issue, but I will not say anything about it being in a repack, but a Trinity Core problem itself? Will that work?

It's not a TrinityCore problem itself as it seems no one else has experienced such issue. It's probably corrupt dbc data, or whatever it is, we'd never be able to tell nor would it be convenient to look into it as it's not a problem pertinent to our project itself but to third-parties.

[Warpten]

No.

Let's put it like this: We have no clue what revision repacks were on. We have no clue whatever custom bullshit was added. We don't have time or want to go dig the crap. That's time wasted.

Thus we cannot tell if the issue is caused by custom code or if it is happening because someone didn't bother updating. So TL;DR, we don't support repack, and generally hate repack people for getting donations while they don't do shit but hit a goddamn fucking button. Don't try to outsmart us by pretending to be running your own compiled TC.

Also, someone please go tell all the idiots to stop forwarding their shit to us.

[Angerpull]

I've seen more than me with this problem, and when I run a mangos server or Arcemu there's no problem.

But since we know how stable Mangos and Arcemu is in terms of being blizzlike, I'd rather use Trinity but hey, this is really game breaking...

[Kinzcool]

This problem is actually caused by items in item_template using DisplayID's that are not in Item.dbc. So, no, actually this problem is not related to us (also, items are in a DB2 file now).

Furthermore, 4.3.4 & 3.3.5a are deprecated in terms of support.

[Warpten]

3.3.5 is no longer supported. We won't update it, but cherry-pick to it from 6.x whenever applicable. Same goes for 4.3.4