Automated updating of API pages at this location, to reflect patch changes, has ceased from 10.1.7 onwards.

This function is restricted. #nocombat - This cannot be called while in combat. Restricted since patch 2.0.1; Fails silently if called from an insecure execution path in combat. Consider using /petpassive instead.

Stops the pet from attacking.

PetStopAttack()

Details

• This function is not called by FrameXML, and is only effective if called by addons while not in combat.

Patch changes

Patch 2.0.1 (2006-12-05): Fails silently if called from a tainted execution path during combat lockdown.

See also

• PetAttack