odd problem

[smokybarnable]

I have an odd problem that just started occurring recently. Whenever I walk the character never puts his foot down completely after stopping, and if I move one step he sort of glides.

[Kabal]

I get this occasionally and I just restart the client.

[smokybarnable]

Seems like it only happens after I use my razor macro for entering my locked house. Maybe I'm not giving it enough time to walk, seems to screw something up.

[Pirul]

Ahhhhh, I've had this happen with macros that involve walking. For some reason if you run a macro that includes walking your client will do that. Mine also "lag-jumps" me several tiles. I have to close my client all the way and open it back up.

I suggest not including walking in your macro, and just do the walking part manually.

[Chaos]

You can macro house entry without walking just make two simple macros one to use the key and target door .. then double click the door to open it then key again to to re lock it . then you just walk in and run second macro the close door and run detect hidden

[iamreallysquall]

Ahhhhh, I've had this happen with macros that involve walking. For some reason if you run a macro that includes walking your client will do that. Mine also "lag-jumps" me several tiles. I have to close my client all the way and open it back up.

I suggest not including walking in your macro, and just do the walking part manually.

^ exactly what i was going to say

[Sheer Luck]

Ahhhhh, I've had this happen with macros that involve walking. For some reason if you run a macro that includes walking your client will do that. Mine also "lag-jumps" me several tiles. I have to close my client all the way and open it back up.

I suggest not including walking in your macro, and just do the walking part manually.

An Corp ?


Moving chars in Razor Macros = Buggy Client.

I had a "Door Macro" when I started here. It would Unlock the door, move 2 steps north, lock the door, then Det Hidden. Not only would it screw-up the current client <No foot down, Unsync client, Lag> but also other instances of the client that were running. Only solution was to close All running clients.

Old, Known, Derrick confirmed, Razor Bug.