hmm… well I’m guessing that for your own ongoing project you’re using C++ and your inv system in it and would prefer to only maintain the one going forward (The one you use). Which makes sense. Personally I don’t care if updates stop for the blueprint version. Support as well at this point. I know BP well enough to figure it out on my own. Same goes for updating it for later versions of ue4. So my opinion is I don’t mind if the BP version stops, support and updates. That said, whether its calsses exposed to BP with nodes or all C++ many purchasers are going to struggle. It would be easier on you if they just didnt buy it. The users that know C++ or at least know how to read and modify the code would still buy. (which is maybe what you want in the end).
Having spent some time modifying the JSON pluging to add missing JSON features to my BPs I don’t mind this method. But for more complex things I’d consider it kind of a waste of time and if I had to do it over and this was already a c++ exclusive or hybrid, I’d go with a different BP system in that case. Trying to figure out how to make it so that when an item is added to back pack to check the quick bar and remove it from there if its a quick item, would be too much time to make it worth it for example. Unless you were planning on being around to supply code for requested features, I really don’t think JCInventory (or any inv systems ) are robust enough to function long term for any project out of the box. Which means adding features.
**TLDR: **personally I’m fine if you switch it. I won’t be adding any new updates that you provide to my version (which is still the first version I got) since its already very modified and I can maintain the updates to BP as needed. I wouldnt mind a C++ version as well though for future use. I’m assuming if it switches (and both products arent maintained) purchasers would already have access to it. The BP version if no longer updated may be removed from market though, not sure what the process is for that kinda thing. Either way, support for both versions would be a burden for sure.