mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #04871
[Bug 1268114] Re: Newly-created looping aliases get their content erased
Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/759
This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.
** Bug watch added: github.com/Mudlet/Mudlet/issues #759
https://github.com/Mudlet/Mudlet/issues/759
** Changed in: mudlet
Status: New => Opinion
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1268114
Title:
Newly-created looping aliases get their content erased
Status in Mudlet:
Opinion
Bug description:
Newly-created looping aliases get their content erased - see attached
video demo.
Introduced by
https://github.com/Mudlet/Mudlet/commit/b925a00e537f675da4a0b3681968128577739cbd,
I suspect the issue lies in returning out of the function so early -
the function might be doing additional setup later on.
One idea is to instead self-disable the alias. Then it'll keep self-
disabling and stay disabled until the looping condition doesn't match
anymore.
As to whenever should it self-enable after the looping condition is
fixed, I'm not sure yet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1268114/+subscriptions
References