Crash accessing the version number
davqvist opened this issue ยท 8 comments
Hi,
I'm working on a modpack and your mod is a great help, thanks for that.
I've updated my modpack and suddenly one of our testers crashes when trying to login on our development server. After seeing the crash log, I've asked him to try singleplayer and it crashes with the same error. I looked at your code and seems it's trying to split the version number at "." but the string is null, so there's a check needed. What I don't understand though, is why he's the only one who happens to crash while everyone else can play fine. Where's your mod trying to access the version number from? Is it the modpack's version number or your mod's one? Is there a way to edit the number so that is doesn't crash anymore until you release the fix?
Crash Log: http://pastebin.com/FsAaUz9P
MPUtils: 1.2.5
MPBasic: 1.1.5
Forge 12.18.3.2221
Minecraft 1.10.2
There is suppose to be a catch in there already if its none a standard number its suppose to change it before it checks. Il look at it tonight to double check. I could have messed up the regex.
What did you version number your modpack?
He could try deleting the nbt file under /mputils. Its the folder in the root instance of his minecraft folder. It will remove any previous version numbers. I can tremember if I saved it as settings.nbt. all though getting me the nbt file will be good. And maybe your mpinfo.info file.
I haven't touched the MPUtils Version number since the start of the beta which was one month ago, mainly because I forgot to adjust, I only changed the changelog regularly. It's still at 0.1 in the mpinfo.info. I asked the user to send me the two files and will report back when I have them.
The user is apparently super busy and hasn't send me the files yet. I can send you my mpinfo file but I have no problems logging in, so I doubt that would help.
mpinfo http://pastebin.com/c3dtDPYw
mputils.cfg http://pastebin.com/mNhtjyq8
This is just a minor change.. may not fix it, but its how mputils is set up to read. I'm will be adding the null pointer catch anyways. The only thing I can think of, Is he changed something on his end or didn't get correct files. He could try remove mpinfo file and let it regenerate with defaults settings.
version numbers work better: Major.Minor.(Revesions/build)
and the authorList is and array of strings make sure to have "";
I have to add a couple other small things.. will get a build tonight hopfully
{
"name": "Age of Engineering",
"description": "The tech-only modpack with progression divided in ages.",
"version": "0.0.1",
"url": "",
"authorList": ["davqvist"],
"credits": ""
}
I set the version number before going to beta test and never changed it. I'm already at 0.1.6 so I follow the major.minor.revision logic, but forgot to change it here. Oh yeah I must have missed setting the author as string, thanks for correcting. Thanks for coming back to me and your work.