# Why is LovenseToySupportConfig.json required for the Unity plugin

**URL:** <https://forum.developer.lovense.com/t/why-is-lovensetoysupportconfig-json-required-for-the-unity-plugin/180>\
**Category:** General\
**Created:** [November 29, 2023, 2:17pm UTC](https://forum.developer.lovense.com/t/why-is-lovensetoysupportconfig-json-required-for-the-unity-plugin/180 "2023-11-29T14:17:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![isaacclarke80\_59](https://avatars.discourse-cdn.com/v4/letter/i/48db29/32.png) [@isaacclarke80\_59](https://forum.developer.lovense.com/u/isaacclarke80_59)\
**Post date:** [November 29, 2023, 2:17pm UTC](https://forum.developer.lovense.com/t/why-is-lovensetoysupportconfig-json-required-for-the-unity-plugin/180/1 "2023-11-29T14:17:35Z")

</div>

According to the [documentation](https://developers.lovense.com/docs/game-engine-plugins/unity-plugin-remote.html#import-the-plugin) (section 4), the developer has to keep the [LovenseToySupportConfig.json](https://developers.lovense.com/LovenseToySupportConfig.json) file up to date to provide support for newer toys.

Why isn’t this handled by Lovense Remote? It could return the configurations of all the toys the user has - and the user would only need to keep the one application “up to date” to support all their toys.

I notice version 1.3 is the current (supporting Solace) - but the latest version of Third Crisis only has 1.2 which means that if support on it suddenly stops then Solace onwards will never be supported.