You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has been a lot of modders using this library to add rich presence to their favourite games. It often comes up how to however as Unity doesn't like the default named pipe implementation.
I have fixed this in my lachee/unity-rpc-unity which uses my lachee/unity-named-pipes to provide a custom implementation of named pipes for C#.
Should this be included in this package by default? The core of the package doesn't actually include anything unity related, just a wrapper around a native library?
Pros:
modders can just use the included UnityNamedPipe in the constructor
no hassle trying to figure out how to build the native library or what files to extract from other packages
Cons:
Extra bloat in the nuget package
Requires a native library to be built
Cross-Library & GitHub
I dont want to work with native libraries they are annoying
Should Lachee/unity-named-pipes be included with the Nuget?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There has been a lot of modders using this library to add rich presence to their favourite games. It often comes up how to however as Unity doesn't like the default named pipe implementation.
I have fixed this in my lachee/unity-rpc-unity which uses my lachee/unity-named-pipes to provide a custom implementation of named pipes for C#.
Should this be included in this package by default? The core of the package doesn't actually include anything unity related, just a wrapper around a native library?
Pros:
Cons:
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions