How To Import MultiCharts Indicators

On this page

Key terms for this guide

These glossary pages cover the ideas and platform language most closely tied to this workflow.

Use PowerLanguage Editor as the real import point

For MultiCharts, the practical workflow is usually to copy the source example into PowerLanguage Editor, save it as a new indicator, and compile it there. This site is giving you transparent source examples more often than packaged files.

• Think copy, compile, and verify instead of one-click import.
• PowerLanguage is close to EasyLanguage, but not identical.
• Always assume a short platform-specific review is still needed.

Start with simpler studies first

Session levels, moving averages, breakout channels, and bar markers are usually better first imports than anything with complex alerts or multi-data logic. That keeps the first compile more educational and less frustrating.

• Simple studies help you confirm the platform path is working.
• Once a straightforward study compiles, harder ports become much less intimidating.
• This site's cleaner source examples are the best place to begin.

Compile, then test on one chart at a time

After the script compiles, apply it to a single chart and check that the plotted result makes sense for the market and timeframe you chose. If a result looks off, fix one variable before changing anything else.

• Session settings can change what levels and ranges look like.
• Chart interval can change how dense a breakout or tempo study feels.
• One chart beats a noisy workspace during early testing.

Document your platform-specific edits

If you make a small PowerLanguage-specific change, write it down. This is especially helpful when you are adapting examples that started life as TradeStation-style EasyLanguage.

• A short note now saves reverse-engineering later.
• Small naming or syntax changes matter when you revisit the file.
• The goal is repeatable workflow, not one lucky compile.

Frequently asked questions