I was doing the Dyson Battlezone this evening. When the final phase started, I was disconnected. After logging in again, I was put in a random instance. When trying to switch back to the instance I was earlier in, I couldn't because it was full.
Which means I got no rewards even though I had helped conquering a large part of the Battlezone, and this is the second time it happens. Could it be made possible to put people back in the same instance after they were disconnected? It's kind of annoying to do all the work and get no rewards because you were thrown out of the game and you can't change back to the instance you were in earlier because it is suddenly full or something.
(The same happened to me a few times in the Cute Space Elite btw: being active the entire mission, but a few seconds after the carrier spawns, I get disconnected. By the time I'm back in the game, the mission is finished and I get no rewards even though you were there for the better part of the mission. This is unfair and should be solved.)
I don't foresee them having an interest to leave spots open in zones for a "just in case" a person comes back. You dropping off that instance leaves an opening for someone who is coming in to be placed there.
I don't foresee them having an interest to leave spots open in zones for a "just in case" a person comes back. You dropping off that instance leaves an opening for someone who is coming in to be placed there.
They could make it such that someone who just enters the battlezone isn't placed in a zone that's almost finished/in its final phase. That's not fair anyway. Such a simple change would mean that the spot stays open for those players that were in that instance before.
Indeed, that would be the primary reaching I cannot foresee them implementing such a system. It would potentially create problems with populated maps near the end trying to capture, for what effectively is a minor issue of someone getting the occasional disconnect.
Bull. What's unfair is to punish the players that had one or more people vanish with no explanation or promise of return.
It's not your fellow players fault you got DC'd.
And this horrible idea of yours could easily be used to grief legitimate players by disgruntled leavers and AFKers who'd disconnect and laugh at how they left people in the lurch with no way to get replacements.
/unsigned
One way to resolve that issue is to set a timer on that spot. At least 10 seconds on that spot. The leavers or AFkers won't be coming back so that spot would be free after 10 seconds so that other players can join.
I have disconnected so many times during the boss stage and lose my spot. I have been there from start to end. I'm after the final reward. When I get disconnected I re-log with-in seconds.
Now, when I re-log I end up in an instance where the map is completely red. You can imagine the frustration after all the effort is lost and plus I get no reward. There has to be some kind of solution for this. The same occurs in the Undine Battlezone.
I can understand the OP's frustrations, but their suggestion could actually result in griefing of other players and even abuse of such a system...
Jump in, kill a few things, ALT+F4 and go away while other people finish the STF/battle zone for you, log back in and collect your reward with no effort applied...
This situation is frustrating and I've had it happen myself, but the truth of the matter is, if you're getting regular disconnects (as the OP seems to be from what they stated) I'd be looking at resolving your disconnections before asking Cryptic to 'fix' anything regarding the rewards...
Instead of trying to juggle instances like this, I think that the server should be able to remember whether or not you had made enough contribution to be eligible for the end-of-mission reward, and then simply give you the reward when the other players finish (or when you log back in if they finished while you were trying to reconnect). I too hate the bit about having to be connected at the very second that rewards are passed out--sometimes the disconnect happens with literally seconds before the mission is finished, meaning that the 10-30 minutes of doing the mission is wasted, plus the cooldown time until I can try again.
Note that I am not saying that players should get the reward for just shooting things for a minute or so and then dropping out. The missions would each have some threshold to determine just how much damage/healing you have to do in order to be eligible (a threshold low enough that the average player who completes the mission normally would definitely have met it, but high enough that you have to be actually trying instead of malingering). If you get disconnected 20% of the way through the mission, then too bad for you, you'll have to start over. But if you get disconnected 70% or more of the way through the mission, and have been fighting hard all of the way, then you should be getting something for it.
I beg your pardon? You should perhaps go and look at who first responded to this 'long dead thread'...
Admittedly, I never actually looked at the original posting date - I merely responded, after the poster before me resurrected this thread which (once again, I did not realise) was 3 months old...
If you're gonna troll, at least troll the right person...
It would be a simple fix. If a disconnect happens no logout script is logged. This is one reason the script for logging out is so important. I don't think it should be that hard to put a hold on your spot if no logout was scripted. Although I don't think it is worth Cryptics time for such a small and random event. Although I would love to see them do it to prevent pvpers from logging to prevent a death. If a logout script is logged during a PvP it should count as a death and the player should not be able to come back into that match and a 24 hours ban from PvP queues. But that is a different subject.
Comments
They could make it such that someone who just enters the battlezone isn't placed in a zone that's almost finished/in its final phase. That's not fair anyway. Such a simple change would mean that the spot stays open for those players that were in that instance before.
One way to resolve that issue is to set a timer on that spot. At least 10 seconds on that spot. The leavers or AFkers won't be coming back so that spot would be free after 10 seconds so that other players can join.
I have disconnected so many times during the boss stage and lose my spot. I have been there from start to end. I'm after the final reward. When I get disconnected I re-log with-in seconds.
Now, when I re-log I end up in an instance where the map is completely red. You can imagine the frustration after all the effort is lost and plus I get no reward. There has to be some kind of solution for this. The same occurs in the Undine Battlezone.
Jump in, kill a few things, ALT+F4 and go away while other people finish the STF/battle zone for you, log back in and collect your reward with no effort applied...
This situation is frustrating and I've had it happen myself, but the truth of the matter is, if you're getting regular disconnects (as the OP seems to be from what they stated) I'd be looking at resolving your disconnections before asking Cryptic to 'fix' anything regarding the rewards...
Note that I am not saying that players should get the reward for just shooting things for a minute or so and then dropping out. The missions would each have some threshold to determine just how much damage/healing you have to do in order to be eligible (a threshold low enough that the average player who completes the mission normally would definitely have met it, but high enough that you have to be actually trying instead of malingering). If you get disconnected 20% of the way through the mission, then too bad for you, you'll have to start over. But if you get disconnected 70% or more of the way through the mission, and have been fighting hard all of the way, then you should be getting something for it.
/10c.
Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
I beg your pardon? You should perhaps go and look at who first responded to this 'long dead thread'...
Admittedly, I never actually looked at the original posting date - I merely responded, after the poster before me resurrected this thread which (once again, I did not realise) was 3 months old...
If you're gonna troll, at least troll the right person...