"Binary" variable type addition

[Jaohammed]

Hi there, it would be really useful if we could add variables that had the "binary" type, as some games have bitfields where each bit represents an individual thing, and as of now it's not possible to make each bit in the field its own individual variable for proper labelling.

Below is an example of what can be done using Cheat Engine, but can't be done on DME as of now.

Lastly, as a long time user of DME let me thank you for making this software, it has been an invaluable tool for TASes! Even if this feature can't be added, everything we already have is plenty, this is just to make labelling a very specific type of data possible.

[dreamsyntax]

Could you show an example with an actively attached game? Im not sure I follow how this is different from changing the View mode to Binary on an array in DME

Edit: oh, saving as a separate watch for a single bit within this type? Besides naming you can achieve the same functionality, right?

[Jaohammed]

Yeah, I can already see the values just fine and edit them individually, it's just a matter of not being able to assign labels for each of the bits individually, let me attach a screenshot below

The highlighted fields there are 2 halves of a bitfield where each bit corresponds to an upgrade for the character I'm currently playing as, and it would be really useful to be able to have labels for each upgrade, because as of now we have to either know them by memory for consult a table, or just try values and see what upgrade we get.

The same thing applies to the other bitfields, but the upgrades one is the only one we have the exact information about each bit so far.

[dreamsyntax]

@cristian64 do you think this would require a node watch node type to accomplish?

[Jaohammed]

I don't know if this is helpful, and you probably already know it, but here's how the variable is set up in Cheat Engine

[cristian64]

I think the request makes sense.

@cristian64 do you think this would require a node watch node type to accomplish?

It almost feels like this type would be similar to an array with some extra metadata (bit offset and bit count), so perhaps it could be an extension of that with an alternative representation in the widget.