It's definitely not a scripting error looping the event either - the
traceback is just:
stack traceback:
[string "function mmp_downloaded_file(_, filename)..."]:2: in function
<[string
"function mmp_downloaded_file(_, filename)..."]:1>
So Mudlet itself is calling the function many times over.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1092769
Title:
Event handlers can go off multiple times
Status in Mudlet the MUD client:
New
Bug description:
Event handlers can somehow get into a state where they will
consistently go off more than once. In an example I've got, on one
profile run one event handler is going off 8 times, and another 144
times (!). Just raising the event makes it go off all those times,
consistently, until you restart Mudlet.
I haven't quite worked out what is causing this issue just yet, either
- this needs to be narrowed down. It does happen to everyone somewhat
infrequently however all the way from test4 and before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1092769/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mudlet-makers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mudlet-makers
More help : https://help.launchpad.net/ListHelp
