I decided to be adventurous, and intentially created a
trigger loop.
I triggered off of a chat channel, and put into that chat
channel the same string needed to re-trigger the trigger,
by the letter.
The result didn't cause an overflow (good), but it did
spam the channel until it was disabled, and even then it
triggered off of the trigger echos in the main screen.
While not a critical problem, it can indeed cause
problems (I have to open the trigger menu to disable it)
and resulted in Cland disconnecting me after the
command spam forced a log off.
On a plus note (or a possible issue) is that the loop
triggered in groups of about 6 lines, and waited for a
response from Cland seemingly before it sent another 6
lines (might be 5 to 8, didn't check.)
Possible solutions, albit perhaps temporary ones, would
be a way to quickly disable all triggers (like an icon next
to the input prompt in zMUD), and even loop detection
or such.
Logged In: YES
user_id=840243
The triggering groups were expectd. Each time the mud
echoed a reply, it triggered off of the reply, as well as your
previous trigger echoes. The result was that each time the
trigger ran, the number of echoes you saw increased by one,
until the mud stopped sending replies.
At present, triggers do not function when disconnected from
the mud, so eventually, the loop would have terminated.
However, I do plan to add trigger loop protection/disabling
triggering off of triggers whenever *cough* we have a
working preference system.
Could you add a feature request for the above? That'd be
handy, and ensure that it doesn't slip my mind :p
Logged In: YES
user_id=712025
Bug moved and renamed to a feature request.