Updated July 4, 2026.
PowerLanguage code repair is often about behavior, not just syntax. A MultiCharts indicator or strategy can compile but still behave differently than expected because of data series, strategy properties, calculation timing, or platform differences from TradeStation.
Moore Tech handles MultiCharts programming for PowerLanguage indicators, strategies, repairs, conversions, and workflow tools.
Use this guide when you have a PowerLanguage compile error, confusing assignment behavior, a Mod-function question, a broken custom indicator, a strategy signal problem, or TradeStation code that does not behave correctly after moving into MultiCharts.
What counts as PowerLanguage repair
Repair usually means the code exists, but it does not compile, does not display correctly, or does not match the intended MultiCharts behavior.
Common repair requests include:
- compile errors in PowerLanguage
- assignment or operator errors around the current source code
- function issues such as Mod usage that need to be reviewed in context
- indicator plots or alerts that do not match the rules
- strategy entries or exits that differ from expectations
- multi-data behavior that is hard to verify
- PowerLanguage .NET or SignalObject-style projects with missing context or dependencies
- TradeStation EasyLanguage logic that needs MultiCharts cleanup
- older code that needs modernization before extension
For these projects, send the code and the platform context. A screenshot of the problem is useful, but the source file is usually required.
Start by naming the failure type
Before requesting help, separate the problem into one of these buckets:
- Syntax or compile error: the editor will not accept the code.
- Indicator behavior mismatch: the study plots, colors, labels, or alerts are wrong.
- Strategy behavior mismatch: entries, exits, position sizing, or order timing are wrong.
- Conversion issue: the original TradeStation or EasyLanguage behavior does not match MultiCharts.
- Data or chart-context issue: the script depends on data series, sessions, symbols, broker settings, or chart type.
- Scope change: the old script works, but you now need new behavior.
That first classification helps decide whether the request belongs in a small diagnostic, paid support, or a larger MultiCharts programmer quote.
Syntax questions need surrounding code
Searches for PowerLanguage assignment operators, :=, =, Mod behavior, or function syntax usually point to the same support problem: the error cannot be judged from one isolated line.
Send the surrounding block of code, the exact compiler message, and what the line is supposed to do. If the issue appears inside a function, signal, or multi-data script, include the full file and any dependency files.
Do not rewrite the script from memory before sending it. The current broken version is useful because it shows the real names, inputs, assumptions, and line numbers Moore Tech needs to review.
Custom indicator repair
Custom indicator repair usually starts with the chart output. Include screenshots that show both the incorrect output and the output you expected.
Useful indicator details include:
- the PowerLanguage file
- symbol, timeframe, bar type, and session template
- input values and default settings
- plot names, colors, labels, and alert behavior
- screenshots of correct and incorrect bars
- whether the indicator depends on another study, DLL, data series, or workspace setting
If the indicator was converted from TradeStation, also include the original EasyLanguage file and a screenshot of the TradeStation output.
Strategy and signal repair
Strategy repair needs more than a compile fix. A strategy can compile and still take the wrong trade, skip an expected entry, exit too early, or behave differently in historical testing and live use.
Send the rules and platform settings that affect the signal:
- entry, exit, filter, and stop/target rules
- strategy properties and order assumptions
- account, symbol, timeframe, and session assumptions
- screenshots of bars where the strategy acted correctly or incorrectly
- whether the problem appears in backtest, real-time, or both
- any broker or data-feed details that may affect order behavior
Moore Tech does not treat a repaired strategy as a performance promise. The repair goal is to match the stated behavior and platform assumptions, not to guarantee trading results.
What to send
Send:
- PowerLanguage source files
- MultiCharts version
- chart symbol, timeframe, and data series
- screenshots of inputs and strategy properties
- examples of correct and incorrect behavior
- TradeStation source files if this started as a conversion
- broker or data-feed details if they affect the result
If the issue is strategy-specific, include the strategy properties and assumptions used during testing.
Conversion problems are common
PowerLanguage is similar to EasyLanguage, but TradeStation-to-MultiCharts conversion still needs review. Data handling, strategy settings, order assumptions, and platform behavior can create differences even when the syntax looks familiar.
If you are converting from TradeStation, review the TradeStation to MultiCharts conversion guide before requesting repair work.
If you are still defining the new MultiCharts version, use the MultiCharts PowerLanguage scope checklist before sending the quote request.
Repair or rebuild
A rebuild may be cleaner when the current code is incomplete, the original assumptions are undocumented, or the conversion introduced too many unknowns.
The old code can still define the desired behavior, but the quote should be scoped around the actual work needed to make the MultiCharts version reliable.
Repair usually fits when the current file is organized, the intended behavior is known, and the issue can be reproduced. Rebuild usually fits when the source is incomplete, the rules have changed, dependencies are missing, or the code cannot safely support the requested behavior.
Common PowerLanguage repair questions
Can Moore Tech fix a PowerLanguage assignment operator error?
Moore Tech can review the source file, exact error text, and surrounding code. Assignment and operator issues are best handled with the full file because the right fix depends on the variable, function, signal, and chart context.
Can Moore Tech help with a PowerLanguage Mod function issue?
Yes, if the request includes the current file, the compiler message or wrong output, and an example of the expected behavior. Function issues are usually quoted as a diagnostic or repair once the surrounding logic is visible.
Can a custom MultiCharts indicator be repaired instead of rebuilt?
Sometimes. Repair is more likely when the original source file is complete and the intended plot, alert, or calculation behavior is clear. Rebuild is more likely when important dependencies, rules, or examples are missing.
Is TradeStation to MultiCharts conversion a syntax-only task?
No. Even when the syntax looks familiar, chart behavior, data series, order assumptions, and strategy settings still need review before the MultiCharts version can be scoped.
Practical next step
Start with MultiCharts programmer services when you have broken PowerLanguage, a confusing strategy result, or a TradeStation conversion that does not behave correctly. Start with paid support when the request is a bounded first-pass diagnostic and you mainly need help deciding whether the issue is setup, syntax repair, conversion, or a deeper rebuild.