+1. If this gets implemented, all bossers will have a peace of mind and there will be virtually no ppl smegaing for rewarp/taking to the forum shoutbox to look for GMs. So it'll be nice for GMs too because they can focus their time and attention to the more important stuff!
No idea about crashes for multi clienting, but have you considered duplicating your MapleRoyals folders for each client you want to use, so they aren't loading and reading from the same wz files?
If there's a way to detect a disconnect that isn't manually exiting the game or ending the application, and the rewarp room makes you wait five minutes then yeah I can see this working. So even if some loon wants to bypass seduce by turning his wifi or router off, the party has to wait five minutes. Then again I'm not sure if that's enough insurance to prevent shenanigans
I'm slightly lost. Can you please clarify what you meant by duplicating the royals folder in order to not load/read from the same wz files? I already have separate folders for different graphics and for e.g, if I duplicate the HD royals folder to launch 2 HD clients, wouldn't they load from identical wz files? Since the latest patch, I downloaded and installed both HD and 800x 600 setups separately. Upon installation, they created their own folders with independent launchers. I only replaced the sound.wz file in the HD client mapleroyals folder but not the 800x 600 folder (I procrastinated since I'm only concerned about crashing on HD client where I'd log in to my main character). In the aforementioned scenario, I used the HD client for Corsair and 2 small clients for mules. Yet, only the HD client loaded from the folder with the new sound.wz froze and crashed. But this was the first time in forever since I soloed zak for months with identical setup (before sound.wz replacement). However, I did crash before in a guild Zak run with a similar freeze-crash fashion.
If there is a possible chance someone could abuse d/c'ing their connection to avoid an unfavorable death due to seduce, then I think maybe there should be a limitation for that too: If the character was seduced or dead at the moment of disconnection, it will be rewarped to town or a different map.
Bump!!! I've done all the band-aid fixes but the pros and cons of everything considered should be weighed more! This isn't fun for anyone legitimately playing with their friends on boss runs OR for someone to try to get what they need in order to succeed in the game. I made it to the end of one Zakum run with my client crashing right after! Then when on Horntail, my party got through 60% of the way done with the body before I crashed, CLIENT CRASHED AGAIN! I still don't have any pendants or book splits which would help me greatly in the game. I can't move forward with the game if this continues. Something needs to be done, this thread seems to have been around a long time and so has this issue.
If this is updated with our new #70 client. royals gonna be 10/10. honestly this has been asked from the community for a long long time, and will allow us to shine above other private servers, i’m sure this or something similar is possible. @Joong is it possible for us to hear alittle opinion on this?
Hi, we really have not forgotten about this idea, and it has been discussed several times internally. As much as I wanted to give a definitive answer and give closure to the topic, all I can say is: It might be possible, but it would require considerable collaboration with Karven, and at this point in time we have chosen to prioritise other functionality. Fortunately since Update 70 we have been seeing a smaller absolute number of reports of crashes, so we are hopeful that the situation has improved somewhat. As such, I can neither move the thread to Accepted nor Not Possible, but will just leave it as it is for now.
This is more a server thing than a client thing. Yes, I can fix some client crashes so that you won't experience those, but I can't do anything about lag or cat that pulls out the plug and allow you to get back into bossing - that's server sided. Maybe some day I can work on the server too, who knows
Honestly who cares if the DC was due to server-sided lag or your cat pulling the plug? If you DC for reasons beyond your control, it is soul-crushing. Possibly soul-crushing enough to make some people quit if it happens often enough. This is a game integrity issue and I'd hate to see it get denied because of some last-minute seduce target clownery that might or might not even happen.
Client crashes isn’t as much of an issue anymore compared to the GFX issues we had before. Problem DC due to, eg. unstable internet connection like the asia players had a week before, or simply your cat/dog/fish pulling the net wire out, wasting your daily CD/causing the run to fail. If anything, this is the most frusfrating thing that can happen in royals. Solution Waiting room to re-enter the boss fight, the indepth explaination is mentioned in original post. - I don’t know if it is even possible to implement this 3min waiting room, or is due to client limitations. If its miraculously possible, please consider implementing this.
I like this idea and what I like about it more is that the main mechanic in this solution was already implemented back in pre-BB GMS with the introduction of Dungeons to the game. I'm sure everyone remembers these dungeons, which are basically a time-limited unique maps that are generated exclusively for you and your party. Once you are in you cannot go out and return and no one else is able to enter after the map has already been generated. The same concept can be implemented here in which the Waiting Room is acting as a dungeon and is generated upon logging back in as long as the expedition is still on-going. So in short, if it is possible to introduce dungeons to Mapleroyals it is also possible to implement the said waiting room.
Actually there's even a simpler solution for now with no new mechanics needed at all! Just add a new isolated map to every major boss expedition and make that map as the default return map after DCing or finishing the expedition (Like the Win\Lose maps in Monster Carnival). The said map will have a single NPC with two dialogue options: 1. Return back to the expedition (as long as the expedition is still on going). 2. Exit to the original default exiting map. The NPC will also present the remaining time that is left in which returning back to the expedition is possible (the 3 minutes counter) and how many times you have warped already back to the raid (the maximum amount of warps can be 1 or 2). Another option is to have a global warp counter which is shared with all raid members, for example there can be a total of 3 warps per raid for all the expedition members. Now for the timer, I'm not sure how time counters in MS works and what are the limitations but these are some options in which it can work: 1. The counter starts as soon as any member enters the map and it ticks as long as there are members presents in the waiting room (not sure if it is possible). 2. The counter starts as soon as any member enters the map and starts ticking regardless of members presence in the map. This means that there's a 3 minutes window in which members are able to warp back that starts as soon as the first member enter the waiting room. In these two cases the 3 minutes counter is shared by all the expedition members but in the second option probably only one member would be able to warp back after dc. A concept for such dialogue: A concept for the waiting room: (Took the picture from a guide on the forum) This can be implemented even today since all the mechanics are already presented in the game, and since boss expeditions are unique for each channel (two Zakum expeditions cannot occur on the same channel for example) the waiting room is inherently unique to each expedition, thus there's no problem of overlapping between different raids. So in conclusion: * Add a unique map to each boss and make that map the default exit map. * Add an NPC to that map that can either warp back or take you out to the original default exit map . The NPC tracks the time remaining and number of warps available. * The time counter can be unique to each expedition member or shared with all the members. * The number of warps available can be unique to each member of shared with all the members. * Once the counter reaches zero or there are no more warps available members cannot warp back to the boss fight.
this has all been thrown out before, because its the best measure, the problem is, it could be exploited by people who are trying to avoid damage or death in some situations like in sed, or a potion hotkey needs replaced, or a pet potion runs out and needs to be changed, or to just afk and return safely, like for mules etc. if it can be exploited, it will. the morality of hacking doesn't prevent it. but it also doesn't mean the entire concept has to be trashed, just work around it, don't half ass it because of demand and give people an exploitable save state
Bump After another dc with the 77.1 update, any progress about this idea? Chris @Zancks / Nut @nutleafcity will love to hear your input.
Would love to see something like this implemented. I have been unable to join boss runs during the last 3 months due to frequent lag and DC.