Langerz82

Dup see: https://www.getmangos.eu/bug-tracker/mangos-zero/Menu-Blocker---GM-Mode-stops-m-r482/

Is this still an issue with the latest version?

Is this still an issue with the latest Revision?

Likely fixed in latest Revision, If it's still bugged please re-open issue with more detail.

Working latest revision. Closed.

SELECT * FROM mangos0.creature WHERE id = 8901; It's set to 20 secs for most of them. What should it be?

Is this still occurring? Cosmetic only please change to priority Low.

Is this still an issue with latest revision?

edit: it's Seal of Command and it's been fixed on latest version. Closed.

Close

No reply appears to be fixed. Close.

Close please

Needs testing: Langerz82/WoWZeroDisableOwnerDefaultChannel.patch

Implementation. Note - The speeds have to be adjusted in Database to match the Pet attack speeds: http://www.wow-petopia.com/classic/attackspeed.php diff --git a/src/game/Object/Pet.cpp b/src/game/Object/Pet.cpp index 7ec1822..37ac5d9 100644 --- a/src/game/Object/Pet.cpp +++ b/src/game/Object/Pet.cpp @@ -1092,9 +1092,30 @@ bool Pet::InitStatsForLevel(uint32 petlevel, Unit* owner) SetModifierValue(UNIT_MOD_ARMOR, BASE_VALUE, float(petlevel * 50)); - SetAttackTime(BASE_ATTACK, cinfo->MeleeBaseAttackTime); - SetAttackTime(OFF_ATTACK, cinfo->MeleeBaseAttackTime); - SetAttackTime(RANGED_ATTACK, cinfo->RangedBaseAttackTime); + CreatureInfo const* creatureInfo = ObjectMgr::GetCreatureTemplate(creature_ID); + if (creatureInfo) + { + if (creatureInfo->MeleeBaseAttackTime > 0) + SetAttackTime(BASE_ATTACK, creatureInfo->MeleeBaseAttackTime); + else + SetAttackTime(BASE_ATTACK, BASE_ATTACK_TIME); + + if (creatureInfo->MeleeBaseAttackTime > 0) + SetAttackTime(OFF_ATTACK, creatureInfo->MeleeBaseAttackTime); + else + SetAttackTime(OFF_ATTACK, BASE_ATTACK_TIME); + + if (creatureInfo->RangedBaseAttackTime > 0) + SetAttackTime(RANGED_ATTACK, creatureInfo->RangedBaseAttackTime); + else + SetAttackTime(RANGED_ATTACK, BASE_ATTACK_TIME); + } + else + { + SetAttackTime(BASE_ATTACK, BASE_ATTACK_TIME); + SetAttackTime(OFF_ATTACK, BASE_ATTACK_TIME); + SetAttackTime(RANGED_ATTACK, BASE_ATTACK_TIME); + } SetFloatValue(UNIT_MOD_CAST_SPEED, 1.0);

I think this issue has been fixed latest revision. Let me know if it's still an issue.

I believe this may be related. Apply the patch and see if you get the same crash. See:

Ok the problem with randomizing respawn times with Plants and Mineral is this. They are treated as a GameObject Chest. If we were to apply some randomizing algorithm to respawn times we would first have to need to create: GAMEOBJECT_TYPE_PLANT GAMEOBJECT_TYPE_MINERAL So we can apply a randomization algorithm for those affected GameObjects only. The other option would be to add another spawntimesecs2 field in the GameObject DB and to random between the two values given the second one is set. However by doing this it would add a redundant data field to all the gameobjects that dont require randomized times. The third option is to just randomize the GAMEOBJECT_TYPE_CHESTS, but that will break fixed times on all chests.

Fixed on latest Revision. Tested and on completed Quest it brought me to the Complete page and not the Incomplete page first like OP has mentioned using same example.

OP hasn't replied, mark as resolved.

I think this can be set to Low Priority as its only cosmetic.

On latest version I didnt see any error and the Portal worked. Is this still an issue?

Is this still an issue with latest revision?

This is probably to do with the pet movement doing a vmaps check and seeing that there is nothing there because its a dynamic moving object it falls through. We need a flag of some sort indicating to the pet that there on a dynamic object and to ignore vmaps and just use the players z-axis.

Should be fixed with patch I made in another post. Please close.

The latest version the aggro only occurs when the target is hit by the Arcane Missiles? Am I missing something or has been fixed?