Open mello0 opened 2 years ago
Hello,
I don't use discord for support unless files need to be transferred as this is an account used for other purposes.
Regarding your issue, first make sure you're using latest and that the game version is properly recognized (no modified resource files). Try to package your mod folder in a 7z and send it, you can remove the nus3audio at this time.
Ah, ok, I'm sorry then!! Here's a link to the 7z, sorry that it took so long. I've removed all the nus3audio and brstm's.
https://drive.google.com/file/d/111ObZzxOb2UyS6CkAwbqt03EaQ3LMQrt/view?usp=sharing
Sorry it took me a while. Looks like your MusicOverride/order_override.json is corrupted. If you remove that file it loads. I'm not sure how it got corrupted, assuming it crashed while saving. On later versions you should have backups created automatically so you could try to go back to the last valid file.
If you think you've got an idea of when/how it happened, let me know!
Sorry for being late, but I got it up and running. Thank you!!!!!!
HI there. I seems to be having the same issue as the last person who had talked in this thread. Also like the last person, I wasn't getting an answer from the Smash Ultimate Discord, so I figured heading to the source would be best.
As for my issue..? I had deleted a few files in the game, mainly the resource files the exe was using before, and I think that's what softlocked it. So, now its just endlessly looking for a file that doesn't exist. Issue is, I'm not sure how to override this. Been hard to figure out.
So, hopefully you have some insight on this possibly. Thanks in advance. ^^
Hi, I tried to contact the dev on discord multiple times but did not receive any response, so leaving an issue here is the best I can do. After adding a few tracks, this error began to appear whenever I opened Sma5hMusic.
"There was a general exception during Init. Object reference not set to an instance of an object."
I had gotten this issue a while back, and I was later helped, as I found out that there was an issue with my metadata_mod.json file. When I ran into the error again, I went back to the person who had helped me before, expecting the issue to be the same. However, they told me that the file seemed perfectly fine, and suggested I leave an issue post here. And that brings us to now.