Selecting only one

[MathewHI]

Is there some kind of list I can expose in the editor that allows me to pick only one? I need a choice of three things and I could use bools but I thought there was a way I could make so that only one option can be selected.

[PraetorBlue]

Use an enum.

Enum basics in unity

[MathewHI]

@PraetorBlue

Use an enum.
https://medium.com/@joshwatts592/enum-basics-in-unity-7e6e2742bd0

Yes thank you.

[pixaware_pwedrowski]

Beware about enums being converted to ints under the hood - it may get messy if you add new enum values

[Kurt-Dekker]

@pixaware_pwedrowski

Beware about enums being converted to ints under the hood - it may get messy if you add new enum values

Yes, this bigtime. If you insist on enums, always assign hard never-ever-changed unique integer values to enums you intend for Unity to serialize.

Enums are bad in Unity3D if you intend them to be serialized:

Best practice to find object in List of custom classes? Do if in list, if not do something else

BUT!!! Be very careful with enumerated types since Unity’s YAML serializer does not save the mnemonic of the enum but rather just an integer. If you change your enum in code, you could potentially silently bork all your prefabs, assets and scenes that contain these non-identifier serialized numbers. I try to stay away entirely from enums for anything that I am going to let Unity serialize. Otherwise they’re great. using UnityEngine; [CreateAssetMenu] public class Attack : ScriptableObject { …

Unity Card Game Structure

Use extreme caution with enums in Unity. Unity does NOT store the actual enum such as "Block". Instead, Unity stores whatever integer number is associated with "Block" This means if you have an enum with: Attack, Block and you later add one at the start: Prepare, Attack, Block Then Block will now be integer 2, and your previously-serialized Block will now magically (and silently) become an Attack. In my opinion this is a MASSIVE failure in the serialization design that Unity cho…

It is much better to use ScriptableObjects for many enumerative uses. You can even define additional associated data with each one of them, and drag them into other parts of your game (scenes, prefabs, other ScriptableObjects) however you like. References remain rock solid even if you rename them, reorder them, reorganize them, etc. They are always connected via the meta file GUID.