usr.loc

BYOND Forums

Announcements · BYOND Help · Bug Reports · Feature Requests · Beta Testers · Beta Bugs · Developer Help · Design Philosophy · Demos & Libraries · Tutorials & Snippets · Art & Sound · Classified Ads · Game Updates · Contests & Events · Linux Talk · On Topic · Off Topic

usr.loc

ID:263220 Jul 15 2006, 10:32 am
Hiro the Dragon King	usr.loc = locate(usr.x+1,usr.y,usr.z) When I use this he walks to the space next to him...why? If I use usr.x+2 he teleports there. Why can't he teleport to the space next to him?

Jul 15 2006, 10:37 am

Loduwijk

Whenever anything is relocated to a space only 1 tile away, animated movement kicks in no matter how it got there. If it's more than 1 tile away, animated movement is ignored. That's just the way it works, and there is no way to change that short of disabling animated movement altogether.

atom/movable has a variable animate_movement that you can disable. However, last I knew you could only change this at compile-time, not at runtime mid-game.

And I also have a tip for you. get_step will get the space next to you much easier. get_step(usr, EAST) will return the same thing as locate(usr.x+1, usr.y, usr.z)

Jul 15 2006, 10:48 am In response to Loduwijk
Hiro the Dragon King	I'm trying to entirely rewrite the movement proc for a project I'm working on. So, disabling the animation for movement wouldn't be a bad thing as long as rewrite it with something like a flick proc in there right?

Jul 15 2006, 11:09 am In response to Loduwijk
Mysame	Loduwijk wrote: atom/movable has a variable animate_movement that you can disable. However, last I knew you could only change this at compile-time, not at runtime mid-game. You can change it at runtime. :<

Jul 15 2006, 12:02 pm In response to Mysame
Mechanios	.configure animation 1 or 0 I think. I have no idea how you would manipulate this , though.

Jul 15 2006, 5:27 pm In response to Mysame
Loduwijk	Wonderful. Once upon a time we couldn't, and we had asked for it to be able to be changed at runtime, but I was not aware that this had been fixed. (edit) At least, I think so... Maybe it was pixel_step_size that we couldn't change at runtime. Whatever it was, one of those movement variables for movable atoms was compiletime only.

Jul 15 2006, 5:30 pm In response to Hiro the Dragon King
Loduwijk	Sure, you could do that. Remember though, this will stop you from sliding smoothly between tiles even for normal movement as you are walking around the map.

Jul 15 2006, 7:12 pm In response to Loduwijk
Hiead	Loduwijk wrote: At least, I think so... 'Twas this one. I wasn't even aware of the fix. Hiead

Jul 15 2006, 7:35 pm In response to Hiead
Nadrew	I'm still not sure changing it actually works; I remember the bug being that if you changed it nothing happened, not that it wouldn't allow it.