mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Public bug reported:

Practical problem: it's necessary for a module to be able to be loaded
and be first, before the users triggers/scripts. This way, the user can
overwrite triggers / scripts with their own things, keeping their
changes when they upgrade the module.

At the moment, the user has to manually move the trigger/script folders
of the module after ever upgrade for their changes to stay.

Proposed solution: allow modules to be loaded, that is, be listed before
triggers/aliases. I don't think all modules should do this by default,
as taking up space on top means the user will have to constantly scroll
down to their own things if they have many modules installed. It should
be configurable per-module.

One way to accomplish this would be through negative module priority -
allow -1 to be the first module loaded that's before users scripts, -2
the second, and so on. 0+ priorities would still be loaded post-
triggers/script as before.

** Affects: mudlet
     Importance: Wishlist
         Status: New

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1096550

Title:
  Allow pre-profile module loading

Status in Mudlet the MUD client:
  New

Bug description:
  Practical problem: it's necessary for a module to be able to be loaded
  and be first, before the users triggers/scripts. This way, the user
  can overwrite triggers / scripts with their own things, keeping their
  changes when they upgrade the module.

  At the moment, the user has to manually move the trigger/script
  folders of the module after ever upgrade for their changes to stay.

  Proposed solution: allow modules to be loaded, that is, be listed
  before triggers/aliases. I don't think all modules should do this by
  default, as taking up space on top means the user will have to
  constantly scroll down to their own things if they have many modules
  installed. It should be configurable per-module.

  One way to accomplish this would be through negative module priority -
  allow -1 to be the first module loaded that's before users scripts, -2
  the second, and so on. 0+ priorities would still be loaded post-
  triggers/script as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1096550/+subscriptions