I mean in different sim world you can choose to either enable nraas story progression or not(there's different config for every world), but if I choose to disable it I still can't enable awesomes.

I know I can just remove nraas story progression but then when I switch to another world where I play with it, I would need to add it back and relaunch again.

yeah I turned nraas story progression off but still couldn't enable awesomes by doing setconfig.

I ran NRAAS core mod along with AWESOMEMOD ever since the NRAAS mode came out. I can't find it in my notes but I'm pretty sure I just turned NRAAS story progression off.
Game itself: Story progression on
NRAAS: Story progression off
Awesomemod: >showconfig< at the cmd prompt and check.

I have not currently implemented any method of doing this, because I wasn't aware that NRAAS story progression was "world specific". Since it makes no sense to have two story progression drivers running and fighting each other, I simply reasoned that if you installed NRAAS, you clearly wanted that one.

What do you even mean by this, anyway? You mean you have different saves in different worlds?

I want to enable awesomemods story driver while still having installed nraas story progression(disabled on the world I want to have awesomes story driver), I am wondering if I can enable it without removing the other one so I can switch between worlds(with different story drivers).

Im kinda trash at coding and whatnot so the possibility that I would even be possible to fix them is between 0 and minus and infinity. Hence, might ask here since these forums basically created the standard store fixes that are used today.

I guess a lot of people already know that the store bunk beds act very weirdly. Both the double bed and only top bunk act weird, they create like a copy of itself in the same place when reloading a save, and the top bunk version seems to be more like an afterthought than intended cause they have no name or description only a price tag in the catalogue.

Has anyone attempted to find a solution to this before, whether it was proven impossible or not.

Also not sure if this is all bunk beds but seems like it, at least the hideaway bunkbed and the one from the futuristic set.

If an action is illegal, it should be marked with the handcuffs, so I don't think this one is flagged as romantic, seeing as it's the opposite thereof. But if anything happens, let me know, because it should be totally okay to break up with someone for being 12.

It wouldn't crash your game regardless. All the code in the mod is still accessible, so even if it did somehow trigger something from that feature (which I doubt), it would work fine. You can infer this from the fact that people used to complain that awesomemod gave their pedo sims the pedo trait even when they used other pedo mods instead.

You found a bug in SMF, though, that's neat.

So Ive got pedophilia off, nothing I really want in my game. I still see the break up option such as "break up text" between my teen sim and the partner who grew up into an adult. While the romantic interactions are off, the break up option is available. Will it be considered like a romantic interaction between a teen and adult and crash my game or was it left available with intention?

Thanks

Thanks for your response. I just found this while searching around (on the nraas forums this time), does it seem plausible?

"There are no game related issues caused by the core version mismatch provided you are actually on 1.66, 1.67, or 1.69 and using a Core Mod designed for any of these. It doesn't matter whether you are running 1.67 (Origin/disc), 1.67 (Steam), or 1.69, the game files are exactly the same except for the final build number which is what the mismatch error is reporting on.

The Feb 2017 update to Awesome was indeed for 1.69 compatibility, all it does is get rid of the core version mismatch error for those on that patch. I don't think the same was ever done for the Steam version.

As long as you are certain that you are not really running a Core Mod designed for an earlier than 1.66 patch level (so that's 1.63 and prior), it is safe to dismiss the version mismatch warning and play on. The tricky part is that when the game minimizes to the task bar instead of displaying the error, some players find that they have no way to bring it back up again and dismiss the warning so the mod becomes unusable for them."

The post was from 2017 so not sure how valid it is (if it is)