UE4.18-to-UE5.7 Migration
Budget: $10 – $80 USD
The multiplayer horror game I have in development currently compiles under a heavily-modified Unreal Engine 4.18 source build. I now need the entire C++ codebase—including my custom engine tweaks and several third-party plugins—brought forward to Unreal Engine 5.7.
Scope of work
• Update all engine-level changes I made in 4.18 so they apply cleanly to the UE 5.7 branch.
• Resolve build errors and deprecated API calls across the core game code as well as the plugins.
• Pay special attention to the networking layer and the custom input system, as these are the areas most likely to break.
• Produce a UE 5.7 project that opens, compiles, and runs in the editor without warnings or runtime crashes. I’ll handle any Blueprint or asset-side adjustments myself.
Deliverables
1. A Git branch or zipped project that builds in Unreal Engine 5.7 with Visual Studio on Windows.
2. A brief migration report highlighting the fixes you applied, any engine changes that were re-implemented, and any limitations or follow-up items.
Acceptance criteria
• “Build” and “Play in Editor” succeed on a clean checkout using UE 5.7.
• No blocking errors in output log; warnings are acceptable only if they do not affect gameplay or packaging.
• Networking session launches with at least two clients in PIE.
If you’re comfortable diving into legacy engine code and untangling multiplayer C++, your expertise will keep this project moving forward.
Scope of work
• Update all engine-level changes I made in 4.18 so they apply cleanly to the UE 5.7 branch.
• Resolve build errors and deprecated API calls across the core game code as well as the plugins.
• Pay special attention to the networking layer and the custom input system, as these are the areas most likely to break.
• Produce a UE 5.7 project that opens, compiles, and runs in the editor without warnings or runtime crashes. I’ll handle any Blueprint or asset-side adjustments myself.
Deliverables
1. A Git branch or zipped project that builds in Unreal Engine 5.7 with Visual Studio on Windows.
2. A brief migration report highlighting the fixes you applied, any engine changes that were re-implemented, and any limitations or follow-up items.
Acceptance criteria
• “Build” and “Play in Editor” succeed on a clean checkout using UE 5.7.
• No blocking errors in output log; warnings are acceptable only if they do not affect gameplay or packaging.
• Networking session launches with at least two clients in PIE.
If you’re comfortable diving into legacy engine code and untangling multiplayer C++, your expertise will keep this project moving forward.