If two or more plugins that use libxplanemp are active, then one of them will successfully register the OBJ8 CSL animation datarefs, and the other(s) will fail to register them, causing graphical glitches for the unlucky plugin(s), like landing gear being always retracted.
I was pleased to read about what you're doing for libxplanemp 2.0, and I hope it can go some way towards reducing the proliferation of forks of the library. The problem with the datarefs could be solved by using shared datarefs, and libxplanemp 2.0 seems like a good time to make that change, if you were so inclined to do so.
See https://developer.x-plane.com/sdk/XPLMDataAccess/#SHARING%20DATA%20BETWEEN%20MULTIPLE%20PLUGINS
If two or more plugins that use libxplanemp are active, then one of them will successfully register the OBJ8 CSL animation datarefs, and the other(s) will fail to register them, causing graphical glitches for the unlucky plugin(s), like landing gear being always retracted.
I was pleased to read about what you're doing for libxplanemp 2.0, and I hope it can go some way towards reducing the proliferation of forks of the library. The problem with the datarefs could be solved by using shared datarefs, and libxplanemp 2.0 seems like a good time to make that change, if you were so inclined to do so.
See https://developer.x-plane.com/sdk/XPLMDataAccess/#SHARING%20DATA%20BETWEEN%20MULTIPLE%20PLUGINS