Several bugs to report.

[subignition]

Some of these are reposts; I'm doing it for the formatting

Skill targeting range
[B]Description: Certain melee skills when combined with the Auto-Attack action will not fire.
Hypothesis: Error in Auto-Attack's estimation of attack distance from target.
Reproduction: As a Cleric, wielding either weapon, use Auto-Attack on a Goblin Captain or Sand Mushroom. Then, while attacking the monster, attempt to use Bash.
Prevalence: Affects many monsters, including the above-- an example of an unaffected monster is the Werebear Fighter
Workaround: Move closer to the monster manually.

Monster position reporting
[B]Description: Loss of sync between client and server's reporting of monster's position causes "out of casting range" error.
Hypothesis: Client incorrectly interpreting monster movement vectors
Reproduction: Attempt to attack a 'runaway' monster with a melee weapon, such as a Prock.
Prevalence: Affects monsters who have ranged attacks, and most monsters who periodically run a few meters away from the player during melee combat
Workaround: Move closer to the monster manually.

Standing dead players
[B]Description: Occasionally dead non-client players will appear to be standing with zero health. They cannot be resurrected, and attempts to do so incite an "Incorrect target" error.
Hypothesis: Player characters that take lethal damage while appearing to be out of range of the attack causing their death causes the bug in every viewing client
Reproduction: In the Lost Mini Dragon KQ, the dragon's jumping attack frequently causes this bug
Prevalence: The KQ in question becomes much more difficult with party members unable to be revived. Unnecessarily wasted hearts. Unknown if bug appears outside KQs.
Workaround: Move out of range of affected players. Their status will be correctly updated when re-sent by server. -Daevor

Map loading failure
[B]Description: Client freezes at 'now loading' screen.
Hypothesis: unknown
Reproduction: unknown; bug seems random, though personally I experience it most trying to go from Collapsed Prison to Goblin Camp.
Workaround: Exit and reopen client.

Will update as more bugs become known. Thanks.
Withstanding, Apoline

[lalawillow]

Map loading failure
[B]Description: Client freezes at 'now loading' screen.
Hypothesis: unknown
Reproduction: unknown; bug seems random, though personally I experience it most trying to go from Collapsed Prison to Goblin Camp.
Workaround: Exit and reopen client.

Will update as more bugs become known. Thanks.
Withstanding, Apoline

I often experience this when i use return scrolls. Never when i use portals.

[subignition]

I've personally never seen it happen with a return scroll, so I'll still call it fairly random.

[Daevor]

Standing dead players
Description: Occasionally dead non-client players will appear to be standing with zero health. They cannot be resurrected, and attempts to do so incite an "Incorrect target" error.
Hypothesis: Player characters that take lethal damage while appearing to be out of range of the attack causing their death causes the bug in every viewing client
Reproduction: In the Lost Mini Dragon KQ, the dragon's jumping attack frequently causes this bug
Prevalence: The KQ in question becomes much more difficult with party members unable to be revived. Unnecessarily wasted hearts. Unknown if bug appears outside KQs.
Workaround: None known. Affected players can only be resurrected by a character whose client did not experience the error (which due to the inaccuracy of positioning across clients may be several.)


Workaround: Cleric needs to move away from the dead player far enough so that when said cleric returns, the information is resent from the server. Cleric will then see dead player "falling down" when dead player comes in to sight of cleric, and cleric will be able to revive dead player.




[Bug] Map loading failure
[B]Description: Client freezes at 'now loading' screen.
Hypothesis: unknown
Reproduction: unknown; bug seems random, though personally I experience it most trying to go from Collapsed Prison to Goblin Camp.
Workaround: Exit and reopen client.


I experience the map loading failure on all my chars in Eld. Either the client spontaneously closes down when all but the "G" is highlighted on the "Now Loading" screen, or it freezes. When it freezes, CPU usage is about 90%, and memory usage is a little 742MB. I can successfully log in to chars in Uruga.

EDIT: Okay, rebooting my PC solved the Eldy loading screen issue

