Using the <local player> value in WorldBuilder often triggers a mismatch in-game.

[AdrianeYves]

Area(s) with this issue?

This bug is a graphical glitch or error

Describe the issue

local player is quite useful because it allows defining the player without needing to reference their specific index (e.g., "player-0 to player-7"). This means that using local player, an action can be triggered for all players without having to write separate scripts for each one—saving a lot of effort compared to manually creating eight scripts.

Unfortunately, local player tends to cause mismatches in multiplayer matches. While there are some scripts where local player works without issues, making it function correctly often requires using unconventional or "quirky" methods to avoid desync problems.

Steps to reproduce

1. Select a script that using a player as its default value in worldbuilder...
2. Select Local Player ...thats pretty much it

Attachments

No response