but the object is added by the sprx, but what is its name?
That's the real problem to do some of the things i was mentioning
The idea is the sprx probably have an area with some data that represents the same we can see in the rcoxml generated by rcomage
The names of all the objects and all the values should match, the biggest difference is the sprx have additionally objects that doesnt appears in the xml
So... if we add that objects in the xml in the same exact positions matching the sprx... this allows us to have a bit of control of them
Most probably the sprx is going to override whatever value change we do in the xml for that object... but we dont really know, also i think there are some features that cant be overrided (like the animations because are values that changes along time)
Edit : when i open the prx in IDA Pro i see there is an element called "plane_progress_unknown" !!
That one could be... actually all names including the word "progress" are candidates
By comparing that names (from the sprx) with the names in the xml (from the rco) it can be deduced which ones are
not what we are trying to find
--------------
Some of your screenshots when you was trying to find the color in hex value are just coincidences, not related
When doing this kind of search you need to look also at the other bytes around it, like in this example:
This is a table where are repeated the entries, like a checkered pattern. Take a look 3 lines up or down the 008000, is doing this:
006000 ---> 006800 ---> 007000 ---> 007800 --->
008000 ---> 008800 ---> 009000 ---> etc...
-------------
Right now i think the colors are not stored like that in the sprx's, what is stored inside the sprx are the multiplyers (but not the hex color code itself), i think is made everywhere by using this multiplyers
colorScaleR="1" colorScaleG="1" colorScaleB="1" colorScaleA="1"
*And i think the montly color filters are working this way too