Explosion flame_range now defaults to light range instead of zero (#27184)

* Explosion flame_range now defaults to light range instead of zero

* Flash range defaults to devastation range
This commit is contained in:
Cyberboss
2017-05-13 07:43:08 -06:00
committed by duncathan salt
parent 7a0f5ca831
commit d8fc923f57
+6 -1
View File
@@ -1,10 +1,15 @@
/proc/explosion(turf/epicenter, devastation_range, heavy_impact_range, light_impact_range, flash_range, adminlog = 1, ignorecap = 0, flame_range = 0 ,silent = 0, smoke = 1)
/proc/explosion(turf/epicenter, devastation_range, heavy_impact_range, light_impact_range, flash_range, adminlog = 1, ignorecap = 0, flame_range, silent = 0, smoke = 1)
set waitfor = 0
src = null //so we don't abort once src is deleted
epicenter = get_turf(epicenter)
if(!epicenter)
return
if(isnull(flame_range))
flame_range = light_impact_range
if(isnull(flash_range))
flash_range = devastation_range
// Archive the uncapped explosion for the doppler array
var/orig_dev_range = devastation_range
var/orig_heavy_range = heavy_impact_range