Feature/door remote radial

[Fildrance]

About the PR

door remotes now use radial menu to chenge modes. Previously they used cycling over modes using 'use' keybind.

Why / Balance

fixing #31977
abusing new easy to create radials. neat stuff!

Technical details

Moved DoorRemote code from server to shared, mostly untouched, changed calls to doors system to use prediction and passed actual user uid (was using remote device as user).

Media

door-remote-radial-colored.mp4

Requirements

• I have read and am following the Pull Request and Changelog Guidelines.
• I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

🆑 Fildrance

• tweak: Door remotes now have a radial menu for changing modes.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[slarticodefast]

I fixed the merge conflicts and pushed some small cleanup.
Two things:

• The BUI uses StyleNano, which is now deprecated.
• Do we maybe want to keep the Status Control UI?

[Fildrance]

Changed to use new Palette, looks the same in game, changed it for ling too - less references of obsolete, less warnings! now about status control. I would like to keep it - it seems like we want more of those. But amount of boilerplate boggles me! I will look at it.

[Fildrance]

ItemStatusControl mispredicts awkwardly, no idea why. Will have to sleep with that thought.

[slarticodefast]

ItemStatusControl mispredicts awkwardly, no idea why. Will have to sleep with that thought.

Probably because it uses a frameupdate loop, which does randomly show whatever prediction is currently calculating.
Try instead making it event based, and add a IsFirstTimePredicted check for the UI change.

[Fildrance]

Well the FrameUpdate loop part was kinda obvious, but the problem with StatusControls is that they are all kinda doing updates in that loop - none of them are doing proper event-based stuff. This is kinda disgusting, but at the same time it means we dont get proper infrastructure to plug events in, unless we will commit several war crimes, like storing nullable control object inside system. Other controls avoid mispredict by exposing extra fields in component, that dictate state specifically for StatusControl. Thats an option, i guess, but... hell thats ugly...

[Fildrance]

Fixed mispredicts, but codewise its a small bloat of boilerplate, annoying AH. StatusControl stuff looks like it needs a refactor for a way to plug events in, but this PR is obviously not good place to start that.

[slarticodefast]

With only the auto handle state subscription update the status control won't show when picking it up, only when you first change the setting.

[slarticodefast]

Looks good to me, this is so much more convenient to use!

get dismissed