atom/movable proc, returns the turf the mob is on, after you go down the loc tree of atoms in atoms in atoms.
same for get_area() as well
ID:2115918
 Jul 14 2016, 5:47 am
|
|||||||
| |||||||
|
Jul 14 2016, 6:06 am
|
|
PJB3005
 |
I don't think this is needed that much. It can already be done very quickly by doing get_step(atom, 0).
|
http://www.byond.com/forum/?post=2110095
It *can* be done with get_step(Ref, 0), but it's not as fast as it could be. | |
What would be the difference between this and directly getting mob.loc?
| |
mob.loc would be another atom/movable if the mob is in an atom/movable
get_turf(mob) would be the turf the atom is eventually on, eg if mob is in A, A is in B, and B is on turf T, get_turf(mob) == T | |
I thought this might be the case (even more-so after re-reading the OP).
I'm kinda skeptical on this, I think, since an object contained inside another technically has no turf loc. Wouldn't hurt I guess, but I'm impartial as to whether a majority would ever need something like this. | |
I would like get_area() specifically since I tend to use it semi-frequently.
get_turf() I don't have any particular use for but it seems like it's something that could be quite useful. | |
bump
| |
This would be nice to have given how often it's performed.
| |
Bump as this would probably be simple to implement and could give a nice performance boost to many games.
| |