2.17 new plugin naming convention

[Amerio.Stephane]

Hi, In 2.17 the plugin naming convention has changed. It's not clear if the function virtual const char * get_name() override { return "MyPluginName"; } should now reflect the real plugin name <VendorName><PluginName> or if the string is totally free.

Is the returned string used in any way by the engine (apart from logging the loaded plugins name)?

Thanks!

[cash-metall]

Hello! 

16 hours ago, Amerio.Stephane said:

Is the returned string used in any way by the engine (apart from logging the loaded plugins name)?

this string is only used to identify the plugin (findPlugin, destroyPlugin, getPluginName)

note: when you call addPlugin("MyPlugin") , it will search by filename, but stored by get_name (because there can be several plugins in one dll). So we recommend keeping get_name and file name the same.