Begin Play Event Not Firing

Hello everyone!

I have not been able to get the Begin Play Events to fire in either my Level Blueprint nor my Gamemode (both of which are set as my defaults in my settings). The Gamemode is set as the Level’s world settings. To describe it a bit more my level is just an empty level with nothing in it and when trying to set a breakpoint or any text prints in the Begin Play event neither work. I have tried playing it in the editor and as a packaged game neither worked. I have tried other projects and they seem to be functioning correctly. I’m trying to implement the online subsystem Steamworks and believe I have set everything for that up correctly.

I’m using 4.14.3

Thank you,

Das Joe

Could you show a screenshot of your blueprint?

The same exact nodes are in both the level blueprint (shown here) and the gamemode.

I don’t see any problems, maybe someone else can help?

What’s Up Averagejoe,

I hope everything is going well! So I am going to do my best to understand whats going on, and stepping through the problem usually helps me. So have you tried loading your Level without the GameMode you created. If you go into your World Settings, and override the GameMode to the default GameMode. See if your Event BeginPlay fires.

Peace,

[Peter L. Newton][2]

Also an additional note. Are you using Level Streaming?

1 Like

Hello Peter,

So it seems that when using the default Gamemode or creating a new one works! Though my current Gamemode I’m using has nothing in it so I don’t know what is wrong with it that would cause it to have problems like this. For now I’m just going to make a new and go from there.

Thank you,

Das Joe

EDIT: I think this might have been from a redirect error??

Hi Averagejoe,

I have the same issue, and thanks for your workaround.
I am using 4.17.2

Fixed this by changing my custom game mode parent class from GameModeBase to GameMode

Can Level streaming cause this problem?

I have this issue currently with WorldPartition. If this solution does not work, check the other issues on this bug

Related issue: