-
Notifications
You must be signed in to change notification settings - Fork 13
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
Issue on Windows 10 Pro with Live/Evil Twins (★ and ☆) #71
Comments
Actually it only crashes in multiplayer, if you run it in solo mode it won't crash |
Ah, good catch! Finally we got it narrowed down. Yes, the little ☆ is a unicode character which might throw something off in the code. Unicode support is a nasty issue which is often overlooked when developing. I'll look into it soon. |
it seems like the higher resolution you play it on the more likely the chance that it crashes too maybe? it's always at the beggining of the duel when you draw 5 cards it and says "DUEL", so maybe game is trying to load stuff properly and gets overwhelmed or something |
Game crashed pretty suddenly, with the audio stuttering. Feels like program is becoming more unstable on this computer over time, I feel like uninstalling doesn't reset things very well, also terminate application forcefully almost always says "Failed to terminate the process with process id: 30280" when it didn't before.Error report: java.io.IOException: Remaining try count exceeded, failed to find function: ipBndkd2mmKZ72foCV6I |
For about a year master duel wasn't working on one very specific account and I didn't really know what was going on, I could play the acccount without Jmaster Duel bot, but when I activated it the game would crash. I tried running it on a laptop running windows 11 and it worked so I just played on that. Recently though I tried running it again, and realized I could play with any other deck that wasn't live twin, so when I narrowed it down I realized it was literally just the cards with the little ☆ in their name that was crashing the game, any idea what is causing this?
The text was updated successfully, but these errors were encountered: