We recently upgraded from 4.7 to 4.8 and we’ve found that the custom GameState class we use is no longer created when we package a build and run it or when we use the launch option. The class settings for the game mode override the game state and it works as expected when we PIE or play standalone. This was working for us in 4.7.
Since posting this question I’ve also found that the PlayerController and PlayerState overrides for my GameMode aren’t being used either. I have a base game mode that all my other game modes inherit from and I originally had the defaults changed for the inherited ones but not the base. I found if I change them for the base game mode then the PlayerController and PlayerState classes are created correctly in shipping builds, though the GameState still isn’t.
Hi kgamble,
Are you using binary from the launcher or source version of the editor?
I’m using the launcher version (4.8.1 now though the behavior also occurred on 4.8.0)
Hello kgamble,
I have a few questions for you that will help narrow down what issue it is that you are experiencing.
Quick questions:
- Can you reproduce this issue in a clean project?
- If so, could you provide a detailed set of steps to reproduce this issue on our end?
- Could you provide screen shots of any blueprints that may be involved with this issue?
Hello kgamble,
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.
Thank you.
Sorry, I’ve been trying to figure out repro steps for this over the past couple days. None of my ideas have reproduced the issue unfortunately. Would you like me to send you the full project where this is occurring (I can try to strip out anything not related to this to make it simpler to debug)?
Hello kgamble,
Yes, it could be helpful to take a look at your project. If you could send in a simplified version with the steps to reproduce the issue in that project I will be happy to take a look.
Ok, I sent you a PM on the forums referencing this question with a link to the project.
Hello kgamble,
I have been taking a look at your project. However, I am unable to get a packaged build to play as it is. This is preventing me from testing the issue discussed above. Could you test the project that you sent me on your end and provide me with any steps needed to reproduce this on our end?
Ok, I pulled down the zip file I sent you and I wasn’t able to get the packaged build to run. However, I was able to repro my issue if I clicked the Launch button from the editor (you’ll have to launch on both FinalLevel and StephsLevel so they’re both cooked). I did realize that I left the Steam subsystem enabled, so you’ll have to make sure Steam is running on your computer and you’ll have to change the SteamDevAppId option in Config\DefaultEngine.ini to 480. If you definitely need it to work in Packaged builds though I can take a look and see if I can figure out why it stopped working.
Hello kgamble,
After doing a bit more digging I was able to reproduce this issue on our end with your project. I also found that you are using the VictoryPlugin by . Is it possible for you to submit a build without this plugin that still reproduces this issue? This is not an officially supported plugin and we would like to eliminate the possibility any interference from the plugin.
I tried to remove the VictoryPlugin before I sent the project to you but when I disable it through the Plugins window in the editor (or just delete the folder) the editor crashes the next time I start the project, so I decided to leave it in.
Hello kgamble,
You will need to speak with for assistance on removing this plug in safely from the project. Once that has been accomplished if the issue is still occurring I will be more than happy to assist you further.