A tiny wand, robe, or broom mod should not automatically require a 250MB download. The April 17, 2025 Creator Kit update removed the need for the Development Asset Registry File that had caused a size floor for many mods. Authors who published before that fix need to send an updated build through CurseForge cloud cooking for their downloads to shrink.
Quick answer
Update the Creator Kit via Epic Games, back up your original project, validate your assets, and re-upload the mod for a fresh CurseForge cloud cook. The April 2025 patch removed the old Development Asset Registry requirement; there is no need to hunt down and delete files from the editor installation. A 5–20MB result may be possible for a simple cosmetic, but it is not guaranteed for every mod.
6 steps, in the right order.
Work through the Creator Kit repair process in order. Save a project backup and validate content before publishing anything new.
Confirm your Creator Kit build is current
Open Epic Games Launcher → Library → Hogwarts Legacy Creator Kit. Install any pending updates and launch from the Epic launcher. The official 17 April 2025 notes identify Creator Kit build 1372712 as removing the old registry-file requirement. Newer builds should include the change.
Back up the project and keep only required assets
Save your mod project to independent storage or source control. Review any textures, materials, meshes, and references that the mod includes. Remove unused references from your mod content, not unrelated engine files. Fix redirectors and excessively long paths if validation identifies them.
Run validation before the cloud cook
Select mod assets in the Content Browser and choose Assets Validation, or use PEEVES Asset Tool → Report → Verify. Resolve missing references and cook errors. A clean validation does not promise a particular file size but reduces avoidable failures.
Re-upload the existing mod as an update on CurseForge
Use Upload to CurseForge from the Creator Kit after checking the account is linked. Select the existing project and upload an update rather than accidentally publishing a new duplicate. Follow the current widget prompts, which may change with Creator Kit versions.
Let the updated mod complete cloud cooking
CurseForge handles the cooking pipeline. Wait for the build to finish and the update to pass whatever review is required, then inspect the resulting downloadable version. Re-uploading and re-cooking is the official way to apply the April 2025 size reduction to previously published mods.
Compare actual file sizes and test subscribers’ path
Record the previous package size, the freshly cooked package size, and whether the new version installs through the in-game mod experience. Test the intended wand, robe, or broom function in a separate modded save. If still over 250MB, inspect dependencies rather than assuming the patch failed.
Important technical note
Size reality check: The developer fixed a minimum-size limitation, not the size of your real textures, skeletal meshes, sounds, or dependencies. There is no documented need to manually delete a development registry file from the installed Creator Kit; direct editing of engine cook settings may break updates.
Frequently asked questions
Did the April Creator Kit patch introduce the 250MB problem?
No. The April 17, 2025 patch removed a pre-existing limitation by removing the Development Asset Registry File requirement.
Will every wand or clothing mod become 5MB–20MB?
No. Those are illustrative target sizes. Real output depends on asset types, textures, meshes, references and cloud cooking.
Should I manually delete DevelopmentAssetRegistry.bin?
Avoid deleting files from the installed Creator Kit or modifying official generated packages. Update the editor and re-upload through the supported CurseForge workflow.
Do old published mods shrink by themselves?
No. Official notes specify that existing published mods must be re-uploaded and re-cooked as updates for the size reduction.
Why is my new build still very large?
Check referenced and duplicated textures, dependent meshes, large maps, accidental bundled content, and the version of the Creator Kit. Inspect the actual cooked archive rather than just a source folder.
Do subscribers need to reinstall a different mod?
When your existing project receives a new approved version, subscribers should receive that version through the normal update flow; confirm its display and staging in the current in-game mod UI.
Official sources
Based on April 2025 patch notes and CurseForge Creator Kit documentation. UI labels and tools may change as later updates arrive.