Does anyone know why this problem occurs?

 

broadcastPacket(new NpcSay(getObjectId(), Say2.ALL, getNpcId(), "Goodbye Traveler!"));
broadcastNpcSay("Goodbye Traveler!");
this.broadcastPacket(new NpcSay(this.getObjectId(), 0, this.getNpcId(),"Hello World!"));

I've checked client side too. Edit npcname-e.dat but still nothing. I thought it might be that.

 

	<npc id="50024" name="Mystery Prize" title="Explore Me!">
		<set name="usingServerSideName" val="true"/>
		<set name="usingServerSideTitle" val="true"/>

 

Edited March 20, 20206 yr by protoftw

This issue occurs due to missing client support for your custom ID.

It's usually not recommended for NPCs but you can have a try with CreatureSay packet. You'll also avoid modifying client this way, since it accepts character name directly, instead of ID.

 

If you still prefer doing it with NpcSay, try adding a new record for it in npcgrp.dat too (npmname would definitely not be enough).

Edited March 20, 20206 yr by DnR

16 minutes ago, DnR said:

This issue occurs due to missing client support for your custom ID.

It's usually not recommended for NPCs but you can have a try with CreatureSay packet. You'll also avoid modifying client this way, since it accepts character name directly, instead of ID.

 

If you still prefer doing it with NpcSay, try adding a new record for it in npcgrp.dat too (npmname would definitely not be enough).

ah because i had many custom npc's added manually i thought i had this ID too and i didn't even bother to check npcgrp.. Although i really appreciate you for taking the time to help me.

You made me see the only thing that i couldnt see :D