[FIXED] Skin gets white/gray after being resurrected (and dead)

[Fresshness]

Looks like a savage (I think savages were those white/grey naked looking fellows on the OSI shard).

Obviously that is not useable for a public server

[giwo]

I was unabled to reproduce this bug with 0.98-3.6d using both a GM and a normal character.

Please give us your UOX3 version, the EXACT steps to reproduce (if you can reproduce it at all) and any pertinent information (IE did you shutdown the server at any point in reproducing the bug, was it a human or elf type character, and so on).

[Fresshness]

It seemed to have only occured once. which is a good thing

thanks for putting up with my nonsense.

[stranf]

It does it on certain characters on my shard. 3.6c. (Example, it happens to my miner when he dies, but not my main PC)

I'll update to 3.6D and see if I can reproduce it.

[Grimson]

Taking in mind these threads:
viewtopic.php?t=1053
viewtopic.php?t=1029
viewtopic.php?t=1000

Can it be that the OriginalID tag in the worldfiles get's corrupted/overwritten at some point?

[giwo]

I'm relatively certain that it is a common issue causing all of the symptoms, the problem is finding the central issue.

I wouldn't be suprised, however, if everyone experiencing the problem used UOX3 0.98-3.6 or some of the CVS builds immediately before it's release. Somewhere along the line some changes snuck in that caused worldfile corruption, which could have caused the OriginalID tag to become malformed.

[Fresshness]

FYI, I'm using UOX3 0.98-3.6b.

I don't want to sound UOX3-expert-ish, because I am far from that

but, I indeed saw (in one of those .wsc files, I think it was 5.1 or 5.2) that the OriginalID 0x190 0xsomething was reset to OrignalID 0x190 0x0.

I think the second argument is the skin color (first being the character id, in this case human male).

I hope this helps a bit.

EDIT: I have found that this was affecting only the first 2 characters of account 1. Much like the female getting into male transformed-oddity I experienced aswell.

[stranf]

For what it's worth Giwo,

I never installed 3.6, I recieved the error warning before installing it. I went from 3.5o or p right to 3.6b.

So the error was most likely caused in the 3.5 batch of CVS builds.

Probably nearly impossible to find out where.


Could it be possible to add a feature in your character exporter to change the skin tone, hair color, hair style, sex, etc of your PCs?

That way we can have a nice interface to change our PCs back in the event that one of our worldfiles gets corrupted.

Just a thought. Such a feature would be nice anyway, and it would also be a temporary fix to various "rare", hard to reproduce character bugs that are popping up.

[giwo]

Well, there is certainly room for new features in the CharacterExporter. Given the free time I will look into adding an Edit feature for characters.

As for when that particular bug was introduced, it happened somewhere along the line in the 3.6 testing phase, which could be any build between 0.98-3.5a and 0.98-3.6b (as it was corrected for 3.6b and thus the re-release).

Basically, to clarify what the bug was, some world tags were being saved as hexadecimal values (like 0xFF) but without the 0x infront of them (so FF). This would cause UOX3 when reading in those saved tags to handle them as decimal (as hexadecimal 0x16 without the 0x infront of it looks just like the decimal value 16, where it would actually be 22 in decimal). And thus values would randomly change as they would get read-in as decimal, and then saved as hexadecimal.

The unfortunate reality of worldfile corruption is that once it's been done, it really can only be undone manually. Even when the issue causing the worldfile corruption is fixed, if it's been corrupted, the data will still not be correct. (for instance if it read in 16 instead of 0x16, when it next saved, that value would become 10 rather than 0x10, which on the next server restart would then be read in as decimal number 10, and later saved as A rather than 0xA).

The easy way to distinguish if this is an on-going issue or an issue caused by previous worldfile corruption is to do this. Create a brand new character using 0.98-3.6b or better and attempt to reproduce this issue. If you can still reproduce it, there is definately a bug somewhere not caused by worldfile corruption.