projectile

This file is not good Fucked up var names lie ahead Caution, traveler

General cleanup todo: Go through undocumented math and document it Remove bad vars, fill in gaps then created Deduplicate info between this and proj_data

Vars
angle	Angle of this shot. For reference @see setup()
armor_ignored	Does this projectile pierce armor?
called_target	Target for called shots behavior - by default does not affect projectile behaviour
called_target_turf	Turf of the called_target during projectile initialization
collide_with_other_projectiles	Below stuff but also this is dumb and only used for frost bats and I don't even know why it's used there. TODO remove
crossing	The list of precalculated turfs this projectile will try to cross, along with the tick count(?) when each turf should be crossed. The structure of this list is pure Byond demon magic: it's an indexed list of key-value pairs that can be accessed like: `var/turf/T = crossed[i]` OR `var/value = crossed[T]` where `T` is a turf in the list and `value` is the aforesaid tick count. a thousand year curse on whoever thought this was a good idea, and Lummox for enabling them.
curr_t	For precalculated projectiles, how far along the `crossing` list have we reached
data	Arbitrary projectile data. Currently only used to hold an object that a projectile is seeking for a singular type. TODO remove
facing_dir	Default dir, set to in do_step()
goes_through_mobs	Whether this projectile can freely pass through mobs
goes_through_walls	Whether this projectile can freely pass through dense turfs
has_atmosphere	Simulate standard atmos for any mobs inside
has_died	For disabling collision when a projectile has died but hasn't been disposed yet, e.g. under on_end effects
hitlist	List of atoms collided with this tick
impact_x	X position of the projectile impact, used for particles and bullet impacts
impact_y	y position of the projectile impact, used for particles and bullet impacts
implanted	What kind of implant this projectile leaves in impacted mobs
incidence	Reflection normal on the current tile (NORTH if projectile came from the north, etc.) TODO can maybe be replaced with a single dir check when relevant? not 100% sure why we need to track this always. Might be crucial, dunno
initial_power	TODO this var also feels dumb. convert to initial() prolly (on data not on this)
is_processing	Yeah this sucks. TODO remove. I don't care bring the bug back so we can actually fix it
max_range	Maximum range this projectile can travel before impacting a (non-dense) turf
mob_shooter	Mob-typed copy of `shooter` var to save time on casts later
orig_turf	Original turf this projectiles was fired from
pierces_left	Number of impassable atoms this projectile can pierce. Decremented on pierce. Can probably be axed in favor of the component. TODO remove
power	One of the two below vars needs to be renamed or removed. Fucking confusing I don't know why this var is here it just stores the result of a proc called on the proj data. TODO revisit
proj_data	Projectile data; almost all specific projectile information and functionality lives here
reflectcount	Number of times this projectile has been reflected off of things. Used to cap reflections
shooter	The mob/thing that fired this projectile
special_data	Bullshit var for storing special data for niche cases. Sucks, is probably necessary nonetheless
spread	Degree of spread this projectile was fired with. Note that this informational, and doesn't affect the projectile's trajectory
targets	List of all targets this projectile can go after; useful for homing projectiles and the like
ticks_until_can_hit_mob	Tracks the number of steps before a piercing projectile is allowed to hit a mob after hitting another one. Scarcely used. TODO remove?
travelled	Number of tiles this projectile has travelled
was_pointblank	Whether this projectile was shot point-blank style (clicking an adjacent mob). Adjusts the log entry accordingly
was_setup	TODO axe this after testing. Used very infrequently, looks redundant
wx	Offset within a tile, separate to pixel_x/y due to animation things probably?
xo	x component of the projectile's direction vector. EAST is positive, WEST is negative.
yo	y component of the projectile's direction vector. NORTH is positive, SOUTH is negative.

Var Details

var
angle
–

Angle of this shot. For reference @see setup()

var
armor_ignored
–

Does this projectile pierce armor?

var
called_target
– /atom

Target for called shots behavior - by default does not affect projectile behaviour

var
called_target_turf
– /turf

Turf of the called_target during projectile initialization

var
collide_with_other_projectiles
–

Below stuff but also this is dumb and only used for frost bats and I don't even know why it's used there. TODO remove

var
crossing
– /list

The list of precalculated turfs this projectile will try to cross, along with the tick count(?) when each turf should be crossed. The structure of this list is pure Byond demon magic: it's an indexed list of key-value pairs that can be accessed like: var/turf/T = crossed[i] OR var/value = crossed[T] where T is a turf in the list and value is the aforesaid tick count. a thousand year curse on whoever thought this was a good idea, and Lummox for enabling them.

var
curr_t
–

For precalculated projectiles, how far along the crossing list have we reached

var
data
–

Arbitrary projectile data. Currently only used to hold an object that a projectile is seeking for a singular type. TODO remove

var
facing_dir
–

Default dir, set to in do_step()

var
goes_through_mobs
–

Whether this projectile can freely pass through mobs

var
goes_through_walls
–

Whether this projectile can freely pass through dense turfs

var
has_atmosphere
–

Simulate standard atmos for any mobs inside

var
has_died
–

For disabling collision when a projectile has died but hasn't been disposed yet, e.g. under on_end effects

var
hitlist
– /list

List of atoms collided with this tick

var
impact_x
–

X position of the projectile impact, used for particles and bullet impacts

var
impact_y
–

y position of the projectile impact, used for particles and bullet impacts

var
implanted
–

What kind of implant this projectile leaves in impacted mobs

var
incidence
–

Reflection normal on the current tile (NORTH if projectile came from the north, etc.) TODO can maybe be replaced with a single dir check when relevant? not 100% sure why we need to track this always. Might be crucial, dunno

var
initial_power
–

TODO this var also feels dumb. convert to initial() prolly (on data not on this)

var
is_processing
–

Yeah this sucks. TODO remove. I don't care bring the bug back so we can actually fix it

var
max_range
–

Maximum range this projectile can travel before impacting a (non-dense) turf

var
mob_shooter
– /mob

Mob-typed copy of shooter var to save time on casts later

var
orig_turf
– /turf

Original turf this projectiles was fired from

var
pierces_left
–

Number of impassable atoms this projectile can pierce. Decremented on pierce. Can probably be axed in favor of the component. TODO remove

var
power
–

One of the two below vars needs to be renamed or removed. Fucking confusing I don't know why this var is here it just stores the result of a proc called on the proj data. TODO revisit

var
proj_data
– /datum/projectile

Projectile data; almost all specific projectile information and functionality lives here

var
reflectcount
–

Number of times this projectile has been reflected off of things. Used to cap reflections

var
shooter
– /atom

The mob/thing that fired this projectile

var
special_data
– /list

Bullshit var for storing special data for niche cases. Sucks, is probably necessary nonetheless

var
spread
–

Degree of spread this projectile was fired with. Note that this informational, and doesn't affect the projectile's trajectory

var
targets
– /list

List of all targets this projectile can go after; useful for homing projectiles and the like

var
ticks_until_can_hit_mob
–

Tracks the number of steps before a piercing projectile is allowed to hit a mob after hitting another one. Scarcely used. TODO remove?

var
travelled
–

Number of tiles this projectile has travelled

var
was_pointblank
–

Whether this projectile was shot point-blank style (clicking an adjacent mob). Adjusts the log entry accordingly

var
was_setup
–

TODO axe this after testing. Used very infrequently, looks redundant

var
wx
–

Offset within a tile, separate to pixel_x/y due to animation things probably?

var
xo
–

x component of the projectile's direction vector. EAST is positive, WEST is negative.

var
yo
–

y component of the projectile's direction vector. NORTH is positive, SOUTH is negative.

projectile /obj/projectile

Vars

Var Details

var angle –

var armor_ignored –

var called_target – /atom

var called_target_turf – /turf

var collide_with_other_projectiles –

var crossing – /list

var curr_t –

var data –

var facing_dir –

var goes_through_mobs –

var goes_through_walls –

var has_atmosphere –

var has_died –

var hitlist – /list

var impact_x –

var impact_y –

var implanted –

var incidence –

var initial_power –

var is_processing –

var max_range –

var mob_shooter – /mob

var orig_turf – /turf

var pierces_left –

var power –

var proj_data – /datum/projectile

var reflectcount –

var shooter – /atom

var special_data – /list

var spread –

var targets – /list

var ticks_until_can_hit_mob –

var travelled –

var was_pointblank –

var was_setup –

var wx –

var xo –

var yo –