KNakamura

Because it's something Beth implemented in the engine. Any tools manipulating that engine should not allow output that is essentially garbage. A failure state is not a valid method of limitation. MO should not generate a plugin.txt that should cause crashes.(BTW: Tes5Edit will not allow loading past FE.)

Then I'll go file a ticket with Tes5Edit. You can't have more than FF load order. (Really, FE). Period. And fine, plugins. (I keep forgetting MO allows BSA unpacking) If you really need to merge more than 255, merge them in batches, but you really shouldn't allow 255. Because here's the thing: you can click "run" from that order even though it's intended for merging. It might not be a bad idea to ONLY allow it in a merging framework, and disengage it otherwise. I.E you have to tell it, specifically, to merge.

In a discussion, it came up that Mod Organizer will allow you to activate 257 mods and pass it to Wyre Bash. I wanted to file this in the tracker, but it's not up from the Nexus link. While it files a warning, it should straight out disallow it, as more than 255 mods will cause the engine to crash.

LvlPredatorScript bugfix - is it really a fix, does it work? ^ I'm only really bringing this up because it appears to have been fixed in the latest USKP. There is a bit of a warning note to it though: