Jump to content

Recommended Posts

  • 40 years later...
Posted

Hi, I'm a level 3 GM on a private WoW server, trying to help out my admin and the regular players there.

Since we upgraded to MaNGOS core 3.3.0 custom weapons stopped working properly. The weapons still give stats, but all skills that requires a Melee weapon on Main hand doesnt work. My rogue has a set of dual custom swords and everytime i have it on my main hand, if i try casting hemorrhage, Ghostly strike, or any other skill that requires a melee weapon, it says I can't cast it cos I need a Melee weapon on my Main hand. But as soon as i replace the custom sword to a regular non custom weapon, all my melee skills works fine.

Also, going a bit off topic here, Throw only works on the target's back.

Any suggestions?

Thank you for reading.

Peace

Posted

You should have waited until the 330 branch becomes supported. It is currently not recommended to use it since it's unsupported.

Posted
The weapons still give stats, but all skills that requires a Melee weapon on Main hand doesnt work.
This meaning that in 3.3.0 client start get weapon type from own DBC insteed sent DB data. I can make only one recommendation true for current and later clients forcustom items: find in items.dbc unused for normal accessable to players item id with _excatly_ item type, and use it. And strongly not recommend use item ids that not exist in items.dbc. Fromclient version to next it will more and more broken because from version toversion client startmore base own work at item.dbc instaed any sent DB data.
Posted

so thats only client side or? there is no way to add a check if an item is not in the dbc and then send it to the game client? im not really expert and i may be asking something that doesnt make sense lol

Posted

we send all data from DB in item data requests from client. But client now partly ignore this data and use own. That why like diff. values spam at server loading.

Before this only affect icons in inventory but now (base at your report this more wide affected).

So this client side limitation.

Posted

ok thanks for the infos, but wasnt something like that also with horde and alliance groups? till a certain game version(i believe before wotlk) they always been allowed to group/trade/heal and so on just by changing the mangos.conf, then we needed to apply the "hacky" patch (if im correct FakeGenesys made it) to make groups work properly between factions.

So since the part of item checking is made by the game and not by the server anymore, maybe there is some sort of work arround to make the server believe the spell u have to cast doesnt require any weapon equipped if u have the correct one... sounds hard and i wont even know where to start from lol, but im trowing out ideas, hoping maybe to find someone more able than me to code.

I will eventually start a thread in the dev part of the forum since thats not really a bug but more like an improvment of the actual mangos functionality.

Posted

I already found some IDS not used in DB with proper CLASS and SUBCLASS fields, to update the entry in the DB I know I should run something like:

UPDATE item_template SET entry = '1313' WHERE entry = '75000';

Now the question is, what should I run in order to update characters inventory? I dont feel like manually changing all the custom items ingame. I know I have to run a query to update characters.character_inventory and item_instance, I know it have to be something like

UPDATE character_inventory SET item_template = '1313' WHERE item_template = '75000';

The problem is that I dont know what should I run in order to update item_instance, hope someone could help us with any idea =)

Thanks in advance for your help.

  • 4 months later...
Posted
This meaning that in 3.3.0 client start get weapon type from own DBC insteed sent DB data. I can make only one recommendation true for current and later clients forcustom items: find in items.dbc unused for normal accessable to players item id with _excatly_ item type, and use it. And strongly not recommend use item ids that not exist in items.dbc. Fromclient version to next it will more and more broken because from version toversion client startmore base own work at item.dbc instaed any sent DB data.

Thanks vlad, this worked perfectly. Just 1 (minor) problem though, if i use a blizz item to be replaced by a custom item, like a sword, the stats, names and quotes are custom, but the seath and display ID are still the same as the original blizz item i used.... even though i coded the values to seath as a staff and a diferent display ID... is there anyway around that?

Cheers!

Posted

More and more spells get broken and tons of hacks, because of inaccurate blizz .dbc data and custom content is difficult to realize.

Maybe time for sql-based .dbc entries, which can overwrite blizz .dbc?

Posted

For let adding another tons hacks just because someone lazy research problem and find proper solution.

Why search solution if so easy just "fix" spell.dbc data. Ofc, this not important that after will find that this "fix" just lazy garbage....

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use