"ev" enum values - how to create new ones?
Wondering if it's possible to create new "ev" values (referred to in the custom content guide as: “ev” an enum value) An example I pulled at random out of the tag file is: Theme I can't...
Forum Discussion
Hey!
An enum is just a named number so as long as the number and the name of it are unique there won't be any conflicts. You can just add anything to it as long as it's unique. The number being much higher than the rest of the existing values is the best way to avoid conflicts.
Following the example:
1000123 is really high so there is a low chance of a conflict but it doesn't have to be that big. Unless tags are saved somewhere it doesn't matter what their number is because they are just used as identification with their name instead of the number. Both still have to be kept unique.
Still, what's the purpose of this? For example, overriding the tags file will cause a lot of issues when something will be missing because of future updates and most of the tuning tests can be done with raw instance ids of objects rather than referring to them with tags.
If you're looking into extending tags for CAS then it might not be possible since outfit generation is not fully done on the scripting side which the tags tuning file is used on.
Extending enums with scripts is a pretty safe way of doing it because you can automatically avoid conflicts but it's pretty pointless because enums are just numbers so you can use raw digits.
I may be able to help more if you can explain the reason behind your interest in enums.
An enum is just a named number so as long as the number and the name of it are unique there won't be any conflicts. You can just add anything to it as long as it's unique. The number being much higher than the rest of the existing values is the best way to avoid conflicts.
Following the example:
MyNewTag
1000123 is really high so there is a low chance of a conflict but it doesn't have to be that big. Unless tags are saved somewhere it doesn't matter what their number is because they are just used as identification with their name instead of the number. Both still have to be kept unique.
Still, what's the purpose of this? For example, overriding the tags file will cause a lot of issues when something will be missing because of future updates and most of the tuning tests can be done with raw instance ids of objects rather than referring to them with tags.
If you're looking into extending tags for CAS then it might not be possible since outfit generation is not fully done on the scripting side which the tags tuning file is used on.
Extending enums with scripts is a pretty safe way of doing it because you can automatically avoid conflicts but it's pretty pointless because enums are just numbers so you can use raw digits.
I may be able to help more if you can explain the reason behind your interest in enums.
