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
The problem s4pe has handling the maslow.package is occurring because s4pe is not completely compliant with the way game.packages should be managed.
It is unclear to me why you think anyone should have reported this to EA or why you are doing so now. It's a tool developer's responsibility to bring their tool into compliance with how the game is made...not the game maker's responsibility to bring their game into compliance with a modding tool that is doing things the wrong way.
EA was kind enough to give us an example gold standard .package. The idea being that tool developers could use it as an example to guide development of their tool. s4pe isn't capable of dealing with it properly and that means s4pe is, in some fundamental way, lacking compliance with the game...that is, there is something wrong with the tool. When something is wrong with a modding tool the appropriate place to seek bug fixes for it is the developer's web site. In this case, s4pe's problem goes beyond a mere inability to manage the maslow.package. That failure is symptomatic of the same problem that causes it to corrupt some previously game-safe items when it merges them. This would be of some concern to the Sims 4 community if there was no other tool to use for merging .packages. Fortunately Studio is able to both manage the maslow.package correctly and merge content without breaking it. Because EA does not advocate merging .packages, and they don't work on s4pe, s4pe's failure to successfully merge .packages isn't their concern nor can they do anything about it. The only people that can do something about it are the people developing s4pe.
This thread is about people putting Sims 3.packages into their Mods folder and having the game not start as a result. The question was: would it cause the community any distress if the game was made to skip over these .packages instead of failing on them. I don't see any post in the thread indicating that it is a general request thread. Of course EA may choose to change the error message the game gives...that's up to them. I agree with Nearia35 though...I would hope that creators understand how the tool they're using works and manage to close files before starting the game if that's what the tool they're using requires. I don't see this as an issue of such proportion that a special request to "fix" it doesn't look a little out of place in a thread that was started as a courtesy to our community not as an open invitation to vent pet peeves resulting from user error.
It is unclear to me why you think anyone should have reported this to EA or why you are doing so now. It's a tool developer's responsibility to bring their tool into compliance with how the game is made...not the game maker's responsibility to bring their game into compliance with a modding tool that is doing things the wrong way.
EA was kind enough to give us an example gold standard .package. The idea being that tool developers could use it as an example to guide development of their tool. s4pe isn't capable of dealing with it properly and that means s4pe is, in some fundamental way, lacking compliance with the game...that is, there is something wrong with the tool. When something is wrong with a modding tool the appropriate place to seek bug fixes for it is the developer's web site. In this case, s4pe's problem goes beyond a mere inability to manage the maslow.package. That failure is symptomatic of the same problem that causes it to corrupt some previously game-safe items when it merges them. This would be of some concern to the Sims 4 community if there was no other tool to use for merging .packages. Fortunately Studio is able to both manage the maslow.package correctly and merge content without breaking it. Because EA does not advocate merging .packages, and they don't work on s4pe, s4pe's failure to successfully merge .packages isn't their concern nor can they do anything about it. The only people that can do something about it are the people developing s4pe.
This thread is about people putting Sims 3.packages into their Mods folder and having the game not start as a result. The question was: would it cause the community any distress if the game was made to skip over these .packages instead of failing on them. I don't see any post in the thread indicating that it is a general request thread. Of course EA may choose to change the error message the game gives...that's up to them. I agree with Nearia35 though...I would hope that creators understand how the tool they're using works and manage to close files before starting the game if that's what the tool they're using requires. I don't see this as an issue of such proportion that a special request to "fix" it doesn't look a little out of place in a thread that was started as a courtesy to our community not as an open invitation to vent pet peeves resulting from user error.
