Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #005124

  • 3 - Medium

  • Fixed

Issue Confirmations

  • Yes (3)No (0)
Photo

eye of hellion quest

Posted by Hercules Bot on 17 December 2011 - 05:25 PM

Originally posted by shadow.sk
I have the same problem here:

http://www.eathena.w...er&showbug=5098

Originally posted by calciumkid
Confirmed to be an issue.

I'm unsure as to why it occurs however. Anyone else have any ideas? I've fiddled with it a bit.

Originally posted by shadow.sk
havent fixed it? thanks

Originally posted by Slim
This user seems to have the same problem, I already tested it myself and it worked fine O_o
http://rathena.org/b...eye-of-hellion/

Originally posted by Mercurial
I can also confirm this, unfortunately I haven't been able to fix it O_O,

my guess that it is a packet problem maybe? or a source problem? this is a bit alarming though,

Originally posted by Mercurial
<Slim> you saw the script already?
<Slim> I tested it and it worked just fine, but apparently it bugs for some people
*** JayPee_ has joined #RAthena
<Mercurial|Ae2rAScripts> o
<Mercurial|Ae2rAScripts> what client are you using
<Mercurial|Ae2rAScripts> the date
<Slim> I believe it was 2010-07-07

Originally posted by Aleos
Try changing the NPC ID from 139 to 111 and see how that works out for you.

Originally posted by Xantara
What Aleos said worked. But I wonder why ID#139 is buggy. =s
Tested on 2011-06-09a.

Originally posted by Mercurial
Confirmed, changing the NPC id to 111 works.

Originally posted by Aleos
You can see the differences here on Ai4rei's website. The little [i] tags will give you a description of the NPC. 139 does not trigger the client which is why the input box was not coming up.