Post: #6

You're not really using double eval on the same value, but using eval on 2 different values

Sphere return TAG/CTAG/VAR/LOCAL/ARGS/etc values in hex by default, so if you set SRC.CTAG0.achievement_1_1_palier=20, <SRC.CTAG0.achievement_1_1_palier> will return 014 (which is 20 in hex)

And this will turn <DEF0.achievement_1_1_palier<SRC.CTAG0.achievement_1_1_palier>> into <DEF0.achievement_1_1_palier014> (which will be 0 because this DEF doesn't exist) and not <DEF0.achievement_1_1_palier20> (which is 500). So to make it work you must read the tag using eval to turn <DEF0.achievement_1_1_palier014> into <DEF0.achievement_1_1_palier20>

Probably experimental build return 500 even without the eval because it automatically eval values by default. Its easy to make sphere return values in dec instead hex but maybe its better leave it returning hex to preserve script compatibility because sphere always had returned hex values since decades ago. But anyway deal with dec values is much more readable than hex, so I will take a better look to check if this can be changed without cause any drawbacks