Basically, wit behaves differently if the value attribute of a memory element starts with 0x (at least in the linux build).
It seems that the actual value is patched when no 0x prefixes the value.
According to the riivolution xml file format it is legal to allow 0x as prefix in the value attribute as they are considered a hex stringhttps://aerialx.github.io/rvlution.net/wiki/Patch_Format/#Memory_Patch
(hopefully this issue is only on value attributes, I have not tested it in original attributes)
test1.xml contents:
<memory offset="0x804D631C" value="4BB2ACE5"/>
test2.xml contents:
<memory offset="0x804D631C" value="0x4BB2ACE5"/>
Hope you are doing well.
Cheers.
PD: Many thanks for this tool, without it my life would be harder.
Basically,
wit
behaves differently if thevalue
attribute of a memory element starts with0x
(at least in the linux build). It seems that the actual value is patched when no0x
prefixes the value.According to the riivolution xml file format it is legal to allow
0x
as prefix in thevalue
attribute as they are considered ahex string
https://aerialx.github.io/rvlution.net/wiki/Patch_Format/#Memory_Patch (hopefully this issue is only onvalue
attributes, I have not tested it inoriginal
attributes)test1.xml contents:
test2.xml contents:
Hope you are doing well. Cheers.
PD: Many thanks for this tool, without it my life would be harder.