Packaged Game Ignoring "Default GameMode" Setting
I've set up a custom GameMode class for my game called ScreenGameMode that uses a custom PlayerController class, and I have it set in "Project Settings -> Maps & Modes" as "Default Game Mode." When I play in the editor it uses ScreenGameMode and my custom PlayerController correctly, but when I package a build, it uses the base GameMode instead and the base PlayerController class. Any ideas why this might be?
There's no "Game Mode Override" set in "World Settings." This is the first time I've tried to make a packaged build of this project.
I have upgrade this project a few times from older versions of UE4; I saw this question that sounds like possibly the same issue. Maybe I need to recreate my GameMode blueprints? Ugh! https://answers.unrealengine.com/questions/253263/wrong-playercontroller-in-cookedpackaged-version.html
asked Dec 31 '16 at 11:44 PM in Packaging & Deployment
Solved it. It looks like the issue is that if you define a custom GameMode in your settings, and then you move and/or rename that GameMode blueprint, the editor knows where to find the blueprint still but the Config\DefaultEngine.ini config file still points to the old path, which causes packaged builds to fail to load the custom GameMode and fall back on the base class GameMode. The fix was to simply go into "Project Settings -> Maps & Modes", change the "Default Game Mode" to GameMode and then back to my custom ScreenGameMode class. I probably could have also just updated DefaultEngine.ini manually to point it to the new location.
answered Jan 01 '17 at 12:01 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here