What's up with enum?

[zinc jewel]

So i see that you can create an enum in a script by just running

enum {ONE, TWO}

As opposed to making an enum with a name like

enum test {ONE, TWO}

When making one with a name it seems to work like a variable or an object, you can reference they specific enum in code by doing match statements etc. But what about the first one. Where does it go? How do you reference it? Can you have more than one? Why would you even want to do this instead of giving it a name? Like you didn't create a variable or an object it's just...there?

[swift carbon]

Unnamed enum kinda just turns into a constant number. You reference it by their value only.

So if i have enum like

enum {ONE, TWO}

I just access it like a normal variable

print(ONE)

And if other script want to access that variable

print(the_node.ONE)

[zinc jewel]

So the enum...is the variable?

[swift carbon]

The value of the enum become variable yes.

[zinc jewel]

What's the point of that? Like an enum is basically just a string or int variable that you can set and reference, but it limits the values the variable can have

[swift carbon]

Enum is a dictionary of string and int. Unnamed enum is when you dont care about the key and just care about the value.

[steep tusk]

For example, if you have an "Stats" class, it may be useful to have the enum without a name so you can do "Stats.HEALTH" instead of "Stats.Name.HEALTH"

[coral steppe]

An enum is more like a constant alias for an int rather than a variable / dictionary.