From 4.24 release notes:
The Developer type was used for editor modules that contain custom blueprint editors, graphs, and nodes. It could work through any of the editor play options. No other module type achieves this including the new DeveloperTool type.
The UncookedOnly replacement does work in all previous cases that the Developer type did, with one exception: when packaging a release build with blueprint nativization enabled for assets that were generated by this editor module. In this case the editor module is included along with the runtime module in the BpCodeGenManifest.json, when it clearly shouldn’t be. This fails to load of course as the module isn’t meant for cooked builds.
In 4.24 using the ‘Developer’ mode still works properly with the BpCodeGenManifest.json only containing the runtime module. I’ve compared the generated cpp files and I don’t see any real difference between them. It appears that the editor module is just being added to the manifest when it shouldn’t be.
This looks like a bug and I can create a issue, but if anyone has any suggestions first that would be great!