Originally posted by [b]theultramage[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=1235
QUOTE("Ancyker")
if 2 people have an away
and 1 message the other
it loops
forever
XD
The exact circumstances go like this:
* char A has /am (client-driven away message)
* char B has @away (automated server reply)
or
* char A has @away (automated server reply)
* char B has /am (client-driven away message)
When A messages B, B counters with a reply, and:
* if both use @away, the server doesn't trigger the loop because it does the sends
* if both use /am, the client will recognize (string comparison?) that the message has bounced
* if they don't use a matching system, they create an infinite loop until one of them logs out.
Testing shows that the client has a hardcoded exception to not autoreply to messages that begin with [Automated Message] (or whatever the msgstringtable says). Therefore the straightforward suggestion is to modify msg_athena.conf entries no. 544 and 545 to cooperate with the client. Or modify the client's msg to match eathena ;p
PS: a link to one old topic of mine:
@away, why is it here?.
This post has been edited by theultramage: Mar 21 2008, 02:05 AM