Client Plugin SDK Outdated?

[JordieDevs]

Hello,

Just recently downloaded the Client Customization SDK, and built the Test Plugin, and apparently, it's out of date?

Screenshot:



Any help would be appreciated.

Thanks!

[Ray.Gamma]

If you look at version 3.1.1.1 of the SDK, in pluginsdk/src/plugin.c you will find

#define PLUGIN_API_VERSION 22

Do you have that in your code?

[JordieDevs]

If you look at version 3.1.1.1 of the SDK, in pluginsdk/src/plugin.c you will find

#define PLUGIN_API_VERSION 22

Do you have that in your code?

Yeah I do.

[Chris]

Other than outright specifying the wrong API version in your plugin source a different cause are missing dependencies. That is your built plugin has unresolved dependencies.

Which compiler did you use to compile it?

[JordieDevs]

Literally just the default Visual Studio compiler. And this is the test plugin that is provided by you guys. I didn't change anything at all.

[Chris]

Well it still depends on the version. If you build with VS 2012 for example, you will need a different runtime library, which is not shipped. Though it should work at least on the system you used to build it, as the correct one is installed on that one.

[JordieDevs]

I'm using VS 2015 Community so, Im still not exactly sure what the issue is, im gonna try messing around with the build settings.

[JordieDevs]

Here is the code https://pastebin.com/6YXm674K

When I build, it gives out the DLL. I put that in the %appdata%/Roaming/TS3Client/plugins directory, and then when I reload I still get the same error.

[Thomas]

The clientlog might have a more verbose output about what went wrong.

[thorwe]

I don't recall if it's the exact syndrome, however could also be that you're using a 64bit client and compile the plugin for 32bit.
Let's not forget that a 32bit client only works with 32bit plugins, and a 64bit client only with 64bit plugins and there's the file postfix convention to prevent the client to try to load the wrong ones.