Is there anything printed in the python console? What do you mean with "breaking the standard completion"? Does completion for your added assemblies work but not for the standard library types such as string? Btw, you've got a much higher chance of me seeing issues by filing one on github rather than writing about it here.

Sorry, I didn't want to open a duplicate of an issue that already appears to have been resolved. I'm assuming it's something I'm configuring incorrectly, but I can certainly open something on github if you'd prefer. For the time being, though...

Without any custom assemblies, autocomplete works as expected. When I add my assemblies, autocomplete works for them, but stops working for the standard libraries.

derthnada, try upgrading to version 1.0.8 which should behave much better.

The root cause was that UnityEditor.dll had dependencies that weren't loaded and thus throwing an exception when trying to call GetTypes on that assembly. This exception has now been wrapped in a try-catch block. I also made ResolveAssembly a little smarter in that it tries to look for assemblies in the same path of other assemblies loaded.

If you want to get completion of UnityEditor, you just need to add in the full path of UnityScript.dll (which is in a different path compared to the other already loaded dlls) to the ones you already have in there and it seemed in my testing to be able to resolve everything else needed by itself.