EA you are violating your own terms
If you have not updated your game past 1.67 don't buy anymore stuff packs or sets for Sims 3. EA is forcing update if you do. I bought 2 stuff packs and was not able to install them unless I updated...
Forum Discussion
"igazor;15283926" wrote:
There was never an ErrorTrap intended to run or proclaimed safe to run on 1.63-1.69. For a core mod, that would be impossible. Our other mods (not counting UnstranslatedKey which you do not have) are script mods, those can span multiple patch levels. Core mods simply cannot.
And let's not get silly about this. I am actually the one who painstakingly typed out which mods are suitable for which patch levels at NRaas on our downloads pages, at least for the ones released since the day 1.69 even came out.
But again, in this particular case, the only "harm" it's doing is triggering that nag message. For some players, their entire game minimizes down to the taskbar when this happens and they have no opportunity to click through it and thus they get stuck. You don't appear to have that issue. So you can keep the 1.67 version of ErrorTrap in and put up with the nag message on every startup or you can try what I suggested.
sorry not trying to get "silly about this"
This is something very serious to me. I practically own the Sims 3 store so I pretty much spent a lot of money on this game.
I must have mistakenly spoken because I download a lot of NRaas mods & the majority of them are for 1.63 - 169
as you can see here for the Master Controller mod. They did have it set up that way at one time.
http://nraas.wikispaces.com/MasterController
The nag message comes whether that mod is in the game or not.
Can't see downloading the one for specifically 1.67 will stop it but I will try it.
edit: even during this session the game still produced that nag message but the game recognizes error trap is not in it
