Nathaniel Mitchell

Confirmed via Discord that the fix is functional.

I'm doing some testing of this. Worth to note, there is already some basic framework setup using [vue-i18n](https://github.com/beyond-all-reason/bar-lobby/blob/f46091b639d4a1fe0b33570338c3d85fb7964f5f/src/renderer/index.ts#L41), so my plan is to validate that it is set up correctly...

Tachyon now supports requests/events for the ``lobby`` endpoint (see [docs](https://github.com/beyond-all-reason/tachyon/blob/master/docs/schema/lobby.md)). I have an active branch on my fork that implements these requests/events (see [tachyon-lobbies](https://github.com/Hectate/bar-lobby/tree/tachyon-lobbies)). This branch will be the basis...

I reviewed this with @scottsaunders and this issue will be closed for the following reasons: 1. #505 Resolves several/all of the connection/communication issues presented here. 2. UI Team is not...

> I'm way less sure about this one. I'm not convinced spending effort of supporting this half-installed state is worth it at all. With the steam install ~everything will be...

Small FYI, I was not able to replicate this on ``master`` on Windows 11 (launched from ``npm run start``).

Discussion: https://discord.com/channels/549281623154229250/1427096722890559528 Resolved points: 1. Protocol changes would be required to include more player data in the lobby preview. Until said details are added the player list area will be...

From a brief research, the issue appears to be that the following code results in a Promise. https://github.com/beyond-all-reason/bar-lobby/blob/4af7468b778f046e3f21456026c691a5832118bc/src/main/services/shell.service.ts#L27 In cases where there are no problems, the Promise resolves silently to...

I believe this issue was resolved with #471 and #484, with changes in #492 to further refine the subscribe/unsubscribe aspects.

I have a branch active with all the tachyon requests/events for Party support functional. There is no UI development added to it at this time.