This final blog post documents the critical phase of integrating the designer’s map into our project and overcoming significant technical challenges in the process.
Map Integration & Version Conflict
After receiving the map from the designers on 04/05/2025, I discovered they had been working with an outdated version of our Unity project. This created a severe version conflict – when I integrated their map, all my previously created animations were deleted from the project.
Recovery Process: Using a Backup Laptop
When the map integration caused major project issues due to version conflicts, I was able to recover my work by leveraging my other laptop, which still had the last stable version of the project. Since this laptop had not been updated with the problematic changes, I was able to copy the necessary files-such as animation controllers, prefabs, and scripts-directly from it.
This approach aligns with Unity community best practices for project recovery: always keep a full backup of your project on a separate device or drive, especially before major updates or integrations. By opening the backup project on my backup laptop, I could export the required assets and then re-import them into the main project, minimizing data loss and speeding up the restoration process.
Technical Fixes
Several critical issues required immediate attention:
- Collision Detection: Multiple objects in the designer’s map lacked colliders, causing players to fall through the terrain. I added mesh colliders to all interactive surfaces, ensuring they weren’t marked as triggers and positioning character spawns slightly above ground level
- Enemy Spawner Reconstruction: The enemy spawners broke during integration, requiring a rebuild. I carefully placed them throughout the map and verified they wouldn’t cause runtime crashes, which had been an issue in earlier development
Work-in-Progress Documentation
I’ve begun creating video documentation of our project’s functionality, capturing the current state with plans to update as we finalize features. This serves both as course documentation and potential portfolio material.
Reflection
This challenging integration process emphasized the critical importance of:
- Consistent version control practices across team members
- Regular prefab backups for critical game elements
- Clear communication about project versioning with designers
- Thorough testing of physics interactions after major integrations
References
- Unity Technologies. (2025). Unity Editor Documentation. Retrieved from https://docs.unity3d.com/Manual/
- Photon Engine. (2025). Networked Physics in Fusion. Retrieved from https://www.photonengine.com
- GitHub Repository: pokimoki99/CGM
- Imgur. (2025). Image Hosting. Retrieved from https://imgur.com
- Clipchamp. (2025). Clipchamp Video Editor [Software]. Microsoft. Retrieved from https://clipchamp.com
Viktor Yankulchovski`s Blog 