OldSchoolKO - ERAGON Reborns! JUNE THE 5TH (official) - Miami 13:00 hours

[dark_warrior_13]

Still waiting on the destruction/goblin armor fix..

[SheldonCooper]

Server's real fun

[razor]

Archer is so underpowered right now 1v1, I hope people won't complain on saturday.

[perhana]

I just wish someone could tell me how to fix my basic attack, my basic r-attack does not work at all!

It just says: " cannot attack because the target is too far".
My character runs to the enemy and starts attacking on my screen, but only animation works, no damage. For others it just shows that im standing near the enemy.

Anyone know what might cause this? I tried with every class, but it does not work!

So basically animation and everything works on my client, but nothing goes through to the server.

Any tips & advice is appreciated

[twostars]

I just wish someone could tell me how to fix my basic attack, my basic r-attack does not work at all!

It just says: " cannot attack because the target is too far".
My character runs to the enemy and starts attacking on my screen, but only animation works, no damage. For others it just shows that im standing near the enemy.

Anyone know what might cause this? I tried with every class, but it does not work!

So basically animation and everything works on my client, but nothing goes through to the server.

Any tips & advice is appreciated

Sounds more like a problem with their movement system than anything on your end. It's really easy for the server to consider you at the position of the last movement update -- not the current one. It relaying the packets from the client so clients see you where you should be, but not actually handling them correctly easily explains why others see you in the correct place. At least, if they were near you when they received the update -- if they weren't in range of you, and they then proceeded to entered your range -- you not having moved since -- they'd most likely see you in the old position. Not something that you'd expect to try in reality, but yeah.

[ilterates]

Sounds more like a problem with their movement system than anything on your end. It's really easy for the server to consider you at the position of the last movement update -- not the current one. It relaying the packets from the client so clients see you where you should be, but not actually handling them correctly easily explains why others see you in the correct place. At least, if they were near you when they received the update -- if they weren't in range of you, and they then proceeded to entered your range -- you not having moved since -- they'd most likely see you in the old position. Not something that you'd expect to try in reality, but yeah.

Let me dumb this down a bit.. Says on your chart, you are fucked up. Server's acting like a fag and your shit is all retarded.

[Kallop]

Sounds more like a problem with their movement system than anything on your end. It's really easy for the server to consider you at the position of the last movement update -- not the current one. It relaying the packets from the client so clients see you where you should be, but not actually handling them correctly easily explains why others see you in the correct place. At least, if they were near you when they received the update -- if they weren't in range of you, and they then proceeded to entered your range -- you not having moved since -- they'd most likely see you in the old position. Not something that you'd expect to try in reality, but yeah.

Since not that many people seem to have this issue I suppose it could be a bug with a specific weapon? I remember seeing such a bug occur when bugged Krowaz weaponry was being used in other servers.

[twostars]

Since not that many people seem to have this issue I suppose it could be a bug with a specific weapon? I remember seeing such a bug occur when bugged Krowaz weaponry was being used in other servers.

True, it could also be the weapon delay/range, but he did say it was throwing an out of range error which I'm pretty sure (but not completely) only happens when you're out of movement range (i.e. not really specific to the weapon). When the weapon range/delay is screwed up, usually it doesn't even error (and if it does, it usually just says it missed).

Edit:
But the client will throw that error when the range isn't large enough client-side (server-side it'll just do nothing). I'm not sure why they'd have messed with client-side ranges though, but it's definitely a possibility.
And yes, I rarely consider the client -- it should never be the client.

[perhana]

Some spesifics on my r-attack problem:

I can find a place near the enemy where it does not say "cannot attack too far..." It starts the attack animation and keeps whacking the enemy (I just cannot make any damage and others do not see me attacking).
And if I start the attack far it runs to the target and starts the attack animation (it says cannot attack too far in the beginning, but it still runs to target and starts animation).

I tried warrior, priest & rogue and same errror, so it cannot be a spesific weapon.

[BlackOak]

Since not that many people seem to have this issue I suppose it could be a bug with a specific weapon? I remember seeing such a bug occur when bugged Krowaz weaponry was being used in other servers.

Yup, like this dude said. On some krowaz weapons, u cant just target Z R for the R to work, ya got to get closer to your opponent for the R part to work in combo, pretty much on top of the mob

[perhana]

Yup, like this dude said. On some krowaz weapons, u cant just target Z R for the R to work, ya got to get closer to your opponent for the R part to work in combo, pretty much on top of the mob

I can get it to start attacking when close (animation) but it still does NOT do anything serverside.. there is no more closer to go to!

[stimpy]

Open Bifrost/FT/Chaos we need events,keep it active and more people will join,bdw is cewl but aint that great. Moar events !

[Professor]

Castle Siege War coming next week

[MyNameIs]

Downloading

[tobol]

how much is class change scroll?