DAS Trader Pro hotkey scripts are semicolon-separated command chains that turn a multi-click order ticket into one keypress. In 2026, prop firms and retail scalpers use DAS scripts for entries, stops, scale-outs, and position sizing. The examples below use 100 shares, a $20 risk amount, and a 0.5% price adjustment. DAS documents the language directly, and some commands are case-sensitive, so copy a working script before changing it.
How DAS Hotkey Scripts Work
Open Setup, select Hotkey, then click "Add New Item" to open the Hotkey Script Builder. Each script is a chain of commands separated by semicolons. DAS runs the commands from left to right when you press the assigned key.
DAS gives this base pattern for a buy limit order:
ROUTE=LIMIT;Price=Ask-0.5;Share=100;ACCOUNT=ACCTNUMBER;TIF=DAY+;BUY=Send
ROUTE=LIMIT selects a limit order. Price=Ask-0.5 sets the price 50 cents below the ask, Share=100 sets the position size, and TIF=DAY+ sets the time-in-force value. The final command sends the buy order. Match the documented capitalization when you edit a script.
Order Trigger Orders (OTOs): Attaching a Stop to Your Entry
An Order Trigger Order (OTO) can send a stop automatically after an entry fills. DAS's documented example uses a limit order to buy 100 shares at the ask plus a $0.10 offset. Once the entry fills, it triggers a stop market order 20 cents below the entry.
The trigger price controls when the stop activates. The stop or limit price controls the price used by the order after activation. Those are separate values and should be set independently.
DAS also supports trigger types for stop limit, stop range, stop trailing, limit, and market orders. That lets you attach a profit target, a stop loss, or both to the entry script.
Dynamic Risk-Based Position Sizing
A risk-based script calculates share size from a fixed dollar risk instead of a fixed share count. The documented example below uses the montage object model for a long entry with $20 at risk:
$MONTAGE=GetWindowObj("MONTAGE1");
$MONTAGE.CXL ALLSYMB;
$buyprice=$MONTAGE.Ask;
$risk=20;
$mystop=$MONTAGE.price;
$pricetostop=$buyprice-$mystop;
$amount=$risk/$pricetostop;
$MONTAGE.share=$amount;
$MONTAGE.ROUTE="LIMIT";
$MONTAGE.Price=Round($buyprice*1.005,2);
$MONTAGE.TIF="DAY+";
$MONTAGE.Buy;
$MONTAGE.TriggerOrder=RT:STOP STOPTYPE:MARKET PX:$mystop ACT:SELL STOPPRICE:$mystop QTY:Pos TIF:DAY+;
The script cancels open orders, reads the stop price from the montage, calculates share size from the distance between the ask and the stop, and submits the entry. It sets the limit price at 0.5% above the ask, then attaches a stop market order after the entry fills.
To tie the position size to account equity instead of a fixed dollar amount, replace $risk=20 with the percentage-based calculation used in your setup.
Scaling Out and Moving the Stop to Breakeven
This long-side hotkey sells half the position, then places a stop for the remaining shares at average cost:
CXL ALLSYMB;Route=LIMIT;Share=Pos*0.5;Price=Bid-0.05;TIF=DAY+;SELL=Send;
ROUTE=STOP;StopType=Market;StopPrice=AvgCost;Share=Pos-share;TIF=GTC;SELL=SEND
The short-side version reverses the order direction and changes the price offset:
CXL ALLSYMB;Route=LIMIT;Share=Pos*0.5;Price=Ask+0.05;TIF=DAY+;BUY=Send;
ROUTE=STOP;StopType=Market;StopPrice=AvgCost;Share=Pos+share;TIF=GTC;BUY=SEND
To scale out without moving the stop to breakeven, use StopPrice=StopPrice in the second half of the script. That keeps the original stop level while adjusting the stop size to match the smaller position.
Common Mistakes That Break Hotkey Scripts
Long entries use a minus offset from the ask. Short entries use a plus offset. Reversing the sign can produce the wrong price or cause the order to be rejected.
LIMITandSMRTLmay behave differently depending on the broker connection. DAS users running Interactive Brokers through DAS have reported inconsistent guidance on when to use each route. Test both in the simulator before using either one live.A missing or malformed
TriggerOrdercommand can leave an entry without its stop. One complaint from a 14-day trial account described an entry that filled without a stop because the trigger line was missing or incorrect. If the stop does not appear after a fill, check the command and its semicolon.Test scripts in the simulator before sending live orders. DAS states that the trader is responsible for testing scripts and for the orders they send. A wrong sign or missing parameter can send an order at an unintended price.
Tools and Resources
DAS Trader's hotkey documentation is available through Setup > Hotkey > Help inside the platform. Use it as the reference when a command does not behave as expected.
The DAS Trader Pro simulator lets you test scripts before they reach a live account.
Community-maintained hotkey libraries from trading groups such as Bear Bull Traders include scripts for breakeven stops, risk-based sizing, and partial exits.
FAQ
What is a DAS Trader hotkey script?
A DAS Trader hotkey script is a chain of commands separated by semicolons that sends an order sequence from one keypress. The sequence can include the route, price, share size, and stop.
How do I create a hotkey in DAS Trader Pro?
Open Setup, select Hotkey, click "Add New Item," and enter the script in the Hotkey Script Builder. Match the documented syntax because some commands are case-sensitive.
Can DAS Trader hotkeys automatically set a stop loss?
Yes. An Order Trigger Order uses a TriggerOrder command to send a stop market, stop limit, or trailing stop after the primary order fills.
What's the difference between ROUTE=LIMIT and ROUTE=SMRTL in DAS?LIMIT sends a standard limit order using the selected route, while SMRTL uses smart routing for the limit order. The behavior can vary by broker, especially with Interactive Brokers connections, so test both in the simulator.
How do I size a position by dollar risk instead of share count in DAS?
Read the stop price from the chart or montage, subtract it from the entry price to calculate risk per share, and divide the fixed dollar risk by that amount. The dynamic risk-sizing script above follows this pattern.
Why isn't my DAS hotkey stop loss triggering?
The most common causes are a missing or malformed TriggerOrder command and a mismatch between the trigger price and the stop price. Rebuild the script from a documented example and test it in the simulator.
Are DAS Trader hotkey scripts the same across all brokers?
The core language belongs to DAS, but available routes and routing behavior can vary by broker. A script that works through one DAS connection may need route changes through another.
Should I test hotkey scripts before using them live?
Yes. Test every script in the simulator first. DAS states that traders are responsible for the orders their scripts send, and a single incorrect parameter can create a live order at the wrong price.
The Patterns Traders Reuse Most
Two patterns recur in trader hotkey setups: risk-based entry sizing and scaling out while moving the stop to breakeven. Both handle actions repeated on individual trades. Range and trailing-stop scripts can be useful, but traders tend to build them once and use them less often.