# How to use an Unreal source build as a packaged one

**URL:** <https://forums.unrealengine.com/t/how-to-use-an-unreal-source-build-as-a-packaged-one/2409765>\
**Category:** Platform & Builds\
**Tags:** engine, engine-compile, unreal-engine, Engine-Source-GitHub, editor, question\
**Created:** [March 23, 2025, 1:24am UTC](https://forums.unrealengine.com/t/how-to-use-an-unreal-source-build-as-a-packaged-one/2409765 "2025-03-23T01:24:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [March 23, 2025, 1:24am UTC](https://forums.unrealengine.com/t/how-to-use-an-unreal-source-build-as-a-packaged-one/2409765/1 "2025-03-23T01:24:09Z")

</div>

Hey everyone,

Up until now, I’ve been using a source build of the engine that is the same version as the project I’m working on, and just excluding the changed engine build identifier from ever being committed. I do also have some minor UI changes baked in that aren’t able to be changed without source, but it doesn’t change anything that isn’t purely UI.

That works, but I feel there has to be a better way. Can I get projects to automatically use my custom build instead of the launcher-provided version?

Thank you!

---

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [March 25, 2025, 4:02pm UTC](https://forums.unrealengine.com/t/how-to-use-an-unreal-source-build-as-a-packaged-one/2409765/2 "2025-03-25T16:02:30Z")

</div>

Well I found a sort of compromise…

By placing the source inside the directory the engine is installed, deleting the install that’s already there, and renaming the source folder to be same as the just deleted folder, it will instead use the custom engine.  
Only problem with this is that it prevents the use of the normal, non-custom engine of that version. Not a big problem or anything, but less desirable.

If anyone ends up finding a better way to do it, please let me know!

---

<div class="post-metadata">

**Author:** ![system](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/1/3/713c9d3f58553f0de89543d76a8a3a2779dc9fa4.png) [@system](https://forums.unrealengine.com/u/system)\
**Post date:** [April 24, 2025, 4:03pm UTC](https://forums.unrealengine.com/t/how-to-use-an-unreal-source-build-as-a-packaged-one/2409765/3 "2025-04-24T16:03:13Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.