Et bug just like hazy bug - Renewal Technical Support / Bug Reporting - WarpPortal Community Forums

Jump to content


Photo
- - - - -

Et bug just like hazy bug


  • Please log in to reply
2 replies to this topic

#1 KriticalAssassin

KriticalAssassin

    They pay me to post.

  • RO Fungineering
  • 9313 posts
  • LocationBehind you?
  • Playing:Ragnarok Online
  • Server:Chaos- Renewal

Posted 20 January 2013 - 03:57 PM

Getting the "Reservation is cancelled" crap for ET just like it was with hazy. Not bothering to ticket in because I reported the same thing with hazy over 7 months ago and each time I get "It's been fixed" it's not fixed. Anyone else still having these problems? Or find anyway that seems to fix it.

After 45 minutes of repeatedly trying it works. Maybe this has to do with too many instances on the server at 1 time?

Edited by KriticalAssassin, 20 January 2013 - 03:59 PM.

  • 0

#2 DrAzzy

DrAzzy

    Really Azzy? Already?

  • VMod Retired
  • 15606 posts
  • LocationNew England
  • Playing:Ragnarok Online
  • Server:Chaos-Clandestine Society

Posted 20 January 2013 - 04:13 PM

Not bothering to ticket in


Okay, so you don't want it to get fixed?

Please submit a ticket to the GM team. They are the only ones who can fix this.
  • 0

#3 KriticalAssassin

KriticalAssassin

    They pay me to post.

  • RO Fungineering
  • 9313 posts
  • LocationBehind you?
  • Playing:Ragnarok Online
  • Server:Chaos- Renewal

Posted 21 January 2013 - 06:13 AM

Okay, so you don't want it to get fixed?

Please submit a ticket to the GM team. They are the only ones who can fix this.

because I reported the same thing with hazy over 7 months ago and each time I get "It's been fixed" it's not fixed.

Side note: That ticket has been re-opened like 20 times. Each time no solution. It tends to fix itself certain days of the week. Responses have always been the same from "It's been fixed" when it hasn't to "Try again". So yeah. i'm just following their "Try again" method now. It's the only one that has ever really worked... eventually. I'm just gong to assume that it gets caused due to there being too many instances open across the server at one time.
  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users