@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
