Nativized blueprints cause error in multiplayer

Apologies for the breakage. What’s the callstack at the time of the assertion?

Sounds like a regression may have been introduced in the hotfix if it wasn’t occurring for you in 4.18. Would you be able to confirm if it happens without Blueprint nativization enabled as well? If so, this will be a new issue.