Problem? with An Icy Keep

Discussion in 'General Gameplay Discussion' started by Tekka, Dec 13, 2017.

  1. Tekka Well-Known Member

    Did you intend to put a lock out timer on the repeatable Frostfell instances - The Icy Keep (Easy) and The Icy Keep (Hard)?

    If not, you did - please fix.

    If so, why?

    Edit: If you have done the (Hard) version of the instance, the (Easy) version gives you the 'This instance will expire in 0.0 seconds. This instance has expired.' message, then kicks you out.
  2. Gninja Developer

    It was a mistake, we will get it fixed asap
    Faelynn, Xillean, Siren and 4 others like this.
  3. Tekka Well-Known Member

    Thanks Gninja! The decorators salute you! :D

    /salute
  4. Grouse Active Member

    FYI -- Tonight Tobrin's Former Domain was also set to expire in 0.0 seconds.
    Was taking an ALT through An Eye for Power and hit that dead end.
  5. Moonpanther Well-Known Member

    thanks!!
  6. Greene Active Member

    Gnomes don't make mistakes. Only slight miscalculations!
    Xillean and Siren like this.
  7. Nella Member

    Since the lockout timer being added to Icey Keep was a mistake ...why wasn't it reverted to how it was before? There is still a lockout, but instead of 90 min, was changed to 5 min (with the 3 day maximum duration). Why not just put it back how it was with no lockout?

    -Nella
  8. Mermut Well-Known Member

    Because they changed ALL zones to be resettable instances rather then lock-out timers. It was a universal change with an unintended consequence for Icy Keep.
    Pixistik and Tekka like this.
  9. Pixistik Don't like it? You're not alone!

    If there is one thing this dev team loves, its easy universal changes!
  10. Tekka Well-Known Member

    To be fair, in this instance I don't think it is a matter of slapping on an easy fix. There are probably sets of code that instances belong to, and in this case Icy Keep belonged to a set of code that was changed with an unintended consequence for the holiday dungeons. Since the code set probably can't be changed, the timer was reduced to a minimal amount - 5 minutes. Which essentially just adds a click or two, not sure it's even possible to run the instance in under 5 minutes.
    Faelynn likes this.
  11. Faelynn Active Member

    Speaking as a dev for something completely different from this - I think you speak truth of all devs, not just DB ;)

    EDIT: Elaborating a bit further: anytime you can accomplish something in a "universal" (or "across the board") manner, that goes a long ways in terms of preserving one's own sanity in maintaining it!
  12. Faelynn Active Member

    Agree. Given the universal change they had applied (eliminating the old "lockout" style in favor of making things Peristent), and certainly not wanting to have to muck with that any further - changing this one to a 5 minute timer sounds like the most no-nonsense solution to appease the masses, with as minimal risk of negative consequences as possible.