Forum Discussion

kello_511's avatar
6 years ago

Stop Scheduling Events on Weekends

Devs:
You have proven over and over again that it’s a terrible idea to have events introduced in weekends since they are incapable of working as intended. Now that has clearly already to TW and GA.

Since we know that no event can ever be proven to run smoothly again, and that we will consistently have to “wait until Monday” for fixes, can we not just stop pretending to be surprised by this and only have these things during the week?

It’s beyond frustrating to see the entire event ruined because of this. Guilds who are focused on tw are usually eager to start, and literally at least half of our guild was affected by this. And on top of that, there have been clear inconsistencies in scoring now which changes the entire scope of the event.
  • "Bulldog1205;c-1860362" wrote:
    "X3ina;c-1860346" wrote:
    "Bulldog1205;c-1860323" wrote:
    Its as fixed as it can get. Having the full dev staff there wouldn’t change anything. It’s not possible to go back and undo this. They simply said they will evaluate the “damage” and determine if compensation is warranted. If it was Tuesday instead of Saturday the only thing that might be different is we could get compensation sooner.



    Cough *fixed* cough


    Not sure what you are trying to say. There are multiple WAI reasons this can happen.


    This

    C3PO or a HY on the other team could easily lead to this. Server issues need not apply.
  • "ChristophIV;c-1860373" wrote:
    "leef;c-1860348" wrote:
    "X3ina;c-1860346" wrote:
    "Bulldog1205;c-1860323" wrote:
    Its as fixed as it can get. Having the full dev staff there wouldn’t change anything. It’s not possible to go back and undo this. They simply said they will evaluate the “damage” and determine if compensation is warranted. If it was Tuesday instead of Saturday the only thing that might be different is we could get compensation sooner.



    Cough *fixed* cough


    IPD could explain that screenshot.


    How? It can't self destruct if it's the last character standing can it? Not being a ****, genuinely interested in what I've missed.


    i don't know tbh, but there had to be 2 characters of which IPD blew up the other leaving hermit on the battle field unable to retreat.
  • "Kyno;c-1860371" wrote:
    "kello_511;c-1860329" wrote:
    "Bulldog1205;c-1860323" wrote:
    Its as fixed as it can get. Having the full dev staff there wouldn’t change anything. It’s not possible to go back and undo this. They simply said they will evaluate the “damage” and determine if compensation is warranted. If it was Tuesday instead of Saturday the only thing that might be different is we could get compensation sooner.


    It’s not possible?
    But the dev post says that they are going to review the effect it had on the players and decide from there.
    It seems pretty clear that they are able to determine what’s impact their latest bug had on the players, and if this was a normal day they could probably correct the scoring issues pretty quickly.

    I do recall some past scoring issues being addressed mid-event before.

    Like I said, I like events on weekends too. But that is overshadowed when those same events consistently can’t run properly (even on the 85th iteration).


    I think you misunderstood what they meam.

    They are going to look at how wide the effect was and what the end result is for the majority effected.

    They will not nor have they ever adjusted scores or any other event data due to an issue.

    Also from what this looked like it was a "connection issue", which means to them, the data is lost, it never made it back to the server. It is doughtful they could determine a loss from a missed connection due to this issue with the data on hand.


    So if there is absolutely no information available, how are they going to determine how “wide the effect was”?

    And there was definitely an event, I think it was an early tw, where points were not scored correctly for battles that were won (shocking, I know). And as I recall they did fix it before the event was over.