Posts made by l'andorrà

Is your question related to this thread? If not, please create a new thread.

De acuerdo. Pero ¿significa eso que no se puede abrir más de una compra por vela? Es decir, si se da la condición de compra y la de venta a la vez en la misma vela, abrirá primero una y luego la otra, perno no más hasta la siguiente vela. ¿Es correcto?

@bagheria Great!

Essentially you need the 3 block trees I share in my example. The first one can be used exactly as I share. Same with the third one. What needs to be adjusted to your case is the second in the middle. In my example I show a oversimplified version. You need to create your own structure with the block on top surrounded by the red line as per my example. Then using that block number on both 'turn on' and 'turn off' blocks.

Then I'm afraid I cannot be any helpful. Definitely it should work. Did you try using the bot on other brokers? Maybe the issue is on that specific MT plaform.

Then you can do this:

https://fxdreema.com/shared/pMNUFoBec

@Ren12 In general, as sktsec said, that depends on your current structure, but more than probably they will be lost for the bot unless you use this block:

But using it can changes the bot's performance.

You should use a pink 'close' block instead of the blue one. Otherwise all trades all be closed, including those that are not 24 hours old yet.

Sadly, crypto payments can need up to 1 week to be confirmed. I'm afraid the only solution is letting the admin now repeatedly. And yes, that means very poor support service in that area.

Just curious. Why do you need any visual confirmation if the bot is supposed to work 100% automatic? Using variables to store that info is the way to do that instead of using objects.

Yeah. That' sounds cool. I support it.

@alisher2386 There are no specific options to do that. You need to use 'buy/sell pending orders' blocks considering where is current price right now. Then the blocks will program stop/limits orders accordingly.

You can use a structure like this:

https://fxdreema.com/shared/LHZfs3gvb

I don't see why it's doing the first issue. The second one is due to the combination of options selected for questions A and B on top of the drawing blocks. IIRC you should select Yes and No or Yes and Yes, instead of No and Yes like now.

Time and price coordinates are wrong. They are not coincidental. You need to find the positions (ie price levels) first into variables and then use them into the fibo block.

@MT4stefano said in Put a price in a variable:

shared/i6f0ezxVd

Blocks 2 and 3 are doing those calculations every single tick. That is messing up the values of those variables later. I guess you need those to be calculated just once, but not sure when exactly. When are they supposed to be calculated?

I see. But I guess you need that to happen on candle ID 1, right? Ortherwise, on candle ID 0 you would get many different highs and lows. Can you please confirm.

Técnicamente no necesitas una constante. Puedes hacer la comparación de este modo:

https://fxdreema.com/shared/MBGPM9She

@QuantalphaAlgorithms You're welcome, man!

The file is available for MT5.