Unity 6.8 replaces Mono with CoreCLR. This modernizes Unity’s C# runtime, but developers must adapt to stricter rules and new APIs.

---

🔹 1. Floating Point Operations

• Change: CoreCLR enforces IEEE 754 math rules.

• Impact: NaN is never equal to itself.

// Old
if (value == value) Debug.Log("Equal");

// New
if (float.IsNaN(value)) Debug.Log("It's NaN");

---

🔹 2. BinaryFormatter Removal

• Change: BinaryFormatter is insecure and removed.

• Impact: Use JSON serialization instead.

// Old
BinaryFormatter bf = new BinaryFormatter();
bf.Serialize(stream, playerData);

// New
string json = JsonSerializer.Serialize(playerData);
File.WriteAllText("save.json", json);

---

🔹 3. Managed Debugger API Removal

• Change: Unity’s custom debugger is gone.

• Impact: Use standard .NET debugger.

using System.Diagnostics;
Debugger.Launch();
Debugger.Break();

---

🔹 4. Static Initialization Order

• Change: Static constructors may run unpredictably (sometimes on background threads).

• Impact: Don’t rely on them for setup. Use Unity lifecycle attributes instead.

// Old
static MyClass() {
    Debug.Log("Runs at startup");
}

// New
[RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.BeforeSceneLoad)]
static void Init() {
    Debug.Log("Runs before scene loads, predictable timing");
}

---

🔹 5. Type Accessibility Enforcement

• Change: CoreCLR strictly enforces public, internal, and private.

• Impact: No more “cheating” into internal methods.

// Old (Mono might allow)
internal class Helper { internal void DoSomething() { } }
new Helper().DoSomething(); // Might succeed

// New (CoreCLR)
new Helper().DoSomething(); // ❌ Throws MethodAccessException

---

🔹 6. Overflow Checks

• Change: Casting large numbers into smaller types throws exceptions.

int big = int.MaxValue;
short s = checked((short)big); // Throws OverflowException

---

🔹 7. AppDomain Unload Removed

• Change: No more domain reload in Play Mode.

• Impact: Static variables persist — reset manually.

[RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.SubsystemRegistration)]
static void ResetStatics() {
    myStaticVar = null;
}

---

🔹 8. Text Encodings

• Change: Only a few encodings registered by default.

• Impact: Register extra ones manually.

Encoding.RegisterProvider(CodePagesEncodingProvider.Instance);
Encoding sjis = Encoding.GetEncoding("shift_jis");

---

🔹 9. Assembly APIs

• Change: Assembly.Location no longer works.

• Impact: Use Unity’s new API.

string path = Assembly.GetExecutingAssembly().GetLoadedAssemblyPath();

---

🔹 10. Fast Enter Play Mode

• Change: Static variables no longer reset automatically.

• Impact: Reset them yourself.

[RuntimeInitializeOnLoadMethod]
static void ResetStatics() {
    score = 0;
}

---

Unity Lifecycle Attributes (for predictable setup/reset)

Unity provides attributes to control when methods run:

• [RuntimeInitializeOnLoadMethod] → Runs when game loads.

• RuntimeInitializeLoadType.BeforeSceneLoad → Runs before first scene.

• RuntimeInitializeLoadType.AfterSceneLoad → Runs after first scene.

• RuntimeInitializeLoadType.SubsystemRegistration → Runs when subsystems register.

---

Quick Takeaways

• Respect access modifiers (public, internal, private).

• Don’t rely on static constructors — use lifecycle attributes.

• Reset static state manually in Play Mode.

• Switch to modern APIs (System.Text.Json, System.Diagnostics.Debugger).

• Handle NaN properly with float.IsNaN().

• Register encodings explicitly if needed.

---