Leaderboard

Patch Notes: Changes to the new Cursed bounty hunter You will now receive an extra cursed emblem upgrade if your opponent was also risking a cursed blood orb! There is now a 10 minute cooldown before receiving the same cursed BH target again, only in non-edgeville wilderness There's unfortunately been players secretively farming in deep wild locations, ruining the fun for everybody else. If you ever witness players farming kills and/or bounty hunter, please report them to the staff team! Note: When we say "non-edgeville", we mean any area outside of the general PK spots at ::home Addressed issues / confusion with the new AGS special scroll The AGS spec scroll was never meant to make the standard AGS appear or perform as well as the AGS (or) This scroll is intended to simply make both the AGS and AGS (or) perform better in terms of accuracy and hit frequency, respective to their type For this reason, along with general confusion about the "+3 max hit" effect, the described bonuses have been modified: Removed bounty hunter at the risk fight arena due to BH farmers Fixed issues with Dark korasi sword's max hit cap being higher than intended Fixed issues with Dark korasi sword's protection value Fixed issues with the DWH and DWH (or) special attack max hits and functionality Fixed issues with the Dragon halberd (or) Fixed an issue where the Limitbreak berserker pet allowed you to hit at your weapon's damage cap even if your gear didn't have it as a max hit. For example, if the damage cap for an AGS spec is 80 but with your gear you only had a max hit of 70, you still had potential to hit an 80! This will reduce the unfair amount of OP hits people were getting with this pet while equipping low/mid tier gear. If you're using this pet with equipment that already brings you to the max hit cap of your weapon, then nothing has changed in terms of power. This is a fix, not a nerf.

This is not your computer fault. This is unknown issue that has been reported to me when that first happened to many players randomly. Unfortunately when that happens client throws NullPointerException and I have no idea how, why, from what, where and client source code is obfuscated so it's a pain to read it.