Developer Notes

This happens because GameMode is extended from GameModeBase to behave as a mutliplayer game mode and as such has specific match starting conditions that rely on the statemachine in GameState. The pawn is created but not ticked because the match has not started.


Using a game mode that contains a custom game state rather than the default seems to be disabling tick for other blueprints such as characters and actors.

Whenever the project is using a custom game state, tick is not running for other blueprints in the project.

Found in 4.14.2 CL# 3241561

Could not reproduce in 4.13.2 CL# 3172292, this is a regression.

Steps to Reproduce
  1. Open the editor
  2. Create a new game mode blueprint and set it to the default in Project Settings
  3. Create a new Game State blueprint and set that to the default in the Game Mode blueprint
  4. Create a new character blueprint and add it to the level
  5. In the Character blueprint, add a print string on tick
  6. PIE

Result: Tick is disabled for the character

Expected: Character tick would run

Have Comments or More Details?

Head over to the existing Questions & Answers thread and let us know what's up.

Login to Vote

Won't Fix
ComponentUE - Gameplay - Blueprint
Affects Versions4.14
Target Fix4.15
CreatedJan 5, 2017
ResolvedJan 12, 2017
UpdatedApr 27, 2018
View Jira Issue