this is due to WS_HearThreatCmd opcode type OP_EQHearThreatCmd not being defined -- we don't currently have the opcode identified for DoF, if it exists at all.
Fixed the underlying issue causing the crash, we shouldn't send the packet at all: 8e1c321c51
Will change this to identify if a threat packet exists.
this is due to WS_HearThreatCmd opcode type OP_EQHearThreatCmd not being defined -- we don't currently have the opcode identified for DoF, if it exists at all.
Fixed the underlying issue causing the crash, we shouldn't send the packet at all: https://git.eq2emu.com/devn00b/EQ2EMu/commit/8e1c321c51aa8a91222d3f955bf4bfc24190bdd9
Will change this to identify if a threat packet exists.
Does not look to be a hear threat packet, either achieved with WS_HearDamageStruct or an offshoot?? (OP_EqHearCombatCmd) or WS_DisplayText (OP_EqDisplayTextCmd)
Does not look to be a hear threat packet, either achieved with WS_HearDamageStruct or an offshoot?? (OP_EqHearCombatCmd) or WS_DisplayText (OP_EqDisplayTextCmd)
.rdata:00CDCF24 aYour351For22 db 'YOUR $3 $5 $1 for +2 $2.',0
vs AoM:
your taunt increases your hate with a small coastal crab for 216 threat.
WS_HearHeal has the potential text string for it
.rdata:00CDCF24 aYour351For22 db 'YOUR $3 $5 $1 for +2 $2.',0
vs AoM:
your taunt increases your hate with a small coastal crab for 216 threat.
and as previously trying to investigate there is no taunt/hate message in the client.
I don't believe the client supports threat or absorb messages.
HearHeal in DoF doesn't support these types afaik:
```
#define HEAL_PACKET_TYPE_ABSORB 2
#define HEAL_PACKET_TYPE_REGEN_ABSORB 4
#define HEAL_PACKET_TYPE_SIMPLE_MANA 8
#define HEAL_PACKET_TYPE_CRIT_MANA 9
#define HEAL_PACKET_TYPE_SAVAGERY 16
#define HEAL_PACKET_TYPE_CRIT_SAVAGERY 17
#define HEAL_PACKET_TYPE_REPAIR 64
#define HEAL_PACKET_TYPE_CRIT_REPAIR 65
```
and as previously trying to investigate there is no taunt/hate message in the client.
since no packet is identified im adding a channel message for KoS/DoF clients. It will be tied to your cast and other cast in terms of the combat chat options
since no packet is identified im adding a channel message for KoS/DoF clients. It will be tied to your cast and other cast in terms of the combat chat options
image
Doesn't like the WS_StartCastSpell/WS_FinishCastSpell behavior
this is due to WS_HearThreatCmd opcode type OP_EQHearThreatCmd not being defined -- we don't currently have the opcode identified for DoF, if it exists at all.
Fixed the underlying issue causing the crash, we shouldn't send the packet at all:
8e1c321c51Will change this to identify if a threat packet exists.
Does not look to be a hear threat packet, either achieved with WS_HearDamageStruct or an offshoot?? (OP_EqHearCombatCmd) or WS_DisplayText (OP_EqDisplayTextCmd)
WS_HearHeal has the potential text string for it
.rdata:00CDCF24 aYour351For22 db 'YOUR $3 $5 $1 for +2 $2.',0
vs AoM: your taunt increases your hate with a small coastal crab for 216 threat.
I don't believe the client supports threat or absorb messages.
HearHeal in DoF doesn't support these types afaik:
and as previously trying to investigate there is no taunt/hate message in the client.
since no packet is identified im adding a channel message for KoS/DoF clients. It will be tied to your cast and other cast in terms of the combat chat options