-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add steamworks transport #89
Add steamworks transport #89
Conversation
- added send packets
- added client - added optional bevy
Co-authored-by: lucaspoffo <35241085+lucaspoffo@users.noreply.github.com>
…enet into steam-transport
Thanks for the PR, did some small tweaks on the steam transport, mostly unifying some functions and making it more like the style I use. Also removed the demos and bevy_renet changes, the scope was too big, and is gonna take a while to get these ones right. Let's remove them for now and merge the transport for now. Added an echo example for renet_steam, which is pretty much the same one from 🎉 🎉 |
Target of this pr is to add SteamworkNetworkingSockets as a alternative transport.
This might require some changes on internal existing code, before breaking-changes are introduced in this pr will the maintainer be notified and possiblities discussed.
This has the advantage to have an existing relay system for P2P games, like coop games, the advantage is that the ip will not be revealed if its used in this context.
It has also the advantage that packages are already encrypted.
Fell always free to review code in the early Stage, it helps to discuss/correct this before further implemented and takes more time to actually change it.
Goals: