Forum Discussion
6 years ago
Excellent. I don't think it's a good idea to advise impatient creators to use a temporary workaround that does not conform with the way EA wants people to do things in the long term (as the rep did in the linked post). Some creators will go with the temporary workaround and never update to the preferred long term format. Even if the creator does update, people who have downloaded the short term fix will not go back to download the long term update. My personal feeling is that EA should select the format that will work best for the community and stick with that. If there is a good reason for creators to avoid using the 0x00000000 group number, then EA should not tell creators to use it, even in the short term. There is no such thing as a short term when you are talking about downloads that go into the mods folders of people who have no idea what "high bit" means - if the item works, they will see no need to update it.
We have counseled people to wait for direction from EA on this issue. Now EA is telling people to ignore the best practices tool makers were told to use. It's more than a bit confusing. Is EA suggesting that this fix is going to take so long that we should update Sims 4 Studio to use the 0x00000000 group number? We could also issue a batch fix to change all the broken group numbers and all other instances of the high bit for that matter. Is that what we should do? Are we going with the high bit and the problem will be fixed promptly or are we going with 0x00000000 embedded in a lot of custom content? What is the plan here?
We have counseled people to wait for direction from EA on this issue. Now EA is telling people to ignore the best practices tool makers were told to use. It's more than a bit confusing. Is EA suggesting that this fix is going to take so long that we should update Sims 4 Studio to use the 0x00000000 group number? We could also issue a batch fix to change all the broken group numbers and all other instances of the high bit for that matter. Is that what we should do? Are we going with the high bit and the problem will be fixed promptly or are we going with 0x00000000 embedded in a lot of custom content? What is the plan here?