Brief summary of issue / Description of requested feature:

The changes to module priorities to help with module install seems to be causing a bug - if the module doesn't set it's priority within its own scripts, it gets reset to 0 after a single mudlet reboot...

I guess the initial loadup of modules is either a case 1 or case 3?

It'll load in the proper place the first reboot, but after loading fully it'll be at 0 priority within the module manager, and if you reboot again, it'll load in the 0 place