I am the easy layers lib from BYOND to make cliffs more realstic, so you can walk on the top, but not hop from the button to the top. It works great.
But monsters, can still pass right through the turfs, and I think its because they can still move diagilonal. Is there a way to stop this?
ID:168312
Nov 6 2005, 12:13 am
|
|
In response to Artemio
|
|
I always doubtet client though.. Would client affect mobs too? :|
|
In response to Artemio
|
|
That wont work for normal mobs, they are still walking diagilonal
|
In response to Shades
|
|
Works fine for me.
|
In response to Artemio
|
|
Well it dosent for me. Thats why I posted it.
|
In response to Shades
|
|
I believe it wont, I am talking abotu mobs besides players. In the help file it says..
client var (mob) See also: client Default value: null This is a reference to a set of properties specific to the player. Therefore non-player mobs (NPCs) do not have a client (client = null). Setting a mob's client connects that player's client to the mob. So it would go without saying, any client commands wouldnt work on those NPCs. |
In response to Shades
|
|
F1 in dreammaker:
Move proc (moveable atom) |
In response to Mysame
|
|
Thanks for that referance, but Ive already looked into that, i thought Move() was for moving mobs from one spot to another.
Then I noticed the help file says that it is called every time a mob moves. But how would I apply that to the mob? |
In response to Shades
|
|
mob Try that |
In response to Shinichi Kudo
|
|
Well after looking through the Easy Layers source, it turns out, they did it a kind of lazy way..
What they did was make it so turfs had limits for N,S,E,W and then they locked out diagilonal movement by client movement. So I went and I also added it in, so turfs had limits for all the diagilonal movement instead of just locking the client diagilonal movement and it works fine now. |
Etc.