-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Testing] MagitekStratagem v0.10 - Builtin server #5207
base: main
Are you sure you want to change the base?
Conversation
Outdated attemptBuilds failed, please check action output. Take care! Please test your plugins in-game before submitting them here to prevent crashes and instability. We really appreciate it! The average merge time for plugin updates is currently 9 hours.
17 Needs (✅ All reviewed)
9 hidden needs (known safe NuGet packages).Show log - Review |
Have you been able to investigate this / figure out a way forward? |
As far as I understand, there are .net packages that need to be whitelisted in order for the solution to build. |
Great, I'll hand it over to @goaaats to figure out then |
Head branch was pushed to by a user without write access
Builds failed, please check action output. Take care! Please test your plugins in-game before submitting them here to prevent crashes and instability. We really appreciate it!
17 Needs (
|
Type | Name | Version | Reviewed by |
---|---|---|---|
NuGet | Microsoft.AspNetCore.SignalR.Client | 8.0.11 | |
NuGet | Microsoft.AspNetCore.Connections.Abstractions | 8.0.11 | |
NuGet | Microsoft.AspNetCore.Http.Connections.Client | 8.0.11 | |
NuGet | Microsoft.AspNetCore.Http.Connections.Common | 8.0.11 | |
NuGet | Microsoft.AspNetCore.SignalR.Client.Core | 8.0.11 | |
NuGet | Microsoft.AspNetCore.SignalR.Common | 8.0.11 | |
NuGet | Microsoft.AspNetCore.SignalR.Protocols.Json | 8.0.11 | |
NuGet | System.IO.Pipelines | 8.0.0 | reiichi001 |
Testing a followup idea to separating the plugin and tracker integration code:
This experimental new version of the plugin includes an entrypoint with which the plugin can be executed as the server.
This allows a separation of processes between the plugin + client, and native integrations + server, without requiring users download an external dependency, and mantaining all code compiled by the pipelines (hopefully this works!)
Unfortunately this also means the plugin itself is much bigger, as it has to bring along the required dependencies to run the AspNet server. Hopefully this won't be a major issue.