Trouble with If statements with AE expressions

The trick is to set up your tests in the correct order, use a chain of else if statements (instead of just if) and have a default else at the end in case all your tests fail. So for your example it would be:

if(time > 8){
  [newCoordinates,708.5];
}else if (time > 5){
  [currentCoordinates,708.5];
}else{
  value;
}

That way the expression will solve, no matter what the input conditions are, and as it progresses through the chain, as soon as it encounters a matching condition it won't even process the rest of the chain. So in this case, if time > 8, that's as far as it gets and it will skip the rest of the chain. Hope that makes sense.

You need an "and" argument to define the middle section. It's also a good practice to set up some variables. Something like this would give you three moves:

t = time - inPoint;
s = value[0];
m1 = 5; //time in second from in point
m2 = 8; // time in seconds from in point
p1 = 200; // number of pixels to jump
p2 = 300; // number of pixels to jump
if (t < m1){
	x = s;
}
if (t >= m1 && t <= m2){
	x = s + p1;
}
if (t > m2){
	x = s + p1 + p2;
}
[x, value[1]]

 There are other ways to do this, including setting up times and easing interpolation moves that are added to each other or using layer markers or even audio levels. I almost always define time as time - inPoint so I can drag a layer around in the timeline to change the timing instead of rewriting the expression.

Mylenium's expression only changes position after 8 seconds. It puts the layer in the upper left corner between 0 and 5 seconds and bounces back and forth to the upper left corner because it's missing an = sign, but it gives you another approach.

You'll need a different approach if you want a move that increases the position each time a new score is reached. The timing is included in your CSV file. For that, you'll need an accumulator function instead of a series of if/else statements.

You may want to look into JavaScript basics. This isn't even AE specific. You need to define the conditions mathematically exact or use nested conditional statements so the engine actually looks at the second statement in the inner branch. It's also good practice to always have a fallback if none of the conditions are met.

if(time > 5 && time < 8){
[currentCoordinates,708.5]
}
else if(time > 8){
[newCoordinates,708.5]
}
else{
[0,0]
}

Mylenium