Currently MO2 only enforces the hardcoded and ESM plugins placement and does not either enforce or warn in case a plugin that a plugin master is loaded after the plugin requiring it.
Technically the game will load fine anyways since it will just force load the measter when it finds the plugin requiring it, but MO2 is still displaying incorrect form ID prefixes.
Possible solutions:
1) Enforce the rule and whenever a plugin is detected that has a master automatically move it after it's master. if it isn't already.
Problem with this solution is that people might not expect this to happen and feel frustrated to the program doing things it wasn't asked for (for example while manually sorting the load order having MO mess with it might be annoying).
2) To avoid the above problem MO2 could limit it self to just display a warning of the incorrect order and offering a guided fix for it. This would probably be the easiest option to implement.
3) Use a detached system of order and form ID where at least the for ID is always calculated correctly even if the order is not correct.
Al12rs
commented
4 years ago
The problem
Currently MO2 only enforces the hardcoded and ESM plugins placement and does not either enforce or warn in case a plugin that a plugin master is loaded after the plugin requiring it.
Technically the game will load fine anyways since it will just force load the measter when it finds the plugin requiring it, but MO2 is still displaying incorrect form ID prefixes.
Possible solutions:
1) Enforce the rule and whenever a plugin is detected that has a master automatically move it after it's master. if it isn't already. Problem with this solution is that people might not expect this to happen and feel frustrated to the program doing things it wasn't asked for (for example while manually sorting the load order having MO mess with it might be annoying).
2) To avoid the above problem MO2 could limit it self to just display a warning of the incorrect order and offering a guided fix for it. This would probably be the easiest option to implement.
3) Use a detached system of order and form ID where at least the for ID is always calculated correctly even if the order is not correct.