Build your own trading indicator

Indicator languages treat every value as a series indexed by bar. The script runs once for each bar from the oldest to the newest, so close means this bar's close and close one bar back means the previous one. Early bars, before a 20 bar average has enough history, return an empty value that the script has to handle.

A script usually has three parts: a header that names it and says whether it draws on the price pane or in its own pane, inputs that show up as settings, and plots that draw lines, histograms, shapes or labels.

Repainting is the most common trap. An indicator that uses future bars, or that changes past values when a new bar arrives, looks perfect on history and fails live. Check how each signal looked on the bar where it first appeared.

Overfitting is the second. Tuning ten inputs until the past looks good fits noise. Keep inputs few, test on periods you did not tune on, and judge results over many trades.

Look at what the language can do, what the platform lets you share, and whether your indicator can run next to the data you care about. A script that needs options or gamma data has to run where that data lives.

OmegaScript is Obelion's language for custom indicators. It uses the same per bar series model that Pine Script and thinkScript users know, and it imports most Pine indicator scripts automatically, with a report of any lines it could not convert. Scripts run sandboxed with no network or file access, and the same bars and script always give the same output.

OmegaScript is in private development. Authoring is currently open to Omega members, a plan offered by invitation, and to approved trial accounts. The documentation is public.