Handling for JA's that return no message at all when failing to take effect #2559
-
I encountered a potential issue while setting up Larceny. Retail testing shows Larceny printing absolutely no message when the target does not have any status effects to steal. I have set up Larceny to default to message 453 in the database and to set server/src/map/entities/charentity.cpp Lines 1444 to 1462 in bcb9e50 Setting ability:setMsg(xi.msg.basic.NONE) in the script triggers the core to default the message to "User uses ability".
My question is: Should this part of the code be adjusted to allow for returning no messages at all? Or is it acceptable for the ability's default return to show message 100 even if that deviates from retail setup? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
No, it has a message. The client may not choose to display it. It appears to be the same message as steal failing.
|
Beta Was this translation helpful? Give feedback.
-
the behavior we use elsewhere is returning zero while the message type is set to one that doesn't expect a zero returned, rather than having no message return at all |
Beta Was this translation helpful? Give feedback.
No, it has a message. The client may not choose to display it. It appears to be the same message as steal failing.