[ghoffman9]

I have the casting range glitch. I tried relogging several times but to no avail. It is like I am stuck with this glitch. If someone knows another way besides relogging to fix this glitch, please let me know.

[subignition]

You can't fix that because it's not a glitch, it's a side-effect of the patch.

I know why it's happening, too.

[allyyCORE]

yeah, it's a really annoying bug especially when you find that out while AOE'ing magmatons in Burning Rock.

The work-around is a temporary alternative for now but it is a huge inconvenience.

[cantheal]

Some of these are reposts; I'm doing it for the formatting

Skill targeting range
[B]Description: Certain melee skills when combined with the Auto-Attack action will not fire.
Hypothesis: Error in Auto-Attack's estimation of attack distance from target.
Reproduction: As a Cleric, wielding either weapon, use Auto-Attack on a Goblin Captain or Sand Mushroom. Then, while attacking the monster, attempt to use Bash.
Prevalence: Affects many monsters, including the above-- an example of an unaffected monster is the Werebear Fighter
Workaround: Move closer to the monster manually.

Monster position reporting
[B]Description: Loss of sync between client and server's reporting of monster's position causes "out of casting range" error.
Hypothesis: Client incorrectly interpreting monster movement vectors
Reproduction: Attempt to attack a 'runaway' monster with a melee weapon, such as a Prock.
Prevalence: Affects monsters who have ranged attacks, and most monsters who periodically run a few meters away from the player during melee combat
Workaround: Move closer to the monster manually.

Standing dead players
[B]Description: Occasionally dead non-client players will appear to be standing with zero health. They cannot be resurrected, and attempts to do so incite an "Incorrect target" error.
Hypothesis: Player characters that take lethal damage while appearing to be out of range of the attack causing their death causes the bug in every viewing client
Reproduction: In the Lost Mini Dragon KQ, the dragon's jumping attack frequently causes this bug
Prevalence: The KQ in question becomes much more difficult with party members unable to be revived. Unnecessarily wasted hearts. Unknown if bug appears outside KQs.
Workaround: Move out of range of affected players. Their status will be correctly updated when re-sent by server. -Daevor

Map loading failure
[B]Description: Client freezes at 'now loading' screen.
Hypothesis: unknown
Reproduction: unknown; bug seems random, though personally I experience it most trying to go from Collapsed Prison to Goblin Camp.
Workaround: Exit and reopen client.

Will update as more bugs become known. Thanks.
Withstanding, Apoline

Bravo on the post!! Those are some of the things that I tried putting a ticket in for, as of now, there are no good responses. If they provide any additional information, I will post.

I think map loading failure and other bugs might be caused by server overload. Freezing on the loading screen might be caused by drop packets, if they set their priority level of zoning from different maps lower than those whose on the map (which is possible). [Saying it might be server overload because of the frequent lag we get on some servers]

Also, dead person standing, also occurs very frequently in pvp kq. This doesn't cause as much issues as MD, but it does become very annoying for those who are trying to attack the person.

Casting out of range issue also occurs in pvp kq, there are no way to get around it. Pretty much if you get caught with it, you are out of luck and the person is already running away from your stun.

[fetishaxx]

[Bug] Standing dead players
Description: Occasionally dead non-client players will appear to be standing with zero health. They cannot be resurrected, and attempts to do so incite an "Incorrect target" error.
Hypothesis: Player characters that take lethal damage while appearing to be out of range of the attack causing their death causes the bug in every viewing client
Reproduction: In the Lost Mini Dragon KQ, the dragon's jumping attack frequently causes this bug
Prevalence: The KQ in question becomes much more difficult with party members unable to be revived. Unnecessarily wasted hearts. Unknown if bug appears outside KQs.
Workaround: Move out of range of affected players. Their status will be correctly updated when re-sent by server. -Daevor



happens outside of kq's.
ive had people ask for revs in sea of greed and sand hill with this problem.
at least it'll be a little easier knowing i can do something other then loging out and then back in every time it happens just so i can revive :|.