You can find more information here: https://dev.mixer.com/blog/mixplaysdkchanges
The C++ Interactivity SDK supports client-side development with Mixer Interactivity. If you have not read through our Interactive Reference Documentation now is a great time to do that.
Checkout the Project's Wiki for documentation, including a Getting Started guide.
Clone the interactive-cpp repository.
$ git clone https://github.com/mixer/interactive-cpp.git interactive-cpp
Copy the source directory into your C++ game project (you will likely want to rename it). Add interactivity.cpp to your compilation list and include interactivity.h to get started.
See the InteractiveSample for an example of how you might handle authorization and connect to an interactive session.
If you don't plan on handling authorization yourself you can use the provided authorization helper functions. To do so you will need an OAuth client ID which you can obtain here: https://mixer.com/lab/oauth
This source code was designed to be easily consumed by any game project. Some of major design decisions include:
- A single header and unity build style cpp file.
- An extern "C" interface.
- No dependencies exposed in the header, all usage of STL and other libraries are quarantined from your game.
- Callbacks on the caller's thread for easy memory management and managed language interop.
- All interactive functions assume UTF-8 strings for input and output parameters.
The interactive-cpp repository is currently in a pre-release state. Please refer
to the release notes for more information.
Is there a feature missing that you'd like to see, or have you found a bug that you have a fix for? Do you have an idea or just interest in helping out in building the library? Let us know and we'd love to work with you. For a good starting point on where we are headed and feature ideas, take a look at our requested features and bugs or backlog.
Big or small we'd like to take your contributions to help improve the Mixer Interactivity API for everyone.
If you are looking for the previous version of the SDK it is preserved here.
We'd love to get your review score, whether good or bad, but even more than that, we want to fix your problem. If you submit your issue as a Review, we won't be able to respond to your problem and ask any follow-up questions that may be necessary. The most efficient way to do that is to open an issue in our issue tracker.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.