• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.

Triggers

Flashlight Test v1.w3x
Variables
Unimportant stuff
Init
Camera
Flashlight Triggers
--- About ---
--- Changelog ---
Flashlight Globals
Flashlight Loop
Explanation of light points
Enter map-specific custom script code below. This text will be included in the map script after variables are declared and before any trigger code.
Name Type is_array initial_value
flashlight_blackmask boolean No
flashlight_length real No
flashlight_lightpoints integer No
flashlight_size real No
temp_group group No
temp_loc location Yes
Unimportant stuff. Just remember to set time of day to night for macimum effetct.
Init
Events
Map initialization
Conditions
Actions
Game - Set the time of day to 18.00
Game - Set time of day speed to 0.00 % of the default speed
Unimportant stuff.
Camera
Events
Time - Every 0.50 seconds of game time
Conditions
Actions
Camera - Set Player 1 (Red) 's camera Distance to target to 2000.00 over 0.00 seconds
-- Info --
This spell will simply apply a flashlight-like cone visibility effect to a unit with the "Flashlight" spell.
The spell should work fine with any number of players and units (The spell should be MUI, although i haven't actually tested it.)


-- Importing --
You need to import these variables into your map:
flashlight_length
flashlight_size
flashlight_lightpoints
flashlight_blackmask
And if you don't already have some temporary variables, these as well:
temp_group
temp_loc

You also need the Flashlight spell and buff (if you don't want to make a system for it yourself.)

And of course the triggers:
Flashlight Globals (Not directly needed)
Flashlight Loop


-- Known bugs --
Setting the variable "flashlight_blackmask to True, will break standard Warcraft 3 visibility behaviour (A units standard visibility radius.)
Version 1:
Release
NOTE: If you are going to use black masks, remember to untick "Masked areas are partially visible" under "Map options", if you want everything to be black. (Please note that doing this will make doodads light up wierdly. Try for yourself.) This is not a bug per se, but an odd Warcraft 3 per behaviour
Flashlight Globals
Events
Map initialization
Conditions
Actions
-------- The length of the flashlight cone --------
Set Variable Set flashlight_length = "1000.00"
-------- ------------------------------ --------
-------- Final width of cone --------
Set Variable Set flashlight_size = "600.00"
-------- ------------------------------ --------
-------- Number of light sources in a cone --------
Set Variable Set flashlight_lightpoints = "10"
-------- ------------------------------ --------
-------- Wether or not black mask should be used --------
-------- Remember to untick "Masked areas are partially visible" under "Map options", if you want everything to be black --------
-------- BUG: Setting this option to True, will break standard Warcraft 3 visibility behaviour --------
Set Variable Set flashlight_blackmask = "true"
NOTE: Flashlights have a habbit of flickering if the Pereodic Event is less than 0.01 seconds.
Flashlight Loop
Events
Time - Every 0.01 seconds of game time
Conditions
Actions
-------- If flashlight_blackmask is on, make sure every player actually has black mask --------
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
If - Conditions
flashlight_blackmask Equal to True
Then - Actions
-------- Make sure that everything is black for all players --------
Player Group - Pick every player in (All players controlled by a User player) and do (Actions)
Loop - Actions
Visibility - Create an initially Enabled visibility modifier for (Picked player) emitting Black mask across (Entire map)
Visibility - Destroy (Last created visibility modifier)
Else - Actions
-------- - --------
-------- Every unit with flashlight buff --------
Set Variable Set temp_group = (Units in (Entire map) matching (((Matching unit) has buff War Drums) Equal to True))
Unit Group - Pick every unit in temp_group and do (Actions)
Loop - Actions
Set Variable Set temp_loc[0] = (Position of (Picked unit))
-------- - --------
-------- If flashlight_blackmask is set to True, these functions are needed for the picked unit --------
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
If - Conditions
flashlight_blackmask Equal to True
Then - Actions
-------- UNIT'S VISIBILITY RADIUS (It needs to be somewhere around 400 for movement to work properly) --------
Visibility - Create an initially Enabled visibility modifier for (Owner of (Picked unit)) emitting Visibility from temp_loc[0] to a radius of 385.00 .
Visibility - Destroy (Last created visibility modifier)
Else - Actions
-------- - --------
-------- This loop creates a line of light source points, each with greater radius --------
For each (Integer A) from 1 to flashlight_lightpoints , do (Actions)
Loop - Actions
-------- Angle = Facing of picked unit --------
-------- Offset = (flashlight_length / flashlight_lightpoints) x Integer_A --------
Set Variable Set temp_loc[(Integer A)] = (temp_loc[0] offset by ((flashlight_length / (Real(flashlight_lightpoints))) x (Real((Integer A)))) towards (Facing of (Picked unit)) degrees.)
Set Variable Set temp_loc[(Integer A)] = (temp_loc[0] offset by ((flashlight_length / (Real(flashlight_lightpoints))) x (Real((Integer A)))) towards (Facing of (Picked unit)) degrees.)
-------- - --------
-------- Radius = (flashlight_size / flashlight_lightpoints) x Integer_A --------
Visibility - Create an initially Enabled visibility modifier for (Owner of (Picked unit)) emitting Visibility from temp_loc[(Integer A)] to a radius of ((flashlight_size / (Real(flashlight_lightpoints))) x (Real((Integer A)))) .
Visibility - Destroy (Last created visibility modifier)
-------- - --------
Custom script: call RemoveLocation( udg_temp_loc[GetForLoopIndexA()] )
Custom script: call RemoveLocation( udg_temp_loc[0] )
Custom script: call DestroyGroup( udg_temp_group )
The way a cone works (for my flashlight at least), is by making a lot
of points along a line.
Like this:

[U]  O  O  O  O  O

Where [U] is the unit and O is a light point.



Each of these points have a visibility radius, increasing each step.

               /
            / ///
         / ///////
 ///  / ///////////
/[U]//O//O//O//O////
 ///  / ///////////
         / ///////
            / ///
               /

Yea, something like that. (The "/" demonstrates visible terrain.)



So by increasing the number of light points, you can (theoretically)
achieve a greater resolution of the light cone.

Also, if you increase the maximum distance of the flashlight, you must
also increase the number of light points, or it might just look like
a bunch of circles in front of your unit.
Top