Home The Bridge

Event Discussion: Continuing Mission - 2024-01-18

24

Comments

  • @STT Community I could have easily been well under 1500 if not for the issues caused by the error messages and the slow gameplay. Gameplay was so slow all morning that battles were taking twice as long as they should have. Captains who could have reached 1500, 750, or the other thresholds weren't able to do so because of these issues.
  • DScottHewittDScottHewitt ✭✭✭✭✭
    Greetings Captains, the team has been informed and they are working on the server issue atm. LLAP

    Are they working on the people who were knocked out of a copy of the Legendary?!?!?


    Greetings Captain, Would you mind elaborating so I can provide detailed feedback to the team? Thank you in advance. LLAPS

    The game was acting up for over an hour and a half right at the end of an Event?

    I moved up 2000+ Ranks this morning despite that. A few hundred more Ranks is far from impossible. IF I had not had to deal with constant problems. I was literally in the middle of a Skirmish, and had Intel left for more, when the Event ended.

    Sorry to be frustrated. But, this is far from the first time there have been issues at the start, the end, or both, in an Event.
    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • DScottHewittDScottHewitt ✭✭✭✭✭
    @STT Community I could have easily been well under 1500 if not for the issues caused by the error messages and the slow gameplay. Gameplay was so slow all morning that battles were taking twice as long as they should have. Captains who could have reached 1500, 750, or the other thresholds weren't able to do so because of these issues.

    Almost every Battle, when I could play, I got the "Hailing Starfleet" hang up after the Battle before the Reward would start loading, then again while the Reward was loading. At least ten seconds each time. That's an extra ~20 seconds per Battle.
    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • @STT Community I could have easily been well under 1500 if not for the issues caused by the error messages and the slow gameplay. Gameplay was so slow all morning that battles were taking twice as long as they should have. Captains who could have reached 1500, 750, or the other thresholds weren't able to do so because of these issues.

    Almost every Battle, when I could play, I got the "Hailing Starfleet" hang up after the Battle before the Reward would start loading, then again while the Reward was loading. At least ten seconds each time. That's an extra ~20 seconds per Battle.

    I experienced the same "hailing Starfleet" issue. In the past when there have been multiple issues in an event, the tiers for Legendary crew have been lowered to compensate for issues.
  • Kim_Novak.IIKim_Novak.II ✭✭✭✭✭
    I didn't reach under 30 because of all the f**k ups in the last 2 hours!
  • Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP
  • IceCatIceCat ✭✭✭✭✭
    edited January 23
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    I used to be a regular commenter, but went back to lurking because it was clear that a lot of our feedback was falling on deaf ears. This issue has frustrated me enough to log back in and speak up though.

    There really needs to be proper compensation given for this. A lot of us would have easily gotten top 1500, if not for all of the server issues. This is also far from the first time that we've experienced this kind of problem during the end of an event.

    Maab isn't even a great crew, but when you need to have him to complete the Convergence Day event/get copies of T'Pol, it is a particularly frustrating result due to continuous and repeated problems on your end.

    The fair thing to do would be to issue a copy of Maab to all. It isn't a gamebreaking crew, and certainly won't upset the balance, but it would go a long way to minimising player anger and would be good customer service.

    I hope the right thing is done.

    Edited to add screenshots

    wkeb4uxdwen4.jpg
    nc99p9f3nsfz.jpg
  • Sven LundgrenSven Lundgren ✭✭✭✭✭
    I got the phase has ended message on the first day of the event several times. There were issues the entire event.
  • DScottHewittDScottHewitt ✭✭✭✭✭
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.
    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • Greetings Captains, tomorrow we are meeting again with the team and I'll gather some information. Updates will follow, Thank you Captains. LLAP
  • ChaosChildChaosChild ✭✭✭✭✭
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?
  • ChaosChildChaosChild ✭✭✭✭✭
    All that being said, compensation is always cheaper than new hardware and it gives the (false) impression that you care about your customers. A bonus Maab for everyone in the top 2000 would work.
  • DScottHewittDScottHewitt ✭✭✭✭✭
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    There were problems throughout the Event. It just got worse towards the end.

    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • WebberoniWebberoni ✭✭✭✭✭
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    There were problems throughout the Event. It just got worse towards the end.

    If the game slowed down equally for everybody (I noticed it too, taking much longer every time a button was pressed over the last 60-90 minutes especially), then why would you or anybody else expect to be bumped up? A complete outage for only some players is one thing, but a slowdown impacting everybody really shouldn't have any bearing on rank, if nobody gained an advantage.
  • DScottHewittDScottHewitt ✭✭✭✭✭
    Webberoni wrote: »
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    There were problems throughout the Event. It just got worse towards the end.

    If the game slowed down equally for everybody (I noticed it too, taking much longer every time a button was pressed over the last 60-90 minutes especially), then why would you or anybody else expect to be bumped up? A complete outage for only some players is one thing, but a slowdown impacting everybody really shouldn't have any bearing on rank, if nobody gained an advantage.

    Because apparently some people had no problems, some had some problems, and some of us had major problems.

    But, congratulations to everyone. I don't even care any more.

    Y'all win.

    Yippee for everyone.

    It doesn't even matter.

    I'm just an idiot anyway.



    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • WebberoniWebberoni ✭✭✭✭✭
    edited January 23
    Webberoni wrote: »
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    There were problems throughout the Event. It just got worse towards the end.

    If the game slowed down equally for everybody (I noticed it too, taking much longer every time a button was pressed over the last 60-90 minutes especially), then why would you or anybody else expect to be bumped up? A complete outage for only some players is one thing, but a slowdown impacting everybody really shouldn't have any bearing on rank, if nobody gained an advantage.

    Because apparently some people had no problems, some had some problems, and some of us had major problems.

    But, congratulations to everyone. I don't even care any more.

    Y'all win.

    Yippee for everyone.

    It doesn't even matter.

    I'm just an idiot anyway.



    I'm not sure I deserve that sort of response. I faced a similar issue that you described, but thankfully I had built up a 300 place buffer to where I wanted to finish. It seems like a lot of people had that issue, so I was just sharing a different perspective IF that issue did actually impact everybody equally. I even left room for understanding if some players were impacted by other issues and/or a more significant delay.

    No need to go off the deep end. I certainly didn't suggest your frustration wasn't warranted or that you were an idiot.
  • DScottHewittDScottHewitt ✭✭✭✭✭
    Webberoni wrote: »
    Webberoni wrote: »
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    There were problems throughout the Event. It just got worse towards the end.

    If the game slowed down equally for everybody (I noticed it too, taking much longer every time a button was pressed over the last 60-90 minutes especially), then why would you or anybody else expect to be bumped up? A complete outage for only some players is one thing, but a slowdown impacting everybody really shouldn't have any bearing on rank, if nobody gained an advantage.

    Because apparently some people had no problems, some had some problems, and some of us had major problems.

    But, congratulations to everyone. I don't even care any more.

    Y'all win.

    Yippee for everyone.

    It doesn't even matter.

    I'm just an idiot anyway.



    I'm not sure I deserve that sort of response. I faced a similar issue that you described, but thankfully I had built up a 300 place buffer to where I wanted to finish. It seems like a lot of people had that issue, so I was just sharing a different perspective IF that issue did actually impact everybody equally. I even left room for understanding if some players were impacted by other issues and/or a more significant delay.

    No need to go off the deep end. I certainly didn't suggest your frustration wasn't warranted or that you were an idiot.

    I'm frustrated at the situation. Not at you.

    Apologies.
    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • IceCatIceCat ✭✭✭✭✭
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    Some of us are limited in our time available, especially in a long grind event, like a skirmish. We play when we can, which might mean having to wait until the last day to get points.

    I also never used to have a problem with doing a good chunk of my play the morning of the last day in the past. There have been times when I barely started until the final day due to time constraints without any problems.

    I've been a consistent top 1500 or better player for years using this strategy in skirmish and galaxy events. Never was an issue until recently with these server issues.

    Your attempt to blame the players who count on the last hours is misguided. The event runs for four days. Why should we be punished for using all of that time? 🤔
  • ChaosChildChaosChild ✭✭✭✭✭
    IceCat wrote: »
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    Some of us are limited in our time available, especially in a long grind event, like a skirmish. We play when we can, which might mean having to wait until the last day to get points.

    I also never used to have a problem with doing a good chunk of my play the morning of the last day in the past. There have been times when I barely started until the final day due to time constraints without any problems.

    I've been a consistent top 1500 or better player for years using this strategy in skirmish and galaxy events. Never was an issue until recently with these server issues.

    Your attempt to blame the players who count on the last hours is misguided. The event runs for four days. Why should we be punished for using all of that time? 🤔

    I wasn't blaming the players, the blame clearly lies with WRG and their inability/unwillingness to support this game properly. However, given that we all know how useless they are, you have to plan these things differently than back in the good old days when the whole game wasn't being run on a shoestring budget.

    Denying the reality of the situation isn't going to help anyone.
  • Greetings Captains, I'll make sure to pass your thoughts to the team. We really hope to fix this issue in order to avoid situations like this one. We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP
  • Kim_Novak.IIKim_Novak.II ✭✭✭✭✭
    Greetings Captains, I'll make sure to pass your thoughts to the team. We really hope to fix this issue in order to avoid situations like this one. We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP

    What's the latest on this?
    Any compensation
  • Kim_Novak.IIKim_Novak.II ✭✭✭✭✭
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    I didn't?
    If you are trying for T100+ you don't leave it just to the last day, or hour
    You are constantly at it
  • ChaosChildChaosChild ✭✭✭✭✭
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    I didn't?
    If you are trying for T100+ you don't leave it just to the last day, or hour
    You are constantly at it

    Then you're fine. You definitely got enough copies for the OE. Why are you complaining? Other than general complaints about WRG that is, but when have those ever got us anywhere?
  • Sulu's HusbandSulu's Husband ✭✭✭✭✭
    Greetings Captains, I'll make sure to pass your thoughts to the team. We really hope to fix this issue in order to avoid situations like this one. We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP

    What's the latest on this?
    Any compensation

    We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP
  • Kim_Novak.IIKim_Novak.II ✭✭✭✭✭
    edited January 25
    ChaosChild wrote: »
    ChaosChild wrote: »
    AviTrek wrote: »
    Greetings Captains, I understand your frustration. Tomorrow I'm meeting the team and I'll let them know about the inconvenience and Hopefully Ill manage to get some compensation, can't promise anything, but I will try. LLAP

    Instead of focusing on compensation can you talk to the team about how this happens every event and we all know it will happen. The team needs to deploy enough AWS instances to handle peak load at the end of an event. After months of issues, no one should be surprised about crashes at end.

    After months, they should have RESOLVED the issue.

    100% agree. BUT, if you're leaving it to the last minute to try to climb those vital places even though we all know about these issues, then you've really only got yourself to blame at this point.

    We all know WRG are useless, the servers can never cope with peak load and the game will stall/crash in the opening and closing phases of every single event. That's a given at this point, and while I'm sure Nancy will bring it up with the team tomorrow I have zero faith in anything actually changing. If it was going to improve it would have been sorted months ago.

    So, knowing that all this is going to happen, why would you leave it to the last minute to make up those vital places?

    I didn't?
    If you are trying for T100+ you don't leave it just to the last day, or hour
    You are constantly at it

    Then you're fine. You definitely got enough copies for the OE. Why are you complaining? Other than general complaints about WRG that is, but when have those ever got us anywhere?

    It's fine if you reach for a safe 100. But when you put all the extra chrons, time & effort to get to the top 30 & then for it to be taken away then it's not so fine

    And There was more to it than just getting copies for the OE
  • Greetings Captains, I'll make sure to pass your thoughts to the team. We really hope to fix this issue in order to avoid situations like this one. We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP

    What's the latest on this?
    Any compensation

    After meeting yesterday with the team, I brought up the issues you Captains have encountered. The devs are considering a compensation plan for upcoming scenarios like this as well as a possible compensation for the inconveniences created in this one too. As soon as I have the final word, I'll update you. LLAP
  • IceCatIceCat ✭✭✭✭✭
    Greetings Captains, I'll make sure to pass your thoughts to the team. We really hope to fix this issue in order to avoid situations like this one. We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP

    What's the latest on this?
    Any compensation

    After meeting yesterday with the team, I brought up the issues you Captains have encountered. The devs are considering a compensation plan for upcoming scenarios like this as well as a possible compensation for the inconveniences created in this one too. As soon as I have the final word, I'll update you. LLAP

    I hope the response from the devs will be better than the one I got from customer service. Which said, in part:

    The anomaly was detected and immediately resolved by the technical team and the game returned to its normal functionality.

    This is not only untrue (issues occurred throughout the event), but does not address the losses of players affected by these outages.

    Repeated negligence on upkeep of the game by WRG is bad enough. But lying to the players AND refusing to make players whole for what they lost out on through no fault of their own is unacceptable.

    At this point, if not for the fact I have a good fleet and would feel bad if I left them in a lurch, I'd probably have deleted the game a while ago. And I'm still getting closer to doing so regardless.
  • DScottHewittDScottHewitt ✭✭✭✭✭
    edited January 25
    Greetings Captains, I'll make sure to pass your thoughts to the team. We really hope to fix this issue in order to avoid situations like this one. We apologize for the inconvenience, and I'll try to get something for you Captains. LLAP

    What's the latest on this?
    Any compensation

    After meeting yesterday with the team, I brought up the issues you Captains have encountered. The devs are considering a compensation plan for upcoming scenarios like this as well as a possible compensation for the inconveniences created in this one too. As soon as I have the final word, I'll update you. LLAP

    No offense. But instead of planning compensation for "upcoming issues like this", why don't they address the problems causing the issues? Instead of waiting for it to happen again, they should be proactive so it doesn't happen again.

    Event after Event the normal response has been "The problem has been fixed and will not happen again." Then, the next Event it happens again. So, obviously it was not "fixed". This Event it was the worst it has been for quite some time for many of us. That response from the company feels less than reassuring about the next Event.


    And, as we often said to Shan, NO ONE is blaming you. All you can do is relay what the company says to relay. We know the response is not from you, and no one blames you for their response.


    EDIT: Typos.
    "The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
  • AviTrekAviTrek ✭✭✭✭✭
    They don't care. TP has said cut server costs. The issues are the result of those cut costs. But it's cheaper to give non-committal updates and be vague about compensation that doesn't happen than it is to fix the problem.
Sign In or Register to comment.