It took me a while to figure out how property defaults work, so I will share with you what I’ve learned. Your example can be simplified to the following, and I’ll explain why:
A quest is a kind of thing. A quest can be discovered. A quest can be completed.
When you declare a binary property, the first (and possibly only) value that you give is the “turned on” value. By default, binary properties are “turned off:”
a quest can be discovered [but by default it is not discovered, so you don't have to state that explicitly.]
Even if you give a name to the second, “turned off” value, that’s still true:
a quest can be discovered or undiscovered [the default is still "not discovered," but now that has a name: "undiscovered."]
But beware! As soon as you add a third possible value, the property stops being binary, and the default values are flipped. Instead of the last value being the default, now the first one is the default! For example:
A quest can be discovered, completed, or undiscovered. [the default for THIS is "discovered!"]
In practice, this is usually what you want. You can think of a binary property as something you “turn on” when the time comes, so it starts out in a nondescript “turned off” state. But an enumerated property is something that counts up from zero, so it’s natural for it to start out at zero. The following ordering would make more sense, wouldn’t it?
A quest can be undiscovered, discovered, or completed.