Package Version Question
Hey all! A common point of failure for Sims 4 users seems to be attempting to run with Sim 2 or Sims 3 mods. Running with Sims 2 mods will result in a cryptic “required game data is missing” ...
Forum Discussion
It seemed you had confusion about how to sort out user errors related to forgetting you had a .package open in your CC creation tool from actual game errors related to missing content. But, as I said, this is very easy to figure out by using the Task Manager :) Problems related to that kind of work flow could be solved if the developer of the tool you like just adapted their tool to your workflow. I guess the alternative is adapting your work flow to the tool you're using. Otherwise your post sounds like you're asking EA to run a check every time the game is launched to see if s4pe has grabbed a .package in your Mods folder and then pop up a special message that says something along the line of "we're sorry the game won't launch but you have a .package open in s4pe" if you forgot to close the .package you were working on.
S4pe's maslow.package issue was brought to light in the Sims 4 Studio forums in our Creator Help section in a post reporting s4pe's corruption of some .packages when merging them. I moved the discussion to our Feature Request section because it wasn't a problem with Studio as much as the identification of a feature (.package merging) it would be handy for Studio to add (and we did add it).
The same person also reported the problem at MTS forums where s4pe's inability to manage the maslow.package correctly was verified and explicitly linked (albeit without futher exploration of the issue) to s4pe's merge failures last year.
S4pe's maslow.package issue was brought to light in the Sims 4 Studio forums in our Creator Help section in a post reporting s4pe's corruption of some .packages when merging them. I moved the discussion to our Feature Request section because it wasn't a problem with Studio as much as the identification of a feature (.package merging) it would be handy for Studio to add (and we did add it).
The same person also reported the problem at MTS forums where s4pe's inability to manage the maslow.package correctly was verified and explicitly linked (albeit without futher exploration of the issue) to s4pe's merge failures last year.
