Eric Anderson

Hi @wgwgamer, are you able to share a link to your project?

Almost all the fails appear to be in docs. They can probably all be fixed in one place (in the server side doc renderer, I believe)

Looks like an off-by-one error in the player state array: https://github.com/microsoft/pxt-common-packages/blob/a0bcbbee0b53f5e443e5693996904fd9a186ac8a/libs/multiplayer/player.ts#L169 Should read ```ts while (this._state.length

The player number thing looks like a different issue. It isn't converting to the JavaScript I would have expected. I get this: ```ts mp.getPlayerSprite(p4).sayText(convertToText(mp.getPlayerByNumber(number))) ``` What I expected: ```ts mp.getPlayerSprite(p4).sayText(convertToText(p4.number))...

Forum user reporting the player custom data issue: https://forum.makecode.com/t/why-doesnt-my-set-player-state-work/27988/2

We don't know if the data loss was due to performance. Worth collecting data loss reports in a separate issue though.

@martinwork can you kindly test with this build? https://microbit.staging.pxt.io/app/90d23a3465264bc5f2cb314fce5d4be956dd7b12-3596625c81# The hex it generates has a smaller footprint, but I'm having trouble pairing Bluetooth, unable to fully test with your sample.

@AlasdairAtKitronik, we found the regression and made a fix to our compiler backend. The fix will be available in the v6 editor, currently live in the beta channel (https://makecode.microbit.org/beta). Thanks...

There are many open questions like these around the game over blocks. Let me draw up designs and we'll review/refine before we implement anything. I'll be sure to address these...

Marking as done! Will open new issues for individual tweaks.