Hi, Gabriel here. This weekend we pushed PineHook 0.0.12, following the 0.0.11 release that brought cTrader and new trade management tools into the beta. If you use MT5, you can now control signal syntax from the dashboard, while the website gives you clearer analytics and trade history for each broker account. You can also attach screenshots to support messages, and we improved how cTrader recovers after a dropped connection or restart. Here is what changed and how to update.

MT5 syntax settings from the dashboard#

When your MT5 EA uses Dashboard as its Settings Source, you can now choose the signal syntax there as well. That includes PineConnector compatibility mode and the five settings that tell PineHook how to read values for sizing, stops, targets, pending orders, and partial closes. You can set defaults across licenses and change them for a particular license, while anyone who prefers to manage settings in MetaTrader can leave the source set to MetaTrader and keep using the EA inputs.

Previously, the dashboard controlled other trading settings, but syntax mode still came from the terminal. You could save a syntax setting on the website and mistakenly think the EA had picked it up. The relay now follows what the connected EA reports it is actually using; settings saved while the EA is offline apply after it reconnects, and an older EA still needs the 0.0.12 update before it can use dashboard syntax controls.

Changing units deserves a little care because an alert such as risk=1 can mean different things under different settings. Pause your alerts while you make the change, check the connected mode, and try a demo trade before resuming. The compatibility guide explains the units and where each one is set.

A quicker way to find the right command#

The commands guide now puts PineHook and PineConnector syntax on the same page, with a finder that understands tasks such as closing part of a position or moving a stop to breakeven. Once you find a command, its parameters and examples sit near the instructions instead of at the far end of a long reference page. The older guide links still work, so bookmarks and links in existing setup notes will take you to the information you expect.

We made a similar change to the guides directory, where you can start with brokers or prop firms and search within that group. There are more setup guides now, including separate MT5 and cTrader steps where a firm supports both platforms. If you are connecting a new account, finding the right guide should take less sorting through unrelated results.

Analytics for the account you selected#

Analytics now shows one license and one recorded broker account at a time. If you have moved a license between accounts, you can choose which account's history to inspect, and the reports use broker identity as well as the login number so two brokers with the same number do not appear to be one account.

The page also stops borrowing a current live balance for a historical account; if that balance is unavailable for the account you selected, it says so. Drawdown has a clearer meaning too: the current figure matches the final chart point and measures observed balance below its running peak. Floating equity can move while a trade is open, so the chart does not claim to show those changes. If you want to check what each number covers, the analytics guide walks through the reports.

Trade history that tells you what happened#

Recent Trades now sorts by close or event time and shows that time down to the second, with the opening time beside it. We renamed the "Manual" badge to "No linked alert" because a trade without a PineHook signal could have been placed manually or by another EA.

MT5's new realized deal reports include broker deal fees along with profit, swap, and commission. The card now reads "Closed-trade P&L," and you can compare it with your broker statement when checking opening charges or partial closes. New deposit and withdrawal imports no longer put today's account balance on an older transaction date; previously stored records are unchanged.

If you use multiple take profit or stop loss levels on MT5, a partial close now keeps the target level that triggered it. Your history can now identify a TP2 close, and the EA keeps the same detail for recovery after an interruption.

Clearer cTrader connections#

Before you connect a cTrader account, Settings and Licenses now show the same explanation of what the trading permission allows and what account information PineHook stores. You can review it before going to cTrader's authorization page, and canceling the review leaves an unfinished license draft in place.

The explanation also distinguishes unlinking a license, removing PineHook's connection record, and revoking the grant through cTrader. Those actions have different effects, so the cTrader setup guide now spells them out alongside the connection steps.

Screenshots and better help when you need it#

You can attach up to three screenshots to a support ticket, feedback message, or Inbox reply, using PNG, JPEG, or WebP images of up to 5 MB each. Screenshots put the setting, alert result, or dashboard view beside your message. Please hide passwords and license keys before attaching an image.

If you reach the assistant's chat quota, you can open a support ticket from the chat. We also fixed cases where the assistant could mistake a healthy account for offline or fail to find an account by name; when a response is interrupted, retry handling is more careful about preserving the answer and your usage allowance. You can still reach a person through the Inbox when the assistant cannot settle the question.

More work on cTrader recovery#

A cTrader relay must check what the broker executed before it resumes an account after a dropped connection or restart. We corrected a history read that could stop after the first page on a busy account, and the relay now paces those requests to respect the broker's limits. If it cannot establish a complete history, it waits instead of continuing on an incomplete picture, while clearer diagnostics tell us what is holding up recovery.

We also fixed an error path for an unknown symbol on a cTrader netting account. Instead of leaving the signal waiting without a result, the relay records and acknowledges the broker symbol failure. These are server changes, so cTrader users have nothing to install.

The smaller things#

Several other changes make day-to-day use a little clearer.

Signal details distinguish an MT5 terminal refusing a trade because AutoTrading is disabled from an alert that expired during relay recovery, and they show more of the stored failure reason when an alert is blocked.
The public status page separates MT5 and cTrader latency figures and labels what each one measures, since the two platforms do not use the same endpoint for that measurement.
Coupon checkout compares eligible offers and applies the largest single discount; if a code is invalid or the chosen discount cannot be applied, checkout no longer continues at a higher price without telling you.
On mobile, a brief connection drop during session refresh could log you out even while your session was still valid. We now retry temporary failures without clearing your login, and switching accounts no longer lets a late response from the previous account appear in the new one.

How to update#

If you trade through MT5, download the 0.0.12 bundle from the downloads page and follow the installation guide to replace the EA and reattach it to your chart. The bundle includes DLL version 0.0.4, which has not changed. After reconnecting, confirm your Settings Source and syntax mode, particularly if you use PineConnector compatibility mode.

The website and cTrader changes require no download, while the new EA gives MT5 the dashboard syntax controls and updated trade reporting. After installing it, send a small test alert on a demo account and check Signal Logs before returning to live alerts.

Keep telling us what to fix#

If something in 0.0.12 does not behave the way you expect, send us a message through the dashboard. Include the alert and what you expected to happen, with a screenshot if that makes the problem clearer, and we will have a much better starting point for reproducing it.

Thanks for testing with us.

Gabriel J., Co-founder

PineHook 0.0.12: More Control and Clearer Reporting