# Scope-ing nested mc's and the /target paths that love them

**URL:** <https://forum.kirupa.com/t/scope-ing-nested-mcs-and-the-target-paths-that-love-them/232505>\
**Category:** Uncategorized\
**Created:** [July 14, 2007, 6:30pm UTC](https://forum.kirupa.com/t/scope-ing-nested-mcs-and-the-target-paths-that-love-them/232505 "2007-07-14T18:30:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![strobotron](https://avatars.discourse-cdn.com/v4/letter/s/5f8ce5/32.png) [@strobotron](https://forum.kirupa.com/u/strobotron)\
**Post date:** [July 14, 2007, 6:30pm UTC](https://forum.kirupa.com/t/scope-ing-nested-mcs-and-the-target-paths-that-love-them/232505/1 "2007-07-14T18:30:33Z")

</div>

MY QUESTION: is there a way to scope instances that haven’t been instanced in the first frame of the movie?

I got brave and nested my btn\_mc clips inside a nav\_mc.

On an action layer in the first frame of my timeline I have:

\_root.nav\_mc.btn1\_mc.gotoAndPlay(“start”);

for example.

In the nav\_mc timeline this works if and ONLY if the btn1\_mc instance is on the first frame of the nav\_mc timeline.

I’m trying to update my skillz and put everything in the first frame of the root timeline rather than doing the backasswards syntax on the mc itself this (onPress) which really confused me for about five years.

Is that ever acceptable (i mean not in a best practices sense but in a 85% solution sense). I’m so down with hacks and kludges if I can get away with it.

/Eval !!!