@TimSweeneyEpic From your point view, which are the API that would need a migration (the most important).
- Steamworks Web API (https://partner.steamgames.com/doc/webapi )
- Steamworks API (https://partner.steamgames.com/doc/webapi )
-
-
One of the big items would be separating social APIs from dependence on the store installation, either by exposing low level friend functionality via API or unbundling the overlay. These are all things we’re working on with EOS so friends can be used through any store.
-
Of course that’s just a short term evolution. Ultimately, we’d love to work with all platforms and stores to create protocol and file format standards for social features, so devs can support all without integrating numerous APIs.
- 8 more replies
New conversation -
-
-
Has anyone at Epic considered implementing Steamworks from scratch as something that talks to Epic servers instead of Valve’s?
-
I not think it's something really easy to do without the source code. But having a generic layer to make it more easy for each dev/publisher would be a good idea but all the stores need to talk about and define a standard so that it can work.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.