Stoder

@yilmas After reading your post I had to double check and run all of the tests again and it looks like I need to make a retraction. Yup, its entirely user error. Somehow, while updating my mods and installing new ones managed to copy the AGExt folder into the game data folder rather than Diazo/AGExt. So yeah, completely user error on both our parts. @Diazo I hope I didn't end up wasting any of your time tracking down a bug that doesn't exist. The one silver lining to all this is now I've got all the other mods I was having a blast with and AGExt all at the same time. My game is beginning to feel perfect. Thanks again for all of your effort Diazo. Keep up the good work.

@Diazo Edit: Disregard, this is not a bug with AGExt but appears to be a result of copying over just the AGExt folder and plugin into the gamedata folder. Rather than having the file structure as Gamedata/Diazo/AGExt. In short, as Yilmas said its simply user error. I believe I can elaborate on the bug Yilmas has experienced. I've run into the same problem and it took hours of troubleshooting to find the cause as AGExt seemed like the least likely suspect at first. Recently I updated all my mods and found that like Yilmas I was unable to place anything after the first item placed in the VAB. Nothing could be attached radially, nothing inline, the extraplanetary launchpads mod would increase the tonnage of the ship as if the part was added but it would not add the part to the ship. I believe it was the FAR update I downloaded that included an update for ModuleManager.2.0.5.dll. AGExt.dll works fine with ModuleManager.1.5.6, no issues in VAB at all. Upgrading to 2.0.5 seems to break the game, consistently on my end. I hope this info helps lead to a fix in the near future. Because, quite honestly, your mod is everything that action groups should be in KSP. Thank you for your time.