Verus NPC - Healer Miyo bug - Renewal Technical Support / Bug Reporting - WarpPortal Community Forums

Jump to content


Photo
- - - - -

Verus NPC - Healer Miyo bug


  • Please log in to reply
7 replies to this topic

#1 Vhaaaan

Vhaaaan

    Amateur Blogger

  • Members
  • 451 posts
  • LocationPhilippines
  • Playing:Ragnarok Online
  • Server:Chaos

Posted 13 December 2018 - 08:22 PM

Problem: you get disconnected when choosing "4,000 z". This shouldn't be an option.

 

unknown.png

 

unknown.png


  • 0

#2 VModCinnamon

VModCinnamon

    Tranquility

  • VMod Retired
  • 16663 posts
  • Playing:Ragnarok Online

Posted 13 December 2018 - 09:02 PM

What.. why >_< I thought this was fixed some time ago.

 

Vhaaaan, did the option work fine for you before?


  • 0

#3 Vhaaaan

Vhaaaan

    Amateur Blogger

  • Members
  • 451 posts
  • LocationPhilippines
  • Playing:Ragnarok Online
  • Server:Chaos

Posted 13 December 2018 - 09:05 PM

It's my first time talking to the NPC, I can't tell.


  • 0

#4 VModCinnamon

VModCinnamon

    Tranquility

  • VMod Retired
  • 16663 posts
  • Playing:Ragnarok Online

Posted 13 December 2018 - 09:06 PM

Thank you, I will create a ticket to have the NPC checked :)


  • 0

#5 canon019

canon019

    Amateur Blogger

  • Members
  • 343 posts
  • Playing:Ragnarok Online

Posted 13 December 2018 - 09:50 PM

The truth is there isn't second option it's only HP/SP full recovery and it cost 4000 z


  • 0

#6 VModCinnamon

VModCinnamon

    Tranquility

  • VMod Retired
  • 16663 posts
  • Playing:Ragnarok Online

Posted 14 February 2019 - 02:49 PM

Applied a fix for the NPC, please check post maintenance Feb 14th.


  • 0

#7 Vhaaaan

Vhaaaan

    Amateur Blogger

  • Members
  • 451 posts
  • LocationPhilippines
  • Playing:Ragnarok Online
  • Server:Chaos

Posted 21 June 2019 - 06:40 PM

Hello, tried the NPC again and still bugged.


  • 0

#8 VModCinnamon

VModCinnamon

    Tranquility

  • VMod Retired
  • 16663 posts
  • Playing:Ragnarok Online

Posted 16 July 2019 - 10:37 AM

Update:
Getting this fixed, ETA is next weekly maintenance.

Apparently, when significant updates happen the fix get rolled back.


  • 1




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users