v.20 and multiple instances of the same plugin

[Alastair412]

What happens when more than one add-on makers post bundles using the same plugin? In particular, in the following scenario:

Add-on X ships with plugin x.dll (under Gamedata\X\Plugins\x.dll). Author of X later updates the plugin but the player doesn't notice or update.

Player then downloads add-on Y, which relies on the plugin from X, and bundles it with the latest version of the plugin. The game now has:

x.dll v1 under Gamedata\X\Plugins\x.dll

x.dll v2 under Gamedata\Y\Plugins\x.dll

How does KSP load the plugin(s) under that version? What happens when parts from either invoke properties that are defined differently in each version? And what is the recommended best practice for curating the plugins folders? Should both X and Y bundle as above, or should Y bundle x.dll under a X hierarchy, even if nothing else from X is present than the plugin?

[ghost010]

This is something that has been bugging me sins start of using ksp(18)

Why dont the moders just let you DL the dll apart from the mod pack.

This saves allot of trouble.

I had this probblems with couple of mods.dling bobcats home firts(new dll) than dling the mk4(old dll) and overwrite it(i always over write).

I always had to keep a log on what to install the last.