Aspiration Lock?
ReneeFox:
No, just the hourly decay. I don't want the meters to go down; only up. This one doesn't have anything to do with Motives ... just the Aspiration Meter/Score. I need to get into the game to get the accurate labels of those meters; I can't remember off the top of my head.
ReneeFox:
I hope you all don't mind if I write out my logic here to get it corrected and understood more by me. I'll just rattle off what I'm thinking, and questions will be included for anybody to answer ... to save time creating this.
Okay, after studying the BHAV mentioned for a couple of hours, what became clear were 2 lines:
9: [private 0x100E] Get in Temp 0 - Decay - Total (Param 0x0000, Param 0x0001), true A, false Error
A: [prim 0x0002] Expression (Local 0x0000 -= Temp 0x0000), true 2, false Error
Param 0 is the Mood, and Param 1 is Aspiration Score??? I think I have to insert a line that compares param1 < Local 0x0000 (assigned from the aspiration score in line #7), or the other way around, and goto line 9 if true, else goto line 2 to ignore both lines that appear to subtract from the Aspiration Score. I'm just going through the motions here. I don't know how to interpret the math going on in these 2 lines; looks like C or something. It appears that line 9 subtracts Decay, Param 0, and Param 1 from Temp 0? Line A is comparing Aspiration Score to whatever Temp 0 is, and going to line 2 if -= works; don't know what -= is, yet ... is it doing a calculation, or comparison?
OR, adjust true's & false's, and delete the 2 lines so decay doesn't happen at all? I'm afraid that would negate increasing the Aspiration Score somehow, i.e., one of those 2 lines (or both) handles increasing aspiration??? I have very little idea of what the rest of the code really does in total, but I usually don't know it all when I'm modifying code. Do I need to understand more or less here? This code calls resources that handle when the decay occurs, so, I don't have to worry about that as long as I prevent the score from going lower than it currently is. Line C appears of interest to me, too, but I don't really know what's going on there, i.e., what the constant is, and the purpose of PersonData Flag 1:
C: [prim 0x0002] Expression (Stack Object's PersonData Flags 1 Flag Set? Const 0x0119:0x23)
I don't think I have to worry about the above line, because it is setting flags which is what I want. I just have to make sure previous logic prevents Aspiration Decay.
Am I close? ??? Anybody out there? 8)
ReneeFox:
Well, geesh! Nobody willing to share their hacking skills? I guess some things never change; happened when I was hacking in the Sims 1 world :D. Anyway, for anybody new to the TS2 hacking-world, I figured it out with hunches. Even though I don't know the details of what much of the code means, deleting those 2 lines did the trick! Aspiration still goes up, but it doesn't go down. Yay! Thanks so much for the lead to the correct BHAV to mess with.
;D
Ellatrue:
The problem with having aspiration only go up, rather than down, is that it would take a very short time for your sims to max out and reach platinum. In which case, why not just cheat and make them perma-plat? Or use one of Inge's Simlogical hacks (I think there might be some on MTS2 as well) that just freeze the aspiration meter. Having it still change, but only going up, seems kind of pointless.
Maybe what you want is a slower rate of decay? Anyway, glad things worked out.
Navigation
[0] Message Index
[*] Previous page