Facepunch.Steamworks VS Zenject

This link might help as it has a couple examples: https://github.com/Facepunch/Facepunch.Steamworks/issues/261

- I'm using Facepunch as the steam library - it's a nice wrapper around the steam SDK, which can be a little annoying to use directly.

If you are using Unity, have a look at the facepunch wrapper for the Steamworks SDK. It's pretty nice.

I’ve been using this. Very easy to use, has p2p support. https://github.com/Facepunch/Facepunch.Steamworks

I also tried to integrate Facepunch.Steamworks, but it didn't seem to be working on Apple Silicon (if I understand correctly). Facepunch's last release was also 2 years ago. Since the latest Steamworks.NET was released a month ago, I believe it's currently the way to go (despite the clunkier API) if you're trying to integrate Steam into your C# Godot Project.

Facepunch.Steamworks 2.3.2

Steam's latest networking API has built in support for using relays to hide p2p IP addresses. He was using Another Fucking Steamworks C# Implementation which appears to be based on the older network apis.

Depending on how you check various things, I'd recommend you use Facepunch.Steamworks which is free and available here: https://github.com/Facepunch/Facepunch.Steamworks

You can try Dependency Injection with Zenject. It’s more complicated than singletons, but has many advantages.

I just noticed I forgot to link the resource collection 😅 so here it is: https://procgen.space/resources and while we're on links and I'm on a computer now instead of my phone, here's a link to zenject: https://github.com/modesttree/Zenject

In Unity, there is the Zenject Asset: https://github.com/modesttree/Zenject

Mhhh I guess you could take a look at a dependency injection framework. https://github.com/modesttree/Zenject

Even better approach is to get rid of singletons with dependency injection. There are several frameworks for this, for example https://github.com/modesttree/Zenject.

Hello everyone! I love unity, it is a great game engine, but I always find myself back to the same architectural hurdles again and again. I used Zenject for several small projects, but I didn't completely like the approach it imposes. In order to improve on what I felt Zenject lacked, decided to make a dependency injection container that fit what I felt was necessary. https://github.com/PereViader/ManualDi.Main (core of the container, just c#) https://github.com/PereViader/ManualDi.Unity3d (extensions to improve usage in unity) As far as I know, dependency injection containers are not a very hot topic around the game dev sphere. Something I think is really not ideal for engineers, as I believe it greatly improves our productivity. What do you think of dependency injection in Unity? What do you think a dependency injection container should have for you to use them in your projects?

Zenject can be found here, and is a dependency injection (DI), which is also a design pattern.

If we are talking about bigger projects, then you cannot put everything into scene that's for sure. Also, creating a prefab for component that you want to inject is not the best option. Therefore, there are different solutions like Zenject.

Look into dependency injection, like Zenject. https://github.com/modesttree/Zenject