# \[MX AS | Noo-B\] Transitions and Tell Target

**URL:** <https://forum.kirupa.com/t/mx-as-noo-b-transitions-and-tell-target/52896>\
**Category:** Uncategorized\
**Created:** [May 28, 2004, 3:48pm UTC](https://forum.kirupa.com/t/mx-as-noo-b-transitions-and-tell-target/52896 "2004-05-28T15:48:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bluewing](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@Bluewing](https://forum.kirupa.com/u/Bluewing)\
**Post date:** [May 28, 2004, 3:48pm UTC](https://forum.kirupa.com/t/mx-as-noo-b-transitions-and-tell-target/52896/1 "2004-05-28T15:48:36Z")

</div>

Ok, to help reduce the number of flames I’ll likely get, I DID READ THE TUTORIAL on this site…and it works. However, I’m trying to extend the practice a little bit.

I have a series of buttons that will cause transitions of certain movie clips in my main timeline. However, I’m trying to do two transitions, within the SAME movie clip, in a specific order.

[indent][color=darkred]on (release) {

```
  tellTarget ("/side_menu") {
               gotoAndPlay ("Splash Out"); [/color]

```

[color=darkred] gotoAndPlay (“Contact In”);[/color]

[color=darkred] }[/color]  
[color=darkred]}[/color]

[/indent]The result of the following code is that it skips playing “Splash Out” and goes straight to “Contact In”.

I can’t hardcode the final frame of “Splash Out” to play “Contact In” because what occurs after this isn’t always the same. So what’s a Noo-B to do?

–Bluewing