Mixed packet timing issue between printToPlayer and messageSpecial in a custom trade script. #10062
-
|
The Issue:
However, right now, the server groups all printToPlayer lines at the top of the chat frame, and clumps all messageSpecial items at the very bottom, completely breaking the order. My Questions: Is there a native function that lets me send a standard text string (like a header) into the same message queue as messageSpecial so the client renders them in order? (I tried messageBasic, but couldn't find the right message ID offsets for plain text). Alternatively, is there a core string utility method (like xi.item.getName or a specific packet token) available in the module environment that exposes raw item names, so I can just use printToPlayer for everything with \x1e\x1f color tags without hardcoding a manual translation table? My code Snippet: Here is the lua file: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
I'm not confident that this is the proper approach, but if there are only two pairs of messages, sending the messages asynchronously from the NPC interaction, like below, might make them appear in the expected order. |
Beta Was this translation helpful? Give feedback.
I'm not confident that this is the proper approach, but if there are only two pairs of messages, sending the messages asynchronously from the NPC interaction, like below, might make them appear in the expected order.