AgenaTrader Docs
HomeIndicatorsAgenaScriptRelease Notes
English
English
  • 🤝AgenaTrader Online Help
  • Introduction
    • Overview
      • Supported Instruments and Order Processing
      • License Versions
      • Hardware and system requirements
      • Licensing, Programming, Costs, and Support Overview
    • Video Guide
      • AgenaTrader Docs
    • Glossary
    • FAQ
      • Top FAQ
        • Chart is ticking without displaying candles
        • How to display P&L on Tradebar
        • Connecting to more than one CFD-Broker simultaneously
        • Hard and Soft stops: Automatic stop movement
        • Which order connections does my broker support
        • Сonditions and Scripts disappeared
        • Trading Functions Are Disabled
        • IB Charts Not Displayed Correctly or Contain Incorrect Data
        • Can I Connect an Additional Data Feed While Using IB as a Broker?
    • Contact Support
  • Main
    • Broker and Datafeeds Connections
      • AgenaBroker
      • Technology Provider
      • Connections
      • Simulated account
      • Datafeed
      • Broker
    • Set Up Your Workspace
    • Chart Area
      • Charting
      • Chart Types
      • Chart Tools
      • Chart Context Menu
    • Chart Trading
    • Order Management
    • OptionTrading
    • Realtime Scanner
    • OrderStream
    • ActionBar
    • Main Menu
  • TOOLS
    • Preferences
    • Mappings and Instrument-Lists
    • Instrument Editor
    • Tools Menu
    • Trading Information
    • System Information
  • Create your own strategy
    • Semi automated trading
    • AgenaTrader++ (plusplus) – Automated Setup & Recovery Management
    • AT (plusplus) Manager
    • Setup Builder
    • Signal Builder
    • Risk and Money management
    • Strategy Manager
    • AgenaScript
    • Scripting
  • Package
    • Package first steps
    • AddOns (packages) and their content
    • Internal Packages
    • External Packages
    • Using AddOn- and package-indicators in scripted components
Powered by GitBook
On this page
  1. Package

Using AddOn- and package-indicators in scripted components

Last updated 2 months ago

When you for example have purchased an AddOn like COT-, Volume-, Rimes,…. you might want to script your individual extensions for that.

Due to technical reasons it is not possible to address those indicators directly e.g. in Scripted Indicators, Strategies or Conditions via Intellisense, as it is possible with the directly integrated system indicators.

But you can use the SignalBuilder to set the correct signature of the respective AddOn indicators in your scripted components.

Therefore please do the following:

1) Create a pseudo-condition in SignalBuilder with exact those settings as you want to use the respective component in your scripting code and save this condition:

2) Switch to your usercode file in the Scanns-folder and open the condition with the notepad-editor:

3) Select and copy the indicator signature from the condition:

4) Now add it to the scripting environment where you want to script your own component: