Drajor
09-05-2014, 02:47 AM
It turns out this is possible (tested with UF). Thanks to Kayen for sitting through the exploration and giving advice!
Currently we use send OP_GMLastName with GMLastName_Struct payload to update clients when a Character/Client has changed their surname. It turns out that this can also be used for NPCs. It is as easy as setting the name parameter to the non-clean (and ideally unique) npc name.
Where npcs have non-unique names the client appears to either update the one with the highest spawn id or the one most recently added.
Does anyone know any history of this packet/payload? I am curious about it's name and the gmname attribute.
Currently we use send OP_GMLastName with GMLastName_Struct payload to update clients when a Character/Client has changed their surname. It turns out that this can also be used for NPCs. It is as easy as setting the name parameter to the non-clean (and ideally unique) npc name.
Where npcs have non-unique names the client appears to either update the one with the highest spawn id or the one most recently added.
Does anyone know any history of this packet/payload? I am curious about it's name and the gmname attribute.