I think we're both overthinking things a bit.
What I call a 'template' is really a saved game that's been configured the way I like to play my games. That way I don't have to spend time hunting for settings or pouring through the sluggish Gallery to find new venues to add to all the empty lots. It's a 'complete' world without the Household I want to play in it.
Steps 5 through 10 really only apply to my current setup. You more than likely play the game differently than I do. Really, the goal is to just create a save file that you can reuse for future games when you don't feel like renovating entire districts and neighborhoods. Just don't save over the 'template' for anything other than updating configurations and lots and it'll serve you well.
The .py files listed in the lastException.txt files aren't accessible through normal means. I'd actually ignore the actual python files and pay attention to the non-EA/Maxis paths.
Errors that look like this:
Code:
Traceback (most recent call last):
File "T:\InGame\Gameplay\Scripts\Server\scheduling.py", line 212, in simulate
File "T:\InGame\Gameplay\Scripts\Server\elements.py", line 376, in _run
File "T:\InGame\Gameplay\Scripts\Server\postures\posture.py", line 1983, in _do_end
File "T:\InGame\Gameplay\Scripts\Server\postures\posture.py", line 1971, in get_endT:\InGame\Gameplay\Scripts\Server\ does not actually exist outside of the game, so you'd never find the scheduling.py, elements.py, or posture.py files.I don't have an example of when a mod actually throws an error, but it'd look a lot different than
T:\InGame\Gameplay\Scripts\Server\ which is one of the many paths used internally by TS4's game engine. But once you see it, you'll know it.Edit: I should add, since I haven't updated my Sims 4 game to the latest patch, I currently don't have any lastExceptions where a mod is being ornery.
