View Categories

World Builder – Runtime Scripting Assemblies

2 min read

Table of Contents

Available Assemblies: #

System

UnityEngine

UnityEngine.CoreModule

UnityEngine.PhysicsModule

UnityEngine.UI

UnityEngine.UIElementsModule

Newtonsoft.Json

netstandard

mscorlib

1. System #

Overview:
This is the core assembly of the .NET framework. It provides the fundamental classes and base types needed by nearly every application.

Key Components:

  • Namespaces: System, System.Collections, System.IO, System.Threading, etc.
  • Common Types: Object, String, DateTime, collections like List<T> and Dictionary<TKey, TValue>, exception handling classes, and more.

Use Cases:

  • Basic data types and runtime support.
  • File and stream manipulation.
  • General-purpose utilities.

2. System.Core #

Overview:
This assembly enriches your applications with LINQ (Language Integrated Query) capabilities and additional core functionalities such as extension methods, lambda expressions, and more.

Key Components:

  • Namespaces: System.Linq, System.Linq.Expressions
  • Common Types: LINQ extension methods provided in Enumerable and Queryable.

Use Cases:

  • Querying and manipulating collections in a fluent, readable style.
  • Enhancing readability and expressiveness of your code with Lambda Expressions.

3. UnityEngine #

Overview:
This assembly is at the heart of Unity scripting. It provides all the base classes and functions needed to build interactive content on Unity.

Key Components:

  • Namespaces: UnityEngine
  • Common Types: GameObject, Component, MonoBehaviour, Transform, etc.

Use Cases:

  • Creating and managing game objects.
  • Implementing behaviors in the Unity runtime.
  • Accessing Unity-specific utilities such as logging and physics interactions (basic).

4. UnityEngine.CoreModule #

Overview:
A more specific set of core functionalities provided by Unity. Many foundational parts of the UnityEngine are segmented into this module for better modularization.

Key Components:

  • Namespaces: Still under the umbrella of UnityEngine
  • Common Types: Essential classes and interfaces that support the Unity engine’s core operations.

Use Cases:

  • Handling core engine functionalities.
  • Directly interacting with the underlying systems of Unity.

5. UnityEngine.PhysicsModule #

Overview:
This module specifically deals with Unity’s physics engine. It contains the components required for simulating physical behaviors.

Key Components:

  • Namespaces: UnityEngine
  • Common Types: Rigidbody, Collider, Physics, and other physics-related components.

Use Cases:

  • Adding realistic physics to your objects.
  • Handling collision detection and response.
  • Simulating environments like gravity, forces, and friction.

6. UnityEngine.UI #

Overview:
This assembly brings in the classic Unity UI system. It allows you to build and manage interfaces using built-in UI components.

Key Components:

  • Namespaces: UnityEngine.UI
  • Common Types: Canvas, Button, Text, Image, etc.

Use Cases:

  • Designing interactive user interfaces.
  • Implementing menus, HUDs, and other UI elements.
  • Responding to user inputs through UI controls.

7. UnityEngine.UIElementsModule #

Overview:
A newer, more flexible UI toolkit provided by Unity that offers a modern approach to UI development. It is designed to work with a hierarchical, style-driven system.

Key Components:

  • Namespaces: UnityEngine.UIElements
  • Common Types: VisualElement, StyleSheet, UIDocument, etc.

Use Cases:

  • Creating editor extensions or runtime UIs with modern styling.
  • Building dynamic, interactive UI using style sheets and hierarchical layouts.
  • Enjoying a more web-like approach to UI development within Unity.

8. Newtonsoft.Json #

Overview:
This popular third-party assembly is your go-to for JSON parsing and serialization. It simplifies working with JSON data significantly.

Key Components:

  • Namespaces: Newtonsoft.Json
  • Common Types: JsonConvert, JsonSerializer, and various attribute classes for customization.

Use Cases:

  • Serializing objects to JSON strings.
  • Deserializing JSON data back into .NET objects.
  • Handling complex JSON structures with ease and flexibility.

9. netstandard #

Overview:
netstandard represents a specification of .NET APIs that are available across all .NET implementations. It ensures uniformity and compatibility.

Key Components:

  • Namespaces: Provides foundational APIs common across different .NET platforms.
  • Common Types: Includes various core libraries and utilities that are standardized for cross-platform compatibility.

Use Cases:

  • Writing cross-platform libraries.
  • Ensuring compatibility across multiple .NET implementations (such as .NET Core, .NET Framework, Xamarin, etc.).

10. mscorlib #

Overview:
Historically the core library for .NET applications, mscorlib contains essential types and base classes for the .NET framework.

Key Components:

  • Namespaces: System, along with many other central namespaces.
  • Common Types: System.Object, System.String, basic collection types, and more.

Use Cases:

  • It underpins much of the functionality you rely on in .NET.
  • Provides critical runtime support and base types used by most applications.