# Overlay shift coding

Solved…Script Deleted

So, from what I see, every paper ball has a first shift and a second shift.

I figure you could:

• Use all the anchor point commands first
• Then string all of the first shift together
• Then all the second shift

&overlay PAPERBALL rotates 360 anchor point 0.5 0.5 in 0.5 AND overlay PAPERBALL scales to 0.163 0.163
&overlay PAPERBALL_2 rotates 360 anchor point 0.5 0.5 in 0.5 AND overlay PAPERBALL_2 scales to 0.163 0.163 AND overlay PAPERBALL_2 opacity 1 in 0
&overlay PAPERBALL_3 rotates 360 anchor point 0.5 0.5 in 0.5 AND overlay PAPERBALL_3 scales to 0.163 0.163 AND overlay PAPERBALL_3 opacity 1 in 0
&overlay PAPERBALL_4 rotates 360 anchor point 0.5 0.5 in 0.5 AND overlay PAPERBALL_4 scales to 0.163 0.163 AND overlay PAPERBALL_4 opacity 1 in 0
&overlay PAPERBALL_5 rotates 360 anchor point 0.5 0.5 in 0.5 AND overlay PAPERBALL_5 scales to 0.163 0.163 AND overlay PAPERBALL_5 opacity 1 in 0

@overlay 5561598568628224_PAPERBALL shifts to 82 284 in 0.2 AND overlay PAPERBALL_2 shifts to 65 338 in 0.2 AND overlay PAPERBALL_3 shifts to 84 263 in 0.2 (and all the rest)

@overlay 5561598568628224_PAPERBALL shifts to 141 164 in 0.2 AND overlay PAPERBALL_2 shifts to 213 169 in 0.2 AND overlay PAPERBALL_3 shifts to 84 263 in 0.2 (and all the rest)

^ You can tweak and change that to look exactly the way you want, but the point is that, with timed shifts like that, you’ll need to group them according to timing rather than name.

I can’t do it like that if all of them go under an “&” command. What did you change actually?

I basically just changed the order, and grouped some together in a line.

For example, these two:
@overlay 5561598568628224_PAPERBALL shifts to 82 284 in 0.2
@overlay 5561598568628224_PAPERBALL shifts to 141 164 in 0.2

First it’s supposed to more to 82 284, then to 141 164, right? So the reader will see both movements. If both are an &…

&overlay 5561598568628224_PAPERBALL shifts to 82 284 in 0.2
&overlay 5561598568628224_PAPERBALL shifts to 141 164 in 0.2

…The second one will interrupt the first one.

So that’s a case where an & isn’t what you want, because the first one will be interrupted. That’s why I rearranged the commands to have all the first shifts happen together, and all the second shifts happen together.

(Edit: Made a tiny spacing change to my earlier post so it looks a little cleaner lol)

1 Like

I found a solution, I added “&” on the last shift commands, an “@” before a “&” causes it to delay and with the right timing, but it’s extremely hard to code it all without it looking like one comes after the other, but thank you.

1 Like

Sounds like that’ll still have them appearing one after another, just with a little less delay. But whatever works for ya haha.

1 Like