Casting Position Bug

I'm not able to reproduce...

whats your client date kyeme

Ind, on 17 May 2013 - 17:38, said:

whats your client date kyeme

2012-04-10

All clients can reproduce this.

Actually I am able to reproduce this, but it seems to only work sometimes, on self-casting skills and when you're moving between the first or second cells.

Feels more like a position fixing tho. Doesnt seem to occur once you've walked 3 cells or more. And it also happens randomly.

Update: Lemme correct myself, it can happen if you walk more than 3 cells, but it really feels a lot like a fixing position issue more than an actual bug.
I guess the biggest bug would be to make the character move to the next cell instead of the previous and make it stop once it hits that cell (Rather than flash-teletransport them to the previous cell)

Edited by Xgear, 18 May 2013 - 02:44 AM.

it looks like the client moves the character faster than the server, when you cast a skill the server makes the char stop walking and tells the client to lock the char in the cell (the cell the server thinks it is in) thats why that happens...i think.

Quote

it looks like the client moves the character faster than the server, when you cast a skill the server makes the char stop walking and tells the client to lock the char in the cell (the cell the server thinks it is in) thats why that happens...i think.

same theory....in aegis its in the other way it teleports you to the new destination..however its random specially in lag situations...

I have also reproduced this. Is there a way for it to be fixed via server?

Confirmed?

Edited by kyeme, 29 May 2013 - 05:32 AM.

	if(ud->walkpath.path_pos>=ud->walkpath.path_len)
		i = -1;
	else if(ud->walkpath.path[ud->walkpath.path_pos]&1)
		i = status_get_speed(bl)*14/10;
	else
		i = status_get_speed(bl);
	if( i > 0)
		ud->walktimer = add_timer(gettick()+i,unit_walktoxy_timer,bl->id,i);

its likely the status_get_speed(); thing doesnt match the client value, I'm not entirely sure (but confirming the issue exists)

Do you mean we have wrong constant?

here is the problem

if(!ud->state.running) //need TK_RUN or WUGDASH handler to be done before that, see bugreport:6026
  unit_stop_walking(src,1);// eventhough this is not how official works but this will do the trick. bugreport:6829

however by disabling this fix new problem exist instead of going back like the first problem it snaps to a new destination just reverse of the other one..

here is how official works
[035F]PACKET_CZ_REQUEST_MOVE2 - player click to a new position then cast
[0087]PACKET_ZC_NOTIFY_PLAYERMOVE - sever immediately issue this to notify the client that tells "oops your casting a skill so I cut your request up to this point.."
and using skill and cast follows [0113]PACKET_CZ_USE_SKILL, [07FB]PACKET_ZC_USESKILL_ACK2

Up~

bump~ I need this fix.

bump~ (

Mine is working properly. I am using 2013 client

sevenzz23, on 29 Sept 2013 - 04:45, said:

Mine is working properly. I am using 2013 client

Im using 2013 too and the bug is still there

Hello i also have this problem is there any way to fix this?

Edited by Cyrax, 18 November 2013 - 09:32 AM.

Working Great rev. 13263 Renewal Client..

sevenzz23, on 18 Nov 2013 - 12:37, said:

Working Great rev. 13263 Renewal Client..

Aww

Bumping~