1. Discord Support team Facebook l2central.info

Labyrinth bug

Discussion in 'Game Bugs (Archive)' started by dimvision, Dec 15, 2011.

Thread Status:
Not open for further replies.
  1. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    today we tried labyrinth 69. the instance was only 20 minutes. yesterday it was 40 or 50 not sure. no way to finish it like that.
     
  2. NeCRo

    NeCRo User

    Joined:
    29.11.11
    Messages:
    8
    Likes Received:
    0
    i did it today worked perfectly
     
  3. Apophis

    Apophis User

    Joined:
    24.11.11
    Messages:
    1,044
    Likes Received:
    215
    didn't have any problem today also.
     
  4. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    ah well, well try it again today and well see.
     
  5. Kall

    Kall User

    Joined:
    24.11.11
    Messages:
    1,019
    Likes Received:
    1
    laba have 60 min limit.
    kama have 30 min limit.
    i don't have any problem either.
     
  6. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    we entered, killed second group of mobs and got last boss to 80% hp when we got ported out (got 5 min and 1 min warning before getting ported out). i still had 40 minutes left on my newbie buffs which i took just before we entered.
     
  7. Kall

    Kall User

    Joined:
    24.11.11
    Messages:
    1,019
    Likes Received:
    1
    i'll pass this to qa team to check (maybe this error occur only when you killed 2nd group)
     
  8. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    great!

    ps: we did 69 like that for 2 times before that already and we had no problem. one member of party did pailaka just before it, maybe it has something to do with that?
     
  9. Kall

    Kall User

    Joined:
    24.11.11
    Messages:
    1,019
    Likes Received:
    1
    let's try after maintance:
    /instancezone (for this one who did pailaka)
     
  10. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    i will tell him to do it when i see him online and i'll post the info.
     
  11. Kall

    Kall User

    Joined:
    24.11.11
    Messages:
    1,019
    Likes Received:
    1
    thanks.
    also i write a msg to my contact for qa.
     
  12. PatriotazX

    PatriotazX User

    Joined:
    08.03.10
    Messages:
    103
    Likes Received:
    0
    let me guess you entered , failed here after 30 minutes , then entered again and you were out of time? if so u have to know that instancezone closes after 10 minutes when noone is inside. after that you can reenter (not continue , but reenter) and have 60mins again
     
  13. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    no it happened on first try.
     
  14. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    he tried it just now: no instance zone under time limit.
     
  15. PatriotazX

    PatriotazX User

    Joined:
    08.03.10
    Messages:
    103
    Likes Received:
    0
    well maby thats happened right on time when kama/laba/daily q resets? (looks like 6:30 server time)
     
  16. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    it was around 7 pm server time. so not even close to instance reset time.
     
  17. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    today we had no problems.
     
  18. MrScubba

    MrScubba User

    Joined:
    03.12.11
    Messages:
    505
    Likes Received:
    75
    that happens if someone hits the escape device and enter again
    5 min timer will start and when over, bb
     
  19. dimvision

    dimvision User

    Joined:
    29.11.11
    Messages:
    97
    Likes Received:
    4
    yeah it could be, i think one of our members reentered.
     
Thread Status:
Not open for further replies.