@alphaomega said in Help with MQL block and variables please:
@tipsywisdom Lol... or maybe he got himself in trouble with that magic and the FBI is looking for him... There are others here that is also wizz kids... Like @miro1360 but he seldom writes anything these days
This kid comes here from time to time and watches the creativity of other people 
It is not possible with integrated martingale systems in Buy block. You can do it only with a custom martingale system (using a combination of variables, blocks for checking trades count, creating a final variable for the comment in Buy block, ...)
It is called "counter trend trading" - in other words "selling tops, buying bottoms"
@l-andorrà
Don't worry, I am still here and I watch people to learn, to come, to try and give up and leave 
@ferdinand-0
Hi, it depends on your trading style, some people buy when trends started, some sell tops 
Both is good if it is timed correctly, timing is crucial. As you move forward, you will understand it.
Try to find a moving average over CCI indicator.
https://www.mql5.com/en/market/product/54067?source=Unknown
I can work faster with custom code blocks, you can follow the logic and easily turn it into blocks
Note: onTimer section is not working with tester
Use onTimer section and set the interval for 1 second. Add a variable and increment it in this section (varCounter = varCounter + 1), and compare the result with the value 85. If it goes over 85, "allow opening" a new trade depending on another conditions (or open one immediately). By "allow opening" I mean set another variable for true (like varOpen = true). When a trade is opened, reset all variables (varCounter = 0, varOpen = false, etc.).
Take an inspiration from this thread and my reply:
https://fxdreema.com/forum/topic/11979/ea-operated-after-3min-from-candle-formation-at-5-min/9
@ambrogio yes I did, and you will face the same problem with positive number for buys
... admin won't change it (it has been the subject of discussion in the past) due to worries of breaking existing projects, so you need to find a workaround ...
use the custom code block and default templates folder, be sure your template is saved with loaded EA for simple logic - if template does not contain EA, the loaded template will be without EA
(you can use the code anywhere .. here it is after button clicked on object)
https://fxdreema.com/shared/vvk9mDAtc
the variables are not declared, so declare them in the variables windows and that is ... I have no idea about this project and the author should know where they belongs
Not that specifically for fxdreema, but in general:
avoid repainted indicators (fisher is a good example, offline renko charts generated from history prices) .. or use it correctly
try to make the indicator effective so that it does not recalculate the whole history, but recalculates only the necessary number of prices
avoid a possibility of division by zero
