ZOMGPets Job Fixes: Because Maxis Screwed The Pooch Again

<< < (10/16) > >>

Ivy:
Quote from: V... on 2006 November 16, 19:44:10

umm, wait a minute, will that affect those of us who only have harderjobs?


Well, according to the RTFM:  "Required for harderjobs."

You should have this anyway...

J. M. Pescado:
Quote from: V... on 2006 November 16, 19:44:10

umm, wait a minute, will that affect those of us who only have harderjobs?

This hack is required to use harderjobs. See "requires". If you have harder jobs, and don't have this, your game doesn't work. Actually, if you don't have this, your game just doesn't work, period. See "VERY CRITICAL" status.

V:
Okay, well, D'uh. I do have petsp0-jobfixes.package and the harderjobs.package. But when I read Kevin's quote:


Quote from: KevinTMC on 2006 November 16, 19:18:35

I was running the old Dizzy d2Check scanner today, and noticed that it turned up a potential conflict for this hack with harderjobs:

Code:

File: petsp0-jobfixes.package, conflicts:
Type = 53545223, Group = 7F8F4EB6, Instance = 12F in file harderjobs.package

I'm presuming there's no reason for concern, but wanted to make sure that was out there.


I thought that this was referring to a hack named "Dizzy d2Check" - which I had never heard of  before (as a hack, because it is a program- again with the "D'uh" moment). And I was all concerned that a modification was being made to a perfectly good hack based on some hack I had never heard of before and wasn't at all sure that I wanted.

So please disregard my earlier question. I had a bad case of "eyes running ahead of the text". And I am off to update the new & improved harderjobs.

Sorry for the misunderstanding.

J. M. Pescado:
Heh, not really improved, just removed the redundant stringset to avoid it showing as a conflict, which was harmless.

redmachine:
I was having this error whenever a certain sim tried to get in their car to go to work. So I checked that all my hacks were up to date and petsp0-jobfixes was the one I needed to update. Initially, this seemed to fix the problem, but a couple of sim days later it's happening again.

anyway, I'll attach the log just in case.

Navigation

[0] Message Index

[#] Next page

[*] Previous page