Conflict with LoadingScreenManager when ModuleManager is present

[UnanimousCoward]

I've come across an interesting little bug that took me a while to track down: The combination of KSPBurst, Module Manager and Loading Screen Manager will cause KSPBurst to fail - but only if there are more than about five user-specified loading screens.

Confirmed on a testing environment with only KSPBurst Compiler & Plugins, Loading Screen Manager and Module Manager installed through CKAN.

The game loads normally when there aren't any user-specified loading screens, but once you have more than about five images in the "UserLoadingScreens" folder, loading hangs with the message "KSPBurst: Waiting for Burst compiler..." and never progresses. (I say "about five images", because it seems to vary a little.)

I tested by adding multiple copies of the same image to the "UserLoadingScreens" folder - once there are five or six images in the folder, loading will fail. Take one or two out, and it loads fine. Remove Module Manager, and it loads fine. Module Manager isn't even running any patches, but it's somehow involved in the issue.

Logs here: Dropbox