WOW EA admits to a cock up
nil:
It's really weird to allow system files over-written when it's not for updating.
To ask people to reinstall is to fool those who still don't know they can get copy files directly from the disc but not those who know. Maxis must have known some players not having the discs for a long long time by now. They do know that speech trickery won't fool all the people but at least those people who happen not to know or think of.
From an another viewpoint, some people really think it's complicated to copy such file back into their game system files, Maxis' suggestion will still work for those people.
The simpler the process and the fewer step, the more people will know what to do and hence the less work to respond to enquirers.
As for the over-writing and system files....
Guess what, even if certain files in the custom folder are made read-only, such files will still be over-written in the next time the game saves. So, somehow the game can undo the read-only attribute during processes.
So, a complete back-up of the custom folder is what I'm doing... I've made a template for varied usages like building, testing, playing... They're all separate, I also trim away unless neiughbourhood as well as useless data (especially the space-eater jpg preview files, they can occupy the file size from 15-70% in my cases, and I don't share them in EAxis site) in lots to save the space and the loading time. The lot folder size plunges down to ~25-30 MB from 100Mb. the more lots you have the more it matters.
The stupid tutorial folder is yet annoyance coz we can't delete it in-game for a safe delete. Need we that crap all the times? They should provide a safe way to delete it easily and maybe a new copy-back from the template in the system files just in case one needs it back.
Well, I've nullified some of those anyhow without destroying the files structure. But, that shouldn't be my work on it!
So, I've kinda optimised the loading and closing processes with lots with only 1 full preview and 1 or 2 neighbourhoods in a running copy.
added:
Because of SecuROM, EAxis still owes me the price at the time of a DVD-RAM drive! :( N, worse of it is the loss of a gift from an already deceased person...
Skadi:
I what I want to know is what happens now with custom clothes? Are they going to change where it saves, or remove the update to the skins.package?
In the mean time if I make that file read only, then I can't make custom clothes...
Either way the end user get fucked over.
jsalemi:
They're either going to have to change the exe file so the game doesn't write to those files (writes instead to a new file somewhere in the The Sims 2 directory), or make future changes/updates to a new skins2.package or something. That way, the custom clothes don't get destroyed while the new/patch stuff overrides the parts of skins.package that need fixing.
I hope for the former; I assume the later. :)
nil:
I think they should also make an option for those who have made new custom clothings to extract them for later re-integration before patching
cwykes:
Could they just set this patch to ignore the fact that the skin package has been modified? That might be possible if they don't need to change that file at all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page