How to pass data between scenes – Static variables

If your game passes the early prototype phase where you just use one scene and build the basic game mechanics, you might come to the point where you start building some test levels to check out some ideas and want to share them with friends, clients (or the world, I dunno).

Let’s say you keep your level selection screen and your game in different scenes (which I prefer to do), how do you pass the selected level id to the game scene where the appropriate data would then be loaded to build the level?

LevelSelection to game



There are different ways to share data between scenes.

You could use a GameObject with a MonoBehaviour script which keeps all attributes you want. You could then call DontDestroyOnLoad on your GameObject to prevent it from getting trashed once the scene is removed.

It could look something like this:

Static attributes

But I think this is rather clunky and there is a much more elegant way to do this by using static class attributes. Static variables aren’t destroyed on scene changes and stay as long as the application is running. I prefer to use a single class called ApplicationModel which keeps things like current level or player data etc. An inheritance of MonoBehaviour isn’t necessary. All the data I’d like to keep available between scenes is placed in there as a static and public attribute.


The currentLevel attribute is updated after the necessary button at the level selection has been clicked. Subsequently the game scene get’s loaded by calling Application.LoadLevel(“MyGame”). After the scene has been loaded the currentLevel value is still available and the appropriate leveldata could be loaded right away.

Levelbutton script example


Game script example


Example & Source

A browser demo can be found here

The Unity3D project can be downloaded here 04-arrow-northeast

28 thoughts on “How to pass data between scenes – Static variables

    1. Yep, that’s correct. I wasn’t sure about the future of flash and wanted to try some more tools for game development like Corona & Unity3D. Thanks for leaving a comment.

  1. I do consider all of the concepts you’ve offered to your post.

    They’re really convincing and can certainly work. Nonetheless,
    the posts are very short for novices. May just you please lengthen them a bit from subsequent time?
    Thanks for the post.

  2. I’m not that much of a internet reader to be honest but your sites really nice, keep it up!
    I’ll go ahead and bookmark your website to come back later.

    All the best

  3. When I was searching for way to pass a parameter, I didn’t like the DontDestroyOnLoad method. Thanks for great tip!

    1. Not sure what you mean. You can create a player class with field named score and add points at all necessary positions in your code.
      You create an instance of player when you start the game (coming from the menu or levelselection etc.).

      public class Player
      public int score = 0;

      public void AddScore(int amount)
      this.score += amount;

  4. Just what I was looking for. I knew there had to be some way to do something like this. Thanks for taking the time to blog this. It is a simple and eloquent solution.

  5. Hi Christian,

    This ApplicationModel needs to be added as a component to a GameObject in every scene?

    In that case, what is the advantage over the DontDestroyOnLoad(gameObject) method?


    1. Hey Gerard,

      static fields are class variables and accessible from everywhere in your code (if made public). You can find more information about this topic here

      You access them like this:

      ApplicationModel.myStaticField = “Hello world!”


      Hope that helps. Thanks for leaving a comment.

      1. Great,

        I didn’t know that I could change the values of a static variable, I believed it only serve as a fixed value.

        Thanks for the help! 🙂

  6. Cool. I hit that point where I needed to start thinking about multiple levels and throwing data around. This helped a lot (and I need a starting start screen as well!) Thanks for the straight forward post. 🙂

  7. Thank you Christian,

    is it your code still current after 3 years? I’ve recently bought a course on Udemy and they use DontDestroyOnLoad method.

    1. Hey Diego, yes this code is still up to date. And it will in be in the future since the solution I explained is Unity independent. You can work with static fields in almost every language. The DontDestroyOnLoad method is more a “beginner” way of doing things since you might not be that experienced with programming in general and static fields can be confusing at first. Also it’s more of a Unity-focused approach which I don’t like.

      Hope that helps. Sorry for the late answer. 🙂

  8. Hello, I’m a little bit confused. You just add that class in your scripts folder, not attaching it to any gameobject and it will stay accesible in all your aplication life cycle by any other class?

    1. Yes, if you started programming with Unity you might be confused. C# is more then a fancy scrip-language for Unity. There is a lot more you can do. Maybe you can look here for further information: (yes, this is for java. But it’s the same in C#). The second one is a general introduction to the keyword static. You can use it not only to create static fields but also for static functions. This is useful for the Singleton- or Factory-Pattern for example (,

  9. Thank you very much for the example – I kind’a got the meaning; but needed the download to have it make sense.

  10. Why couldn’t i find such a simple and powerful solution in all the tutorials i read/watch about Unity in so many years?

    Thanks a lot, this will solve me hours of hard work. 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.