RootVehicle tag missing for players when multiple players ride a multi-passenger entity

Description

When a player is riding on a multi-passenger entity (such as a camel or happy ghast), the command

/data get entity @s RootVehicle

/data get entity @s RootVehicle

normally returns the correct root vehicle data, meaning the RootVehicle tag exists in the player's entity data.

However, if multiple players are riding the same multi-passenger entity at the same time, the RootVehicle tag is missing from each player's entity data, executing the same command on any of these players will fail to return valid data. Instead, the game outputs:

Found no elements matching RootVehicle

Found no elements matching RootVehicle

This behavior is inconsistent. The riding state exists, and players are clearly attached to the entity, yet their RootVehicle tag becomes inaccessible only in the multi-player-riding scenario.

Expected Behavior

Whether riding alone or with multiple players, each player's entity data should contain the RootVehicle tag, correctly reflecting the root entity they are riding, regardless of:

• Whether one or multiple players are riding the same entity

• Whether the entity supports multiple passengers

As long as the player is mounted, the root vehicle should be retrievable.

Actual Result

When multiple players ride the same entity, the RootVehicle tag is missing in all players’ entity data, making it impossible to retrieve root vehicle information such as using /data get entity @s RootVehicle.

Reproduce

1. Summon a multi-passenger entity, for example a camel:

   /summon camel ~ ~ ~

   /summon camel ~ ~ ~

2. Have Player A ride the camel.

3. Have Player B also ride the camel.

4. Both players run:

   /data get entity @s RootVehicle

   /data get entity @s RootVehicle

5. The game returns:

   Found no elements matching RootVehicle

   Found no elements matching RootVehicle

If only one player is riding the camel, the command works correctly.