TES5 CTDA Type

[mufcfan]

Hey Everyone!

 

I want to edit the CTDA of a Condition in TES5Edit and I find the Type value weird.

I read these:

UESP wiki on CTDA Field

Explanatory topic on old Bethesda forum

 

I understand that the first (or top) three bits are used to define the operator. However, I find no logical connection to the specifications with the way TES5Edit actually interprets them:

100   Equal

000   Not equal

010   Greater than

110   Greater than or equal

001   Less than

101   Less than or equal

 

I've tried to calculate five ways, but 100 doesn't add up to 0, and 000 doesn't add up to 1 or 20, just to point out the weirdest ones.

Obviously, I can make the changes in TES5, but the fact that I don't get the logic is driving me crazy.

 

Can someone please explain to me the logic behind these numbers?

 

Thanks in advance!

[yatol]

5 hours ago, mufcfan said:

Can someone please explain to me the logic behind these numbers?

 

 

0,1,2,3,4,5,6,7,8,9,10,11....

0,1,10,11,100,101,110,111,1000,1001,1010,1011,1100...

0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f,10,11...,1a,1b,1c,1d,1e,1f,20,21...

 

16 478 596 254

in binary 1111010110001100110110110010011110 (for pc, it's either write or not write)

in hexa 3d6336c9e (easier to find that than the binary)

 

 

 

[mufcfan]

Thanks for replying!

 

I can calculate with these numeral systems. What I don't understand is that the wiki says that the value 0 means Equal, but in reality binary 100 means Equal.

I don't see the logic of how binary 100 is translated into 0 or binary 000 is translated into 1 for that matter.

I can translate binary 100 to these decimal values using two's complements and similar operations: 4, 8, 3, 7, 11. But what calculations should be applied which gives 0 and works for the other values as well?

 

Was this changed at some point and the wiki is outdated?