Unity中CharacterStats类CurrentHealth始终为0问题求助

Hey there! Let's break down why your CurrentHealth is stuck at 0 even though you set it equal to MaxHealth in Awake()—this is a super common gotcha when scaling up a Unity project, and it's almost certainly not a Unity bug. Here are the most likely culprits to check:

1. Your Awake() Method Isn't Running (Or Runs At The Wrong Time) #

• Is the script/GameObject disabled? Unity won’t execute Awake() on a disabled MonoBehaviour or a GameObject that’s turned off in the hierarchy. Double-check the checkbox next to your CharacterStats component and its parent GameObject.
• Script execution order conflicts: Unity runs Awake() methods in an undefined order by default. If another script modifies CurrentHealth before your CharacterStats Awake() runs, it could overwrite your initial value. Fix this by setting a custom execution order in Project Settings > Script Execution Order to ensure CharacterStats runs first.
• Multiple script instances: If you’ve copied GameObjects across scenes, you might have multiple CharacterStats instances—one where MaxHealth is set to 0, and you’re checking the wrong one. Add Debug.Log(this.gameObject.name) in Awake() to confirm which object’s script is running.

2. MaxHealth Is 0 When Awake() Executes #

• Accidental Inspector reset: After adding new scenes/objects, it’s easy to accidentally reset MaxHealth to 0 in the Inspector. Double-check the value for the GameObject you’re testing.
• Missing/unloaded references: If MaxHealth pulls data from a ScriptableObject, external file, or another component, that reference might be broken or not loaded yet when Awake() runs. For example, if a data-loading script runs after CharacterStats, MaxHealth will default to 0 until the data loads.
• Serialized value mix-up: Awake() runs after Unity deserializes Inspector values, so your code should overwrite any Inspector-set CurrentHealth—but if MaxHealth itself is serialized and set to 0 in the Inspector, that’s the root issue.

3. CurrentHealth Is Being Overwritten After Awake() #

• Early damage triggers: Is there a collision, trigger, or event that fires immediately when the scene loads? A trap or enemy might deal damage right after Awake() runs, setting CurrentHealth to 0 before you can see it.
• Hidden code modifications: Search your entire project for every instance where CurrentHealth is modified. Check Start(), Update(), OnEnable(), or event callbacks like OnCollisionEnter() that might be setting it to 0 accidentally.
• Editor-only scripts interfering: If any of your scripts use [ExecuteInEditMode], they might modify CurrentHealth in the editor, which carries over to play mode.

Quick Debugging Trick #

Add logging to your Awake() method and turn CurrentHealth into a property to track every change:

using UnityEngine;

public class CharacterStats : MonoBehaviour
{
    public float MaxHealth;
    private float _currentHealth;

    public float CurrentHealth
    {
        get => _currentHealth;
        set
        {
            _currentHealth = value;
            // Log exactly who changed the value
            Debug.Log($"CurrentHealth updated to {_currentHealth} by {new System.Diagnostics.StackTrace().GetFrame(1).GetMethod().Name}", this);
        }
    }

    private void Awake()
    {
        CurrentHealth = MaxHealth;
        Debug.Log($"Awake: Initialized CurrentHealth to {CurrentHealth} (MaxHealth = {MaxHealth})", this);
    }

    // Your damage method
    public void TakeDamage(float damage)
    {
        CurrentHealth -= damage;
    }
}

This will show you exactly when CurrentHealth is modified, what value it gets, and which method is responsible—perfect for tracking down hidden issues.

内容的提问来源于stack exchange，提问作者Skatebanded