Occupant property of
Seat, as well as the
SeatPart property of
Humanoid is not properly being replicated to players who join the game after another player already sat in a seat, for players who join after another player has already sat in a seat, the
Occupant properties will be
nil for the respective Humanoid and Seat, despite a
SeatWeld being visible on all clients, including new ones. If the sat player jumps and sits back on the seat, all properties are then correct again.
I have an uncopylocked repro place here which displays the
Occupant property of a seat, whether or not there is a
SeatWeld instance as a child of it and the
SeatPart property of all the other
Humanoids in the game, output is displayed on both client and server output.
I’m able to reproduce 100% of the time:
- Join the game on one account and sit in the seat, open F9 client output to view status of properties.
- Join the same server on a different account and view the F9 client output to see
The behaviour I’m expecting new players to see is for the
SeatPart property to point to the sat
Humanoid and for the
SeatPart property to point to the
Humanoid is sat on.
I’ve only just had a report of this bug and I’ve only tested and repro’d on a Windows 10 PC so far.