This could go to troubleshooting, I think. Anyway, if you script a creature - like a creature you are about to make an invisible servant out of, for all sorts of menial tasks - if you script a servant, I say, to look around for Nearest, SecondNearest and so forth so it can, for example, cast a spell on them, he will totally ignore and snub Specifics values and Spell State values that you may have wanted to distinguish the target with. This goes for both custom and basic entries in those IDS files. For example, if you tell him to look for
and so on for everyone up to TenthNearest, the servant will just turn his nose and not notice any of them. He will react to Race, Class, Alignment and Gender that you can set through opcode 72, Set IDS State, but not Specifics. This makes Specifics a lot less useful for doing what it's supposed to do, marking things. I'm less certain about Spell States, but I wasn't able to get the servant to notice those either. I don't know if switching someone's class through 72 is an actual game change or only a formal change, the same for gender-swapping and so on. I haven't tried. If this opcode only changes the IDS value, it can be used as a marker, but turning someone's class to ANKHEG is an awfully theatrical way to get noticed.