Values on script populated inside prefab, but not in the inspector

[Kurt-Dekker]

There’s kind of a cascade of serialized values here to beware of, each subsequent one having a chance to overwrite the previous one, if it exists.

1. the value defined in code

2. the value overridden in void Reset() (if present)

3. the value saved in the prefab

4. the value saved in the prefab override

5. the value saved in the scene.

When in doubt, wipe these things out and create them afresh.

Here’s more insight into the problem:

Field initializers versus using Reset() function and Unity serialization:

Sensitivity in my MouseLook script.

Whatever value you set and save in your scene or prefab will wipe out the field initializer value you change in the code above. This is a common source of confusion: the object is created, so at that instant in time it has the value you set in code, but before the object is put into use, if Unity has a saved scene or saved prefab that this is already in, then the value saved is overwritten. It’s best to remove the initialization value above and instead provide it in a Reset function: public f…

Crouch speed is faster than Movement Speed

If something is public: The instant you add that to your scene / prefab it is 10f … AND THEN IT GETS SERIALIZED. Now go change the value in code. Note that it has no effect: the serialized value writes over the code value. This is how Unity serialization works. If you want to define it in code, make the variable private. If you want to define it in the editor, make it public and DO NOT INITIALIZE IT. Instead, make a Reset function, which ONLY runs at the instant it is added: void Reset(…