"Cupid;c-16870673" wrote:
"drake_mccarty;c-16870655" wrote:
Is there even any confirmation this issue is resolved in the next patch?
No, nor did I say there was.
"drake_mccarty;c-16870655" wrote:
To be completely honest this seems like something that should have been caught prior to release, the rhetoric that one shouldn’t have to mod their game for it to function correctly is applicable regardless of when the pack released. If something is broken it’s broken, allowing them a chance to fix it doesn’t stop the issue from happening.
But they didn't catch it, and now we are waiting for it to be fixed. No one is expecting anyone to mod their game to fix a bug that has existed for all of 3 weeks, but at the same time they aren't going to release an update every time they fix a bug.
Correct and that’s how they choose to operate. The time between when the issue was first noticed and when the issue is fixed will be filled with people complaining about said issue, that’s expected and isn’t a rhetoric that Maxis should be unfamiliar with at this point. When mistakes are made that directly affect the customer’s enjoyment of the product they purchased you are going to hear complaints until it’s fixed. I personally don’t care how long the pack has been out, something so obvious should have been noticed - but that’s really no different from any other pack they have released and really not where I’m trying to go with this. They’ll get their chance to fix it when they release a fix, until then people are free to complain about issues. I reiterate, just because the developers have acknowledged the issue doesn’t mean it stops being an issue in the meantime. A player saying “I shouldn’t have to mod my game for this to work correctly” is in the right 100% of the time, because the reality is that they shouldn’t have to mod their game for it to function as it was advertised.
