class in UnityEngine
/
Implemented in:UnityEngine.CoreModule
Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.
CloseFor some reason your suggested change could not be submitted. Please <a>try again</a> in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.
CloseCauses a MonoBehaviour-derived class to execute in Edit mode in addition to at runtime.
By default, MonoBehaviour event functions only execute at runtime. Applying ExecuteInEditMode
to a MonoBehaviour-derived class causes the event functions for any instance of that class to also execute in Edit mode.
This attribute targets classes, but it only has an effect on classes that inherit from MonoBehaviour.
This attribute is not recommended because it is not compatible with editing in prefab editing mode. The recommended alternative is ExecuteAlways.
If you're editing a prefab containing a MonoBehaviour with the ExecuteInEditMode
attribute in prefab editing mode and you then enter Play mode, Unity exits prefab editing mode to prevent accidental modification to the prefab caused by logic intended for Play mode only.
To keep prefab editing mode open while in Play mode, use the ExecuteAlways attribute instead. If you do this, you must take care to ensure your runtime MonoBehaviour code does not modify the prefab you're editing in ways intended to occur only during gameplay. For more details, refer to ExecuteAlways.
In Edit mode, event functions are not called as frequently or under all the same conditions as they are at runtime. Event functions are called under the following conditions:
OnGUI
is called on receiving an instance of EventType.ScrollWheel that's not forwarded to EventType.KeyDown or EventType.KeyUp. Events forwarded to the Game view are added to a queue and aren't guaranteed to be processed immediately.See Also: ExecuteAlways, Application.IsPlaying, runInEditMode, EditorApplication.QueuePlayerLoopUpdate.
// The PrintAwake script is placed on a GameObject. Usually, the Awake function is // called when the GameObject with this script is initialized at runtime. Due to the ExecuteInEditMode // attribute, the Editor also calls Awake when the script component is created via an Editor menu or when a scene that contains it is loaded. // The Update function is called when the Scene view needs to render, which happens when something in the scene changes or you navigate the scene with mouse or keyboard inputs.
using UnityEngine;
[ExecuteInEditMode] public class PrintAwake : MonoBehaviour { void Awake() { Debug.Log("Editor causes this Awake"); }
void Update() { Debug.Log("Editor causes this Update"); } }
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.