nicegamer7
nicegamer7
So the problem even occurred on version 4.1.0?
A short video would work, although, I don't think it's necessary as I understand the problem as described. Could you run `mv debug 3` from the console then try one...
Okay, I suppose a short video wouldn't hurt. I tried to replicate this on my end but couldn't.
I watched the video yesterday and I'm not sure what would cause that. Since you don't have too many portals it shouldn't be too much work to set them up...
Glad to hear you figured it out. We'll keep this in mind next time someone reports something similar. Thanks for letting us know 😀! edit: Didn't mean to close this....
I closed this earlier because I thought I had broken the `mvinv migrate` command, however, it seems it isn't working even before these changes.
Here's a build of this PR, please report any issues :) [Multiverse-Inventories-4.0.0-SNAPSHOT.zip](https://github.com/Multiverse/Multiverse-Inventories/files/4822646/Multiverse-Inventories-4.0.0-SNAPSHOT.zip)
I decided to test the `mvinv migrate` command again, and it turns out this PR DOES break it. Although, I think there are some cases that caused it not to...
I suppose it's not needed, but I think this is the better way of doing things. No need to migrate on username change with this. Needs to be rebased though.
I couldn't reproduce the behaviour you mentioned. Try running `/mvv -p` again, and if it gives you an error send your `latest.log` file.