Thats's fair and I'm not against that transition in the long run - obviously all you try to do is improve the game. With all the feedback you have now, isn't it smarter to revert that transition (or release img files right now) while you digest all that information and release a fixed version in a later date? People cannot play the game properly and enjoy the event for over a week now, bossing aside - you can't even APQ or farm. Please reconsider?
As I said I’ve been told the current bugs should not be caused by the transition to wz files. Therefore a img based setup won’t help here. Unfortunately I can’t go into detail because I’m not involved in the development progress as I don’t have experience with that and for game security reasons.
If the client transition into wz files was for the sake of better anti-hack I can understand. But I really don't understand the concept of "better performance" in a game that shouldn't stress your computer more than it first released nearly 20 years ago. The ironic part is, the client based on wz files actually became heavier on both your cpu/memory usage. If the developers aimed to have buttery smooth 60 fps in Nibergen pew pew laser, they have succeeded. But now, it feels whenever I open up a client, I am using powerstance. But instead of falling from head C, the game crashes instead. Additionally, based on the patch notes/update notes the only "major" change in the past 3 updates/patches as far as I can see is regarding the transition into the wz-files. So if multiple people are experiencing random crashes, isn't it reasonable to assume that the wz file are the main issue? Fundamentally, the game has not changed that much since 2 months ago or even a year ago. I really don't know how the client suddenly becomes this impaired when the game hasn't changed.
Crashing issues actually increased in Update 77 and we are currently working to resolve those issues. It is related the anti-hacking improvements that were made, and we believe we have figured out what part is causing the problems and plan to release new files soon. Update 77 is the second major update which we are now using wz files, and although there has been some increase in issues while bossing, there has been a notable reduction in random crashes caused by img files. We are still working to see what we can do to reduce issues while bossing. We would like to see how things are after we have fixed the issues caused by Update 77 before considering releasing an img installation.
Possible to revert the changes at the moment? So you guys as developers have time to fix it and release it again when it is stable? At least player like us can enjoy the game while you guys fixing the issue
Could developers show/prove something fixed about "there has been a notable reduction in random crashes caused by img files"? most player don't know about coding stuff but only see the amount of problems increasing, and many of them are very likely to be those classic problems due to wz files loading. Can players actually SEE something(instead of "this and that had been fixed" or "players will no longer experience random client crash") so we can be convinced this update actually made the game better?
One clear example would be how there have not been any mass crashes within GM events when using .wz files compared to .img files.
What are you talking about??? I already witnessed 3 ola ola events getting re-hosted due to dc issues, despite my miniscule playtime in Royals these days, not to mention dc issues in valentine bosses.
I don't disagree with that either, and was just providing one example showing a reduction of random crashes caused by .img files as requested. We have already acknowledged in previous posts that .wz files do have increased crashing issues compared to .img files at bosses, and that we are working on trying to make improvements in that regard. We also mentioned that we would consider releasing an .img file installation once we have fixed crashing issues caused by the anti-hack implementation. Only one event since Update 77 was rehosted, and this was due to around 20 players crashing - this is far off the mark of what we would class as a mass crash. Any events rehosted between Updates 76 and 77 have also not been mass crashes, but likely had more crashes since players were using a mixture of .wz and .img files.
Unstable client, day 19: The heroes of Maple World are no longer capable of defeating the mighty Horntail. His DC mechanic is too strong. Despite their best efforts to defeat him, once they kill the legs and tail and begin hitting head C, they are promptly yeeted out of the game, making the fight impossible. Perhaps there shall come a time when the heroes of Maple World will be bestowed with their long lost no-DCing abilities, thus granting them a chance against the mighty beast. Then, they could save Maple World and rise as heroes once more.
I managed to survive the last 2 Horntail runs without crashing. I GFXed whenever I entered a room (preheads and mainbody) AND whenever any of Horntail's bodyparts died. I don't know if that is what really made the difference but I recommend trying this as it has worked for me.
These dc's are so random. My ppl already tried it and many other possible ways, but still failing . Can't believe it's our 23th HT | 12th AUF | 10th CWK run and there's always a guildy or two dcing. How unplayable this game became bc of the last client. How much longer we have to keep afking FM?
This also worked for me whilst playing on an Intel CPU + Integrated Graphics Laptop. Playing on self-built PC AMD Ryzen + Nvidia RTX does still crash in HT (afaik).
Our devs have been very hard at work improving the client and newly added features on the backend to help with many things that were previously "soontm" or "limited", but are slowly (but surely) becoming a reality. In the coming update (Update 78) players will be provided with a choice of a wz setup or img setup. Thank you to all players who took the time to voice their concerns and bug experiences. We appreciate your patience and understanding as we move in the coming days to prepare the next patch.