Posts: 17,217
Thanks: 1844 in 10 Posts
14 Achievements
I wouldn't worry about the LTW thing. You can find a lot of nonsense and half-truth on the Wiki, depending on who edited it last. I've got a Delilah who wants the Gaming career and one who wants to be a City Planner. I seldom get a University sim whose LTW matches what the Wiki says, and I think it's assigned randomly on first load of the character, along with turn-ons/turn-offs and other features that post-date university.Culinary isn't normally a Knowledge LTW, but you may have a mod for that. Just give her what you want her to have. No wants is a problem if it persists, but it doesn't necessarily mean a corrupt sim. Sometimes it's a mod conflict. Sometimes it's a bad lot. Sometimes the game just stutters and the wants thing fixes itself. After a little gameplay, the training mechanism will kick in and she'll get less generic Wants.
Strictly speaking, corruption arises because data gets assigned or used in an inappropriate way. This is almost always because a character is deleted, leaving data behind; or because a character has incomplete data for some reason, or because data gets damaged due to some computer event (such as a crash while saving). The organizing principle of sim identity is the Sim ID Number. This is supposed to be unique. Due to a design flaw, when a sim is deleted, some data are left behind, still using that ID Number; but the number is perceived by the program as being free to re-use. The result is that, for instance, a number for which data appropriate to an adult male sim may be reassigned to a female cat sim, or a newborn baby, and that data will be used by the new sim regardless of whether it makes sense. Similarly, if a sim's data are damaged, it may render it incapable of behaving normally.
Another form of "corruption" occurs due to normal data deterioration. All your programs accumulate a certain amount of wear and tear on their data; but most programs are simple enough, or robust enough, for this not to be a major problem. The Sims 2, however, is an extremely complicated program even before you add in mods and mod combinations, different user interfaces, and user peculiarities or experiments that were never anticipated by the programmers. So you get a certain amount of virtual grit in your data. Some of this kind of corruption, and the more detectable and isolatable forms of major corruption, can be dealt with by a program called Mootilda, called the HoodChecker.
To minimize corruption, make sure you have the truly essential mods, the ones like "nounlinkondelete" and "nocorruptdeath" that prevent some of the more common types of accidental data deletion. Never delete characters from a neighborhood you want to keep. And on some sort of schedule that makes sense for your gaming habit, make it a habit back up your neighborhood, run the HoodChecker (on Remove setting) on it, and then resume play. While playing, you can also use editing tools like the batbox to check for and delete corrupt memories and fix some problems.
Always back up your neighborhood and run HoodChecker before making major changes like adding a subhood or a major mod (such as ACR or a multi-PT), so you can revert if anything goes wrong.
And when little glitches arise, if you know you haven't done anything terrible like send someone to a lot bin - troubleshoot, clean up the effects, and keep rolling. Because you can't play soccer with a clean ball! Stressing about this stuff is no fun, so once you've developed some good habits, don't spoil your own fun by stressing about it.
Ugly is in the heart of the beholder.
(My simblr is
Sim Media Res .
Widespot,
Widespot RFD: The Subhood, and
Land Grant University are all available here. In case you care.)