Batbox writing to objects.package

[Arzenic]

I've used the batbox to rename townies often, sometimes 'change first name' doesn't take after a 'copy to last' or having changed another sim's name unless I unpause the game, but that just means that nothing happens.

Playing a new uberhood in a game with maybe a third of the cc in my main game folder, so far twice the renaming has gone...wrong.  The cancel error didn't pop up for me to enter name, it went straight to the 'new baby' screen, twins both times, and has the name of an NPC object at the top and a random townie at the bottom.  The first time it was Bigfoot but I didn't realize the problem because I forgot there's no instantiated Bigfoot copy in this hood.  This last time it was Crumplebottom.  There's no way to cancel the naming, you can only 'ok' it and, when I checked, indeed my objects.package had a new date and filesize.  Luckily I had a copy that I've now made read-only, so no need to re-install/re-patch but seems like a VBT that it keeps choosing NPC objects that shouln't be overwritten when it errors.

[J. M. Pescado]

If you're using the SHIFTCLICK version, it's regarded as "dangerous" and you use that version at your own risk. I have tried adding some more variable clears to clean out potential trash, but it's REALLY not meant for you to be doing that frivolously and I have no idea what you did to cause that.

[Arzenic]

Noted.  Had assumed the risk was mainly to my hoods, not game files, but now I know so I'll be a bit more circumspect about using it.  Wish I knew, well actually wish you knew, what could've caused it to react so differently this time.

[J. M. Pescado]

I can honestly say I've never actually seen that happen, but I added a few more lines to zero out some more temp variables that are often rubbish-filled and used for passing data like that. But really, you should have locked your objects.package file anyway.