Can't import script (indicators)

[alexnj]

I get an error when trying to import an indicator script.
When I open the script editor I find 2 files missing
What can I do? It was a fresh installation with no custom script imported before so as to cause errors. I installed on drive d since I have my documents in there too, otherwise I get other problems when on drive c and my documents on drive d

[NinjaTrader_Bertrand]

alexnj, please see this link here for how to add back those needed references - http://www.ninjatrader.com/support/h...indicators.htm

After you've added them back in the NinjaScript editor, please press F5 to recompile your custom assembly.

[ZTR]

Had a conflict last night and it made me think: Why do @Indys give a message then there is a potential conflict but I can not remember seeing one for custom ones. Am I wrong?

I had a lot of problems with a new version of the GomLadder that had been recently modified. It kept telling me that that name was already in use. Eventhough I had manually taken it out of the NT users file structure.

I ended up removing all Gom stuff, opening a workspace with nothing in it and then pasting into newly created indys all the new and old conflicting indys as the import utility was still not working.

[NinjaTrader_Bertrand]

ZTrade101, you would need to copy in components of the zip (all cs) manually in this case in the respective folders and then compile to see which method / file is giving you the issues. Take for example the T3 that is now a system indicator in NT7, but was not in 6.5, so if you'd tried importing a custom one named T3 (sharing same namespace as NT7 system one), then you would run into this conflict unfortunately.

[ZTR]

ZTrade101, you would need to copy in components of the zip (all cs) manually in this case in the respective folders and then compile to see which method / file is giving you the issues. Take for example the T3 that is now a system indicator in NT7, but was not in 6.5, so if you'd tried importing a custom one named T3 (sharing same namespace as NT7 system one), then you would run into this conflict unfortunately.

But why do @Indys warn you and non@Indys do not?

That is the real question. Why can't I create something as @XYZ? (with a unique, non-NT built in name), I know it will not let me with New NinjaScript. Wonder if I could name it that & just copy it to the indicator folder.

[NinjaTrader_Bertrand]

ZTrade101, the @ones are system indicators and those would be read only in NinjaScript.