No, I get it, since he’s using two position vectors for the timeline, no matter where he places it, it moves its location to those vectors. Note that an actor (evidently) can’t have a relative location, only a child component (since it’s relative to parent; an actor or root component’s relative location is relative to the world)
Try this: in the Construction Script, use a “get location” node and some vector addition to Set the “Up” and “Down” variables to the object’s start location plus or minus some Z value.
Since the Construction Script is only run when the object is built/updated/moved, rather than during its play, this will define the positions the platform moves to relative to its start location. Use a second pair of exposed variables to control the nature of that movement (e.g. you would add the Get Location output to Get UserStartPoint and UserEndPoint to get the Set StartPoint and EndPoint values actually used by the Construction Script; by exposing UserStartPoint and not StartPoint, you can allow each platform to specify in-editor some amount of X, Y, and Z movement which will be automatically added to the platform’s placement data)