Packaging File Name Error

  • Modkit:20260107.9652.W.MODKIT.EGS

:scream: After multiple attempts, the packaged folder name in C:\Users\filmi\Documents\inZOI\Mods\88849 is wrong. My file is Versatile_Tank_Top_20260123, but the output folder is Bar_Table_20260114 — which isn’t even in my Modkit project anymore; I deleted that folder a while ago. The file I’m currently working on is Versatile_Tank_Top_20260123.

Hi there, is it possible that you accidentally clicked on the bar_table folder the first time your exported your versatile_top mod? When that happens, even though you are exporting ā€œVersatile_Tank_Topā€ it will be renamed to what the clicked folder was. Try deleting bar_table again and exporting without clicking anything and see if it works.

Maybe it is not the issue, but it could be, since it happened to me before.

Best of luck!

I mean, I’ve deleted it over and over. It’s completely gone. But still, after packaging, the folder name automatically changes to a different file’s name. That folder doesn’t exist on my computer anymore. And it’s from a very old furniture project. If it’s going to mess up, why not pull a recent folder name? This is so bizarre in the middle of the night, and honestly, it’s starting to freak me out!

This is very bizzare then, I don’t know what could be happening. Best of lucks :smiling_face_with_tear: :custom_heart:

Thanks for being part of the conversation. It’s nice that amidst all the busyness, we can still chat about these weird and wonderful topics — it’s a different kind of unwind :heart:

This is no coincidence. I found another bug before. When I deleted a project file and created a new one (20260112), importing a new mesh gave an error about a missing file. And that missing file was data from a very old project of mine (e.g., 20251208). The thing is, there should be no connection between two Modkit projects. How could a new project be missing a file from an old one? After that error, reinstalling Modkit fixed it. But now, less than a week after reinstalling, this problem is back. I think this issue is similar to the previous one — both are wrongly linking two unrelated projects.:rofl: