This change will enable mods that previously used VampireCommandFramework to switch to using Bloodstone.
Primarily the work behind this is factoring the existing VampireCommandFramework plugin into two assemblies, one that's a BepInEx pure library: VCF.Core , the other that's a V Rising plugin VampireCommandFramework, after 0.6.0 there is no longer a plugin by that name. Details: https://github.com/decaprime/VampireCommandFramework/pull/12
This change pulls VCF.Core in via the same package. Although it's not ideal to shift the purpose of the existing pacakge, these changes represent a choice in the road to no longer support a stand alone plugin hosting the framework; that hosting will be done here in Bloodstone. When you look at the changes you'll see the V Rising aspect is the minority of what we call VampireCommandFramework that now lives in Bloodstone.CommandFramework
For sake of transition and scope; I've maintained mostly the same namespaces from VampireCommandFramework for now. It's future work to reposition that repository as purely about the library.
This change will enable mods that previously used VampireCommandFramework to switch to using Bloodstone.
Primarily the work behind this is factoring the existing VampireCommandFramework plugin into two assemblies, one that's a BepInEx pure library:
VCF.Core, the other that's a V Rising pluginVampireCommandFramework, after 0.6.0 there is no longer a plugin by that name. Details: https://github.com/decaprime/VampireCommandFramework/pull/12This change pulls
VCF.Corein via the same package. Although it's not ideal to shift the purpose of the existing pacakge, these changes represent a choice in the road to no longer support a stand alone plugin hosting the framework; that hosting will be done here in Bloodstone. When you look at the changes you'll see the V Rising aspect is the minority of what we callVampireCommandFrameworkthat now lives inBloodstone.CommandFrameworkFor sake of transition and scope; I've maintained mostly the same namespaces from VampireCommandFramework for now. It's future work to reposition that repository as purely about the library.