TickValue

I think you are correct . . .

What TICKVALUE do they have for other XXXUSD pairs ?  they should all be 1.00 

//double PipValuePerLot(string pair=""){ return(DeltaValuePerLot(pair)*pips2dbl);}
double DeltaValuePerLot(string pair=""){
    //{ Value in account currency of a Point of Symbol.
    // In tester I had a sale: open=1.35883 close=1.35736 (0.0147)
    // gain$=97.32/6.62 lots/147 points=$0.10/point or $1.00/pip.
    // IBFX demo/mini       EURUSD TICKVALUE=0.1 MAXLOT=50 LOTSIZE=10,000
    // IBFX demo/standard   EURUSD TICKVALUE=1.0 MAXLOT=50 LOTSIZE=100,000
    //                                  $1.00/point or $10.0/pip.
    //
    // https://forum.mql4.com/33975 CB: MODE_TICKSIZE will usually return the
    // same value as MODE_POINT (or Point for the current symbol), however, an
    // example of where to use MODE_TICKSIZE would be as part of a ratio with
    // MODE_TICKVALUE when performing money management calculations which need
    // to take account of the pair and the account currency. The reason I use
    // this ratio is that although TV and TS may constantly be returned as
    // something like 7.00 and 0.0001 respectively, I've seen this
    // (intermittently) change to 14.00 and 0.0002 respectively (just example
    // tick values to illustrate).
    // https://forum.mql4.com/43064#515262 zzuegg reports for non-currency DE30:
    // MarketInfo(chart.symbol,MODE_TICKSIZE) returns 0.5
    // MarketInfo(chart.symbol,MODE_DIGITS) return 1
    // Point = 0.1
    // Prices to open must be a multiple of ticksize
    //}
    if (pair == "") pair = Symbol();
    return(  MarketInfo(pair, MODE_TICKVALUE)
           / MarketInfo(pair, MODE_TICKSIZE) ); // Not Point.
}

You are right, but what it relationship with the problem mentioned here ?

A value of 0.0001 for TickValue is a non sense, I don't see any type of account or trading parameters that can explain that. For the date provided on post#1, the correct value is 1.0, like RaptorUk said.

I'm surprised such an error may occur, this can effectively be catastrophic for an EA. Yet another solution to find for developping a robust EA.

WHRoeder,

if you check this screenshoot then your method should not work reliable on non-basecurrency pairs. On Left side is the "problematic-broker" and on right side is another broker.  I personally think nothing can replace TickValue.

WHRoeder

I found out that this broker gives WL MT4 to many sub-brokers. And i found out there are many sub-brokers. And i also found that all those sub-brokers have same TickValue. And there are probably thousands of people using this Stream with their EAs. 

Now my theory is that almost all EAs they use MM will use Tickvalue and oversize the position sizing. Moreover on symbols without base currency tickvalue cannot be calculated too simply. Not all EA is prepared for those brokers (they are many).

My question is : do i see this thing too strict? Is the world really that relaxed? What do you guys think is the strategy of those brokers to publish wrong TickValue? Do they want keep distance from "professional"  traders they trade with position sizing and EAs?

thanks, every comment is welcome because we do argue with main broker why they do this. They simply tell me its their policy. 

I think MetaQuotes would have something to say about this, perhaps you should report it via your Profile on the MT5 site (assuming you have one) to the Service Desk.

Too strict ?  nope, it doesn't have to be deliberate though,  there is plenty of scope for this error to be caused by incompetence,  there is plenty of it about. 

is the leverage the same on both brokers?  mostly asking out of curiosity.