-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic: runtime error: index out of range [1] with length 0 #9
Comments
I'm getting this same issue (Linux Mint 22, bug has been around for at least a few months now). I noticed it only happened to me after I ran |
Hi both, sorry for the delay here. Summer time is vacation time. I'll look into this and see what I can do.
Maybe a screenshot of the twad ui with the specific situation? Regards |
Ok, I went to go test a little since its been a minute. Interestingly, it's no longer happening when I use DSDA-Doom, or at least not in my couple minutes of running around and trying to get a crash. I'll update if I pinpoint anything. |
Alright, thanks for the answer. I cannot reproduce the issue on my end currently either, but will leave this open since I think DSDA acts a little funky and I guess I need to add at least a section in the readme for it. It migt be the case that the unusual behaviour in some instances causes the issues here. Still twad should not crash in these instances but just either warn or go over it gracefully. Some examles of what I mean: -levelstat does not seem to work or at least I am not able to find the stat file and this file is used for displaying stats in boom-family ports. Anyway, again cheers and thanks! |
Hey. I just started getting this error after a system update.
The text was updated successfully, but these errors were encountered: