test
11-20-2008, 04:39 PM
Summary:
Crashing to desktop (CTD) may lead that player's instance progress to become out of sync with the group they are in. This makes the player unable to join the rest of his or her party and the rest of the party usually cannot continue without that player. The only thing the players can do is stop and wait for the lockout to expire. Unfortunately this becomes unreasonable when lockouts span longer than a couple days.
Scenario:
A group member crashes during a boss fight or directly after inside an instance of either Inevitable City dungeons with lengthy lockouts (Bilerot, Blood Wrought Enclave) or Lost Vale.
Problem:
That group member is rolled back (as in, loads the last successful character save on the server that was prior to the boss being killed) and does not match the current progress of the group and can no longer zone back into the instance with the group he/she started with.
Why can't the group member join us:
Particularly, this group member's progress shows that the boss that was killed with the group is still alive in their 'instance' or whatever you want to call it. Note: This cannot be fixed with /partyresetinstance the same error continues.
How does this effect us:
Everyone has to stop, we cannot continue any of these dungeons with 5 people, nobody else can join us unless they crashed at the exact same point, which in general NEVER HAPPENS. The group member that was rolled back faces the same problem. In the two Inevitable City instances, this means we have to wait 3 days without actually progressing in the dungeon before we can try again. In Lost Vale we have to WAIT A WEEK.
How CSR could help in this scenario:
1. Reset every group member's lockout timer and the the group can restart.
2. Bypass the 'does not match current progress' and insert our group member back into the instance with the rest of the group.
3. Allow the group member to zone into the instance with CSR, and have CSR slay the boss that should have been registered dead. This will allow that member's progress to resynchronize with the group.
When talking to CSR we offered several ways to fix this problem. Their response was they can't do anything and we would have to wait out the lockout period and submit a bug report.
The real question does CSR actually have the ability to do any of these 3 suggestions. And if not, maybe the developers of the game can design a way of resyncing a player back up with its group when this happens.
I am not sure how mythic queues their bug fixes, but I would like to bring this to the attention of the developing team so it may one day get resolved. (Hopefully sooner than later)
Crashing to desktop (CTD) may lead that player's instance progress to become out of sync with the group they are in. This makes the player unable to join the rest of his or her party and the rest of the party usually cannot continue without that player. The only thing the players can do is stop and wait for the lockout to expire. Unfortunately this becomes unreasonable when lockouts span longer than a couple days.
Scenario:
A group member crashes during a boss fight or directly after inside an instance of either Inevitable City dungeons with lengthy lockouts (Bilerot, Blood Wrought Enclave) or Lost Vale.
Problem:
That group member is rolled back (as in, loads the last successful character save on the server that was prior to the boss being killed) and does not match the current progress of the group and can no longer zone back into the instance with the group he/she started with.
Why can't the group member join us:
Particularly, this group member's progress shows that the boss that was killed with the group is still alive in their 'instance' or whatever you want to call it. Note: This cannot be fixed with /partyresetinstance the same error continues.
How does this effect us:
Everyone has to stop, we cannot continue any of these dungeons with 5 people, nobody else can join us unless they crashed at the exact same point, which in general NEVER HAPPENS. The group member that was rolled back faces the same problem. In the two Inevitable City instances, this means we have to wait 3 days without actually progressing in the dungeon before we can try again. In Lost Vale we have to WAIT A WEEK.
How CSR could help in this scenario:
1. Reset every group member's lockout timer and the the group can restart.
2. Bypass the 'does not match current progress' and insert our group member back into the instance with the rest of the group.
3. Allow the group member to zone into the instance with CSR, and have CSR slay the boss that should have been registered dead. This will allow that member's progress to resynchronize with the group.
When talking to CSR we offered several ways to fix this problem. Their response was they can't do anything and we would have to wait out the lockout period and submit a bug report.
The real question does CSR actually have the ability to do any of these 3 suggestions. And if not, maybe the developers of the game can design a way of resyncing a player back up with its group when this happens.
I am not sure how mythic queues their bug fixes, but I would like to bring this to the attention of the developing team so it may one day get resolved. (Hopefully sooner than later)