Game Analytics API Plugin
Analytics is a feature I have long thought was a good candidate to be moved into a plugin.
- It is an optional features that only some users care about.
- It imports some pretty big third-party libraries into the engine.
- It requires an extra DLL be distributed with your game.
- It's a totally self-contained features that is easy to separate out from the rest of the engine.
I have uploaded my code for Analytics in Leadwerks here as a new empty Visual Studio project:
https://github.com/Leadwerks/PluginSDK/tree/master/Game Analytics
This will be a good test case to see how we can implement API plugins. An API plugin is an optional module that adds new commands to the engine. It should work with C++, Lua, and C#.
How do we do this? I'm not sure what the best way is. Do we want to try to make an object-oriented API like the rest of the engine, or should we just stick to a simpler procedural API? I putting this out now so we can discuss and determine the best way to handle this.
Here is some info on using sol to expose an API from a DLL:
https://github.com/ThePhD/sol2/tree/develop/examples/require_dll_example
If we can make this plugin work then it will serve as an example for how all API plugins should be integrated. Please take a look at tell me how you would like this to work.
- 3
10 Comments
Recommended Comments