Game Piece Asset Support [AARD-1902]

[azaleacolburn]

Description

Game pieces are now treated as separate assets from the field, they are able to be spawned, deleted, cached, etc, all on their own.

Objectives

• Frontend configuration menu for game pieces
• Game pieces are returned as separate assemblies
• Game pieces are pruned from the main assembly
• Game pieces are treated like separate entities, neither fields nor robots and are configurable
• Game pieces still start in the same place on the field as before
• Game pieces cache properly
• Game pieces can be interacted with by robots as before
• Game pieces work in match mode as before

Testing Done

• Parsing fields (2023 & 2024) still works
• Game pieces can still be manipulated
• Game pieces can be configured
• Configuration and spawning UI works

Note

Fields no longer spawn with a transform gizmo attached

AARD-1902

[AlexD717]

When you spawn a field its name is now a game piece

@AlexD717 I can't replicate this, what field did you use?

This happens to me with almost every single field

Fission._.Synthesis.-.Google.Chrome.2025-07-14.08-54-48.mp4

[rutmanz]

I'm also seeing that but only in the spawn assets panel, the configure assets panel is unaffected

[AlexD717]

I'm also seeing that but only in the spawn assets panel, the configure assets panel is unaffected

I am also only seeing this in the spawn asset panel

[azaleacolburn]

@AlexD717 I couldn't reproduce because I had already cached this field, so it just kept the field in cache rather than trying to cache it but using the wrong scene object. Thank you for the visual.

[rutmanz]

Also looks like there's an error in the CacheInfo method when loading gamepieces, I imagine it doesn't actually matter for gamepieces but it would be nice to silence the error either way

[azaleacolburn]

Also looks like there's an error in the CacheInfo method when loading gamepieces, I imagine it doesn't actually matter for gamepieces but it would be nice to silence the error either way

Ya, Alexey already pointed that out, I'll just silence it.

[azaleacolburn]

Waiting on #1200 for a MirabufLoader testing suite.

[rutmanz]

Part of the JIRA ticket is to provide default gamepiece assets to use. Is that going to be part of this PR?

[rutmanz]

you can always just use bun x vite

[rutmanz]

but fusion seems to just mess with this stuff itself, I don't think you should commit the changes though. You can't gitignore them though if they're already tracked

[BrandonPacewic]

Are ball socket joints implemented? I'm kinda hesitant to remove this because I don't know what it does.

[azaleacolburn]

All I was doing here was removing the function CreateBallBadAgainConstraint which was already commented out. I think it's fine to remove an unused function because we can always get it back from an old commit if we really want to, there's no point in dead code in the codebase. Ball and socket joints are not implemented.