Mingwei Samuel

Ah, looks like the gamemmode is `PRACTICETOOL` which is missing from the enum. Didn't realize practice tool games could be public

Should be fixed in `3.0.0-nightly-2022-04-12-9fe967ddf9`

Also would help for `gameModes`, for issues like #84

Are you mainly interested in making an user interactive app that hooks into LCU, or just want to collect data?

Which endpoints are you planning on using? We should pick some to support initially and add more as needed Endpoints to be included (preliminary): ## Control * GET/POST/DELETE `/lol-login/v1/session` *...

Alright, I have an initial version that you can test. https://www.nuget.org/packages/Camille.Lcu/ Currently the setup is pretty hidden from the user, just calling `var lcu = new Lcu()` reads the lockfile...

Will put that down as a TODO, but unfortunately don't have time to work on it this week

Looks like it will be easiest to just support .net core & standard 2.1+ due to the custom cert used by the client https://docs.microsoft.com/en-us/dotnet/api/system.net.websockets.clientwebsocketoptions.remotecertificatevalidationcallback?view=netcore-3.0#System_Net_WebSockets_ClientWebSocketOptions_RemoteCertificateValidationCallback ~~Could enable the Riot CA cert...

Any opinions on what the interface should look like? My philosophy has been for Camille to do as little as possible to get a one-to-one mapping between the methods available...

Ah, I meant "interface" in the more general way of how the API would look like on the outside. Anyway, I have a first-pass version: https://github.com/MingweiSamuel/Camille/blob/0b45aca/Camille.Lcu.Test/UnitTest1.cs#L18-L48 https://www.nuget.org/packages/Camille.Lcu/3.0.1-nightly-2019-11-30-0b45aca4fa Essentially there is...