> For the complete documentation index, see [llms.txt](https://reach-cloud.gitbook.io/reach-explorer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reach-cloud.gitbook.io/reach-explorer-documentation/metaverse-cloud-engine-sdk/unity-engine-sdk/custom-scripting.md). # Custom Scripting {% hint style="danger" %} Custom C# Scripting is **NOT** supported. {% endhint %} {% hint style="success" %} Custom JavaScript **IS** supported, however. {% endhint %} Due to limitations of with AoT platforms, it is not possible for REACH Explorer to dynamically load .NET assemblies at runtime. For more details on why this is not possible, see this article by Unity: ### Does that mean I can't use ANY custom C#? No, that's not what this means. REACH Explorer has support in it's core engine for specific assets. You can see a list of assets that REACH Explorer supports here: * You may use the (unmodified) scripts provided in these assets, and they will work within the REACH Explorer app. ### Is there any other languages supported? Yes! We have a JavaScript module that you can use to write custom scripts. See [this section](/reach-explorer-documentation/metaverse-cloud-engine-sdk/unity-engine-sdk/custom-scripting/custom-javascript.md) for more information. ### What about Visual Scripting for custom behavior? **Yes!** You can utilize Visual Scripting to make complex custom behaviors that you would otherwise do in C#. REACH Explorer supports the following visual scripting systems: * [x] Unity Visual Scripting: * [x] Playmaker: ### Limitations The following limitations apply not only to custom Javascript, but also PlayMaker and Unity Visual Scripting. {% hint style="danger" %} Be aware that for security reasons, there are limitations in place that may prevent you from doing certain operations with custom scripts. See the information below. {% endhint %} [**Blacklisted Member Names**](#user-content-fn-1)[^1] * OpenURL * SendMessage * SendMessageUpwards * BroadcastMessage * Find * FindWithTag * FindAnyObjectByType * FindObjectsByType * FindObjectOfType * FindObjectsOfType * FindObjectsOfTypeAll * FindObjectsOfTypeIncludingAssets * FindSceneObjectsOfType * DontDestroyOnLoad [**Blacklisted Namespaces**](#user-content-fn-2)[^2] * System.IO * System.Reflection * System.Web * System.Http [**Blacklisted Types**](#user-content-fn-3)[^3] * Resources * AssetBundle ## JavaScript Supported Assemblies Here's a full list of all the supported assemblies in the custom JavaScript module. * netstandard 2.1 * MetaverseCloudEngine.Unity * MetaverseCloudEngine.Common * MetaverseCloudEngine.ApiClient * UnityEngine.CoreModule * UnityEngine.PhysicsModule * UnityEngine.TerrainModule * UnityEngine.AudioModule * UnityEngine.UIModule * UnityEngine.InputModule * Unity.InputSystem * Cinemachine * Unity.VisualScripting [^1]: Any members (functions, fields, properties) with these names is unusable. [^2]: Anything under these namespace is unusable. [^3]: Anything under these types is unusable. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://reach-cloud.gitbook.io/reach-explorer-documentation/metaverse-cloud-engine-sdk/unity-engine-sdk/custom-scripting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.