can_pass_info ![code/__HELPERS/paths/path.dm 271](git.png)
Holds all information about what an atom can move through Passed into CanAStarPass to provide context for a pathing attempt
Also used to check if using a cached path_map is safe There are some vars here that are unused. They exist to cover cases where requester_ref is used They're the properties of requester_ref used in those cases. It's kinda annoying, but there's some proc chains we can't convert to this datum
Vars | |
access | What access we have, airlocks, windoors, etc |
---|---|
anchored | Are we anchored |
buckled_info | If our mob is buckled to something, what's it like |
camera_type | Cameras have a lot of BS can_z_move overrides Let's avoid this |
can_ventcrawl | Can we ventcrawl? |
has_gravity | Do we have gravity |
incapacitated | Is our mob incapacitated |
incorporeal_move | Is our mob incorporeal |
is_bot | Are we a bot? |
is_living | Are we a living mob? |
is_observer | Are we a ghost? (they have effectively unique pathfinding) |
mob_size | What is the size of our mob |
movement_type | What sort of movement do we have. Mirrors /atom/movable/movement_type |
no_id | If we have no id, public airlocks are walls |
pass_flags | What we can pass through. Mirrors /atom/movable/pass_flags |
pulling_info | Pass information for the object we are pulling, if any |
requester_ref | Weakref to the requester used to generate this info Should not use this almost ever, it's for context and to allow for proc chains that Require a movable |
rider_info | If our mob has a rider, what does it look like |
thrown | Are we being thrown? |
Var Details
access ![code/__HELPERS/paths/path.dm 278](git.png)
What access we have, airlocks, windoors, etc
anchored ![code/__HELPERS/paths/path.dm 284](git.png)
Are we anchored
buckled_info ![code/__HELPERS/paths/path.dm 303](git.png)
If our mob is buckled to something, what's it like
camera_type ![code/__HELPERS/paths/path.dm 312](git.png)
Cameras have a lot of BS can_z_move overrides Let's avoid this
can_ventcrawl ![code/__HELPERS/paths/path.dm 293](git.png)
Can we ventcrawl?
has_gravity ![code/__HELPERS/paths/path.dm 306](git.png)
Do we have gravity
incapacitated ![code/__HELPERS/paths/path.dm 297](git.png)
Is our mob incapacitated
incorporeal_move ![code/__HELPERS/paths/path.dm 299](git.png)
Is our mob incorporeal
is_bot ![code/__HELPERS/paths/path.dm 291](git.png)
Are we a bot?
is_living ![code/__HELPERS/paths/path.dm 289](git.png)
Are we a living mob?
is_observer ![code/__HELPERS/paths/path.dm 287](git.png)
Are we a ghost? (they have effectively unique pathfinding)
mob_size ![code/__HELPERS/paths/path.dm 295](git.png)
What is the size of our mob
movement_type ![code/__HELPERS/paths/path.dm 280](git.png)
What sort of movement do we have. Mirrors /atom/movable/movement_type
no_id ![code/__HELPERS/paths/path.dm 273](git.png)
If we have no id, public airlocks are walls
pass_flags ![code/__HELPERS/paths/path.dm 276](git.png)
What we can pass through. Mirrors /atom/movable/pass_flags
pulling_info ![code/__HELPERS/paths/path.dm 308](git.png)
Pass information for the object we are pulling, if any
requester_ref ![code/__HELPERS/paths/path.dm 317](git.png)
Weakref to the requester used to generate this info Should not use this almost ever, it's for context and to allow for proc chains that Require a movable
rider_info ![code/__HELPERS/paths/path.dm 301](git.png)
If our mob has a rider, what does it look like
thrown ![code/__HELPERS/paths/path.dm 282](git.png)
Are we being thrown?