DAS Trader Pro hotkey scripts turn a multi-click order ticket into a single keypress. The scripting language is documented directly by DAS and used daily by prop firms and retail scalpers. Here's the real syntax, working examples pulled from actual trader setups, and the mistakes that break scripts in 2026.
How DAS Hotkey Scripts Work
Go to Setup, select Hotkey, then click "Add New Item" to open the Hotkey Script Builder. Every script is a chain of commands separated by semicolons, executed top to bottom when you press the key. DAS's own documentation gives the base pattern for a buy limit order:
ROUTE=LIMIT;Price=Ask-0.5;Share=100;ACCOUNT=ACCTNUMBER;TIF=DAY+;BUY=Send
That single line sets the route to a limit order, prices it half a dollar below the ask, sizes it at 100 shares, and sends it as a day-plus order. Some commands are case-sensitive, so copy scripts exactly before editing values.
Order Trigger Orders (OTOs): Attaching a Stop to Your Entry
The most useful hotkey pattern is the Order Trigger Order, which fires a stop automatically once your entry fills. DAS's documented example: a limit order to buy 100 shares at the ask plus a 0.10 offset, which triggers a stop market order 20 cents below entry once filled. The trigger price sets when the stop activates; the limit price sets what it fills at, and those are two different numbers you need to set deliberately, not interchangeably.
DAS also supports trigger variants for stop limit, stop range, stop trailing, and a straight limit or market order on trigger, so you can build in a profit target and a stop loss from the same entry hotkey.
Real Working Script: Dynamic Risk-Based Position Sizing
The pattern traders actually use in 2026 calculates share size from a fixed dollar risk rather than a fixed share count. Here's a documented version for a long entry with a $20 risk, using the montage object model:
$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+;
This cancels open orders, reads your stop price from where you clicked on the chart, calculates the exact share count that puts $20 at risk between entry and stop, buys at a 0.5% premium to the ask to guarantee a fill, and attaches the stop automatically. Swap $risk=20 for a percentage of account equity if you want position sizing tied to buying power instead of a flat dollar figure.
Real Working DAS Trader Script: Scaling Out and Moving Stop to Breakeven
A frequently shared hotkey sells half a long position and moves the remaining stop to breakeven in one keypress:
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 mirror flips Bid to Ask and Sell to Buy:
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
If you want to scale out without moving the stop to breakeven, just reuse StopPrice=StopPrice instead of StopPrice=AvgCost in the second half, keeping your original stop level while resizing it to match the smaller position.
Common Mistakes That Break Hotkey Scripts
Wrong sign on Price offsets. Long entries use a minus offset from the ask; short entries use a plus offset. Traders regularly flip this and get filled at the wrong price or rejected orders.
Route confusion between LIMIT and SMRTL. Traders using Interactive Brokers through DAS report inconsistent documentation on when to use "LIMIT" versus the smart-routed "SMRTL" option. If your broker's routing table treats them differently, test both in the simulator before assuming they behave the same.
Missing the TriggerOrder stop entirely. A documented trader complaint from a 14-day trial account: the entry filled but no stop attached, because the TriggerOrder line was missing or malformed. If your stop isn't showing after a fill, check that the TriggerOrder command is on the same script and correctly closes with a semicolon.
Testing live instead of in the simulator. DAS's own documentation states plainly that it is the trader's responsibility to test scripts before using them with real capital. Every trader-shared script above carries the same warning: run it in DAS's simulator first, because a single wrong sign or missing parameter sends a real order at a real price.
Tools and Resources
DAS Trader's own hotkey documentation, accessed through Setup > Hotkey > Help inside the platform, lists every available command and is the authoritative reference when a script doesn't behave as expected
The DAS Trader Pro simulator account, used to test every script above before it touches a live account
Community-maintained hotkey libraries from trading communities like Bear Bull Traders, which host tested scripts for breakeven stops, dynamic risk sizing, and partial exits
FAQ
What is a DAS Trader hotkey script?
A hotkey script is a chain of DAS Trader Pro commands, separated by semicolons, that executes a full order sequence (route, price, size, stop) from a single keypress instead of manual clicks through the order ticket.
How do I create a hotkey in DAS Trader Pro?
Go to Setup, select Hotkey, click "Add New Item" to open the Hotkey Script Builder, and enter your script. Some commands are case-sensitive, so match documented syntax exactly.
Can DAS Trader hotkeys automatically set a stop loss?
Yes, through Order Trigger Orders (OTOs). The entry order carries a TriggerOrder command that fires a stop market, stop limit, or trailing stop automatically once the primary order fills.
What's the difference between ROUTE=LIMIT and ROUTE=SMRTL in DAS?
LIMIT sends a standard limit order at your specified route; SMRTL is a smart-routed limit order. Behavior can differ by broker, particularly for traders running DAS through Interactive Brokers, so test both in the simulator rather than assuming parity.
How do I size a position by dollar risk instead of share count in DAS?
Use a script that reads your clicked stop price off the chart, subtracts it from your entry price to get risk-per-share, then divides your fixed dollar risk by that number to calculate share size dynamically, as shown in the risk-based sizing script above.
Why isn't my DAS hotkey stop loss triggering?
The most common cause is a missing or malformed TriggerOrder line in the script, or a mismatch between the trigger price and the stop price parameters. Rebuild the script from a documented working example and test it in the simulator.
Are DAS Trader hotkey scripts the same across all brokers?
The core scripting language is DAS's own, but order routing options and available routes can vary by broker. A script that works through one broker's DAS integration may need route adjustments through another.
Should I test hotkey scripts before using them live?
Yes, always. DAS's own documentation states it is the trader's responsibility for all orders sent, and every experienced trader sharing scripts publicly repeats the same warning: test in the simulator first.
One Last Thing
The scripts that actually get used daily aren't the flashiest ones. The two patterns that show up across nearly every trader's hotkey setup are dynamic risk-based entry sizing and scale-out-with-stop-to-breakeven, because those two actions are the ones repeated on every single trade, while more complex range and trailing-stop scripts get built once and rarely touched again.