Re: Error Code 132:<Various Numbers>, Corrupt Ladders

Hi @SatiSim 

Try resetting your user files as described in the factory reset described in this post: http://answers.ea.com/t5/The-Sims-4/FAQ-Troubleshooting-Steps-amp-Known-Issues/m-p/3621199

You won't loose anything. Just make sure to not delete any files  and make a backup.

After renaming, repair your game by right clicking on the game in Origin.

Try on a new game with nothing added back first (start new game). If it works, put back your save game and try again. If it still works, you can start putting stuff back.

• Options.ini (or just re-set all your settings manually)
• Tray Folder
• Screenshots/Videos/Custom music
• Rest of the save games (leave out slot_00000001.save which is the autosave and no longer needed - if you still have it)
• Custom content like clothing, hair, skins, make up ....
• ConfigOverride, if you have your own configuration files.
• Mods (one by one, making sure they all still work)

The rest does not need putting back, cause they are mostly cache files that recreate or log files that are not needed for the game.

Thank you for relocating my reply, i was not sure where to put my question!
I tried almost all of the above as i saw this reply to a similar problem, but it's caused by the lot and i don't know what specifically causes it. 
A version of the build in an earlier stage is completely free of issues, but after i worked on it yesterday, the newer version will not load in live mode. 

It's only one specific Lot (maybe i should say build!) and also only in a very developed stage it suddenly gave me this error whenever i tried to access live mode on it! 
Even traveling to this lot caused me to get this error and get sent to the world view! 
I (thankfully) have an earlier stage of the build saved where live mode has no issues, though something must have happened while i worked on it and i'm really curious what... 
I don't want this to occur for anyone who downloads my builds and i also don't want to have to rewind hours and hours of work :D
I tried to deactivate snowy escape as i used a bunch of landscaping between the working and the not-working state of the build, but it didn't help.
I also tried to remove levels to maybe detect where this issue came from, but so far i couldn't make it out.
I used the T.O.O.L. mod, everything i did with that mod works on the earlier stage so that's not the issue either...

I am really clueless! ☹️

Yes, got plenty of those! Do they point to the issue?

Alright! Thanks for looking into it, i attached the file - hopefully the correct way! :D

Again, thanks for looking into it!

Weird thing is that i don't have any ladders in the build, a lot of staircases though! 
I managed to restore the progress on the older version without any issues which is even more weird - everything works fine on the version i have now, I just really want to know what made the build create errors when trying to enter live mode on the previous version.

If theres nothing else pointing to the issue, i guess it will stay an unsolved mystery, lol

Do we have a more general bug report on this because I feel we need one?
I have a Very similar problem, with a different error code (mine is 132:3d75644b:e4596f1a) and better exceptions mod is able to tell that it has something to do with ladders. I've been working on a large-ish build that has become unaccessible in live mode (as in, I can access it in build mode only but when I try to load the family that I moved there it won't load and I get the error). I have several ladders on the lot, some of them are ocean ladders since it's a lot in Sulani where I'm building. (and yeah I have already established that it's not my mods, it's that one lot. Another lot in the same neighbourhood loads just fine )

@crinrictOh, that's a new one for me! After a quick googling I'm assuming you mean TwistedMexi's allcheats? I'll give it a try right away!

EDIT: one hour later..

Nope. I installed the mod and used the command you suggested. (And yes, remembered testingcheats, script mods are enabled etc.) It was kinda hard to find information about this mod (didn't find any usage guide other than just to enable testingcheats) but I understood that it would print stuff on the console whether the cheat you used succeeded or not.. But I got nothing so I have to assume it couldn't remove that item since I still kept getting the same error (not sure if it's really important at this point what the exact error code is, since it's regenerated after each launch but always starts with 132: ).

We've been guessing around with my SO (we're a household of programmers) that it might be some object that has been removed at some point but not perfectly. Like some of the data persists? And it ruins the whole build. I'm assuming this same thing has happened to other builders too, Sati's error code started with 132 as well. Sometimes I wish I was in the dev team, I just really, really want to get this build working.. :/

@siirysiir Do the other lots in the same neighborhood work ?

The mod just basically enables all dev cheats that are usually disabled. objects.destroy destroys an object if you know the ID of the object. Was hoping that the number you had there showing in BE would be the number of the faulty object.

can you try the cheat objects.list adder to get a list of all ladder objects in your hood (not a typo, just post adder). See if there are more ladders than you're seeing.

You can try deleting one by one with the cheat above and use objects.list again to see if they really get deleted (work on a backup of course). Objects.list gives you the object ids

This thread just saved my build! Thank you both so much <3

After getting the sims 4 For Rent expansion pack and starting a new game, when i went to load the game to play it again, it give me a loading error. I have tried relaunching the game, removing all my mods and cc, restarting my computer (mac), restarting origin and nothing has worked. I uninstalled the sims 4 for a second time and downloaded all my packs exception for For Rent and the game was able to load properly. I also tested to see if it was a problem with any mods or cc I had so while For Rent was not installed, I added all the ones that I previously had as part of my game back in and it was still able to play. Finally, I downloaded For Rent again the error appeared once more. Is this just an error that people are having with the new expansion pack or is there something else?

Edit By Crinrict: Adjusted Title to better reflect the issue

Just attached it!