I wouldn't worry about it at all. As for myself, the only reason I don't display my birthday is to keep my identitety secret, I guess? I dunno. Date of birth doesn't say much really but I've simply no reason for showing it everybody.
I get the idea
What about being "non-social" ? Would you like it to change over time?
As for myself, a lot of crazy things in life have happened which pretty much lead me into spending time re-mapping crystal rom which I used to do until I started developing myself and turned out a great rom hacker in overall. Now, "everything" is going well.
Sorry about that what I said in the thread, I never meant to reply in your place although that's what I did. But yeah, when you're done with Skyline, keep away from the hacking scene for a while and think about it. I've pretty much decided myself that once Dark Future gets complete, I'll retire from the scene although I'd be there to help out others to solve problems they're having.
Life is a lot more important. You know, we're both at the same age and I get the feeling we've also got a lot more in common than that (although we've never talked about anything). Not sure what I really want to say here but oh well...
Hopefully I remember right that I mentioned you to check what the ips-file does with a hex editor. If this is the case, create an ips-file between the your current buggy rom and the latest one that doesn't have the bug. Open the ips-file with a hex editor and the go to offset 0x5 (five first bytes are PATCH in ASCII code and have nothing to do with the "changing the rom" itself). The bytes in offsets from 0x5 to 0x7 determine the first offset in the "unmodified" rom to write new data to. If that offset is smaller than 6B 09 F8 (blank data FF FF FF... starts here in Ruby (U) rom), go to that offset with a hex editor (if it is for example 0A C7 23 = 0xAC723) and see what's written in there in "umodified" and "modified (buggy)" rom. You can easily change that data back to normal. After the 3-byte offset (in ips-file), there are always two bytes telling how many bytes to re-write in that offset and after these two bytes, the bytes to write there.