Page 1 of 2 1 2 LastLast
Results 1 to 10 of 17

Thread: [Confirmed] Ezalor's Illuminate starting position is wrong

  1. #1
    Basic Member
    Join Date
    Dec 2011
    Posts
    11,187

    [Confirmed] Ezalor's Illuminate starting position is wrong

    E:
    Quote Originally Posted by imxtrabored View Post
    The Illuminate Lightning Orb effect is created 150 units in the direction of Illuminate's cast. The Illuminate dummy caster is created 50 units behind the Orb. The Illuminate spell cast is based on a Breath of Fire with 10 levels and a starting and ending radius of 350. The base spell means this spell regards target collision. Distance is 1200 and speed is 1050, 50-500 damage increasing by 50 every 0.5 seconds. Vision is granted by 350/350 vision flying dummies that are created ever 0.5 seconds at 150 distance intervals; the first is created on top of the Lightning Orb and they have 7 seconds timed life. The Lightning Orb and Illuminate Spirit have no vision. Cast range is 2000; targeting type: unit or point target.

    For reference, the Dota 2 data:
    Spoiler: 
    Code:
            // Casting
            //-------------------------------------------------------------------------------------------------------------
            "AbilityCastRange"                "1800"
            "AbilityCastPoint"                "0.3 0.3 0.3 0.3"
    
            // Time        
            //-------------------------------------------------------------------------------------------------------------
            "AbilityCooldown"                "10.0 10.0 10.0 10.0"
            "AbilityChannelTime"            "2.0 3.0 4.0 5.0"
    
            // Cost
            //-------------------------------------------------------------------------------------------------------------
            "AbilityManaCost"                "150 160 170 180"
    
            // Special
            //-------------------------------------------------------------------------------------------------------------
            "AbilitySpecial"
            {
                "01"
                {
                    "var_type"                "FIELD_FLOAT"
                    "damage_per_second"        "100.0 100.0 100.0 100.0"
                }
                "02"
                {
                    "var_type"                "FIELD_INTEGER"
                    "radius"                "350 350 350 350"
                }
                "03"
                {
                    "var_type"                "FIELD_INTEGER"
                    "range"                    "1550"
                }
                "04"
                {
                    "var_type"                "FIELD_FLOAT"
                    "speed"                    "1050.0"
                }
                "05"
                {
                    "var_type"                "FIELD_FLOAT"
                    "max_channel_time"        "2.0 3.0 4.0 5.0"
                }
                "06"
                {
                    "var_type"                "FIELD_INTEGER"
                    "vision_radius"            "800 800 800 800"
                }
                "07"
                {
                    "var_type"                "FIELD_FLOAT"
                    "vision_duration"        "3.34 3.34 3.34 3.34"
                }
                "08"
                {    
                    "var_type"                "FIELD_INTEGER"
                    "channel_vision_radius"    "350"
                }
                "09"
                {    
                    "var_type"                    "FIELD_FLOAT"
                    "channel_vision_interval"    "0.5"
                }
                "10"
                {
                    "var_type"                    "FIELD_FLOAT"
                    "channel_vision_duration"    "10.34"
                }
                "11"
                {
                    "var_type"                    "FIELD_INTEGER"
                    "channel_vision_step"        "150"
                }
            }
        }
    The bug: Illuminate starts at Ezalor's position, instead of 100 units infront of him, making it 100 units shorter than it should be.




    Quote Originally Posted by ThoAppelsin View Post
    Everything seems to be as intended...

    Moderate #156

    HOWEVER

    I have tested the actual Illuminate range on W3 DotA with setting coordinates.
    It looks like I can deal Illuminate damage up to 2124 range...
    The changelog says 2000. If the range display is correct, then it does indeed deal damage up to 2000 range on Dota 2.
    I don't know why it is 2124 on DotA. 2000 + 100 + 24. 24 from the collision thing, 2000 is the actual range, where does the 100 come from?

    Illuminate seems to have 1600 range according to the tooltip. it should be 2000 with 6.75 parity.
    Last edited by bu3ny; 02-01-2014 at 09:49 AM. Reason: Updated OP
    Make sure to read the Forum Rules as well as the stickied Threads of the Forum Section you are posting in.

    Contributions i'd like to highlight:
    My Suggestion: Coaching System
    My Sticky: Intended Changes List
    My Challenge: Completely Fixed Hero Challenge: Skywrath Mage

  2. #2
    Basic Member Kevinriz9r's Avatar
    Join Date
    Nov 2011
    Location
    Germany
    Posts
    525
    confirming it test it with range display 2000

  3. #3
    Basic Member
    Join Date
    Nov 2011
    Posts
    22

    Bug Keeper of the light Range only 1800 instead of 2000.

    Using the console command dota_range_display 2000 and then hovering over the skill [which by the way tool tip still says 1600] it seems like the range shows as 1800 and after testing it actually is at 1800 as opposed to 2000. ALSO, The vision it gives is at 1600 still. This needs to be changed to the 2000 its suppose to have. Can someone confirm as well.

    EDIT: Actually i'm not sure if the dmg is only at 1800 but the vision is definitely at 1600 as well as the tooltip and the range the tooldip displays is 1800 but the dmg may actually be 2000.

    Yeah, The dmg is 2000. But theres still the vision being 1600 and tooltip text inaccuracy and the tooltip range finder.[ ALthough im not sure if the tooltip range finder is suppose to just show the casting range until your hero will move then cast]. Also, the Visual runs for 1800 idk if thats intended.

    TL;DR
    Dmg is at 2000 Range
    Illuminate Visual is at 1800 Range
    Tooltip text is 1600 Range
    Tooltip Range finder is 1800 range if you click out of the 1800 range it will move you idk if thats intended or if its suppose to match up to 2000.
    Last edited by st4n13y415c; 10-04-2012 at 05:27 PM.

  4. #4
    Basic Member
    Join Date
    Dec 2011
    Posts
    1,903
    Did you verify the impact distance or the visual?
    I somewhat find it hilarious if they've failed to apply this change correctly seeing as they 'fixed' this from 2000 to 1600 the week before...

  5. #5
    Basic Member
    Join Date
    Nov 2011
    Posts
    22
    Im using the console cmd to find the range. But i may of been wrong about the dmg portion, still testing.
    Oh cool they merged thread.
    Last edited by st4n13y415c; 10-04-2012 at 05:23 PM.

  6. #6

    Ezalor's Illuminate range error?

    I did some testing and I believe Ezalor's q ability should have had its range buffed up to 2000 but it seems to still be at 1600. Is this a bug or intention?

  7. #7
    Basic Member
    Join Date
    Apr 2012
    Posts
    140
    The aoe is 400 with a range of 1600, meaning it can hit units at up to 2000 range. The previous range was 1200.

  8. #8
    Basic Member
    Join Date
    Nov 2011
    Posts
    22
    Quote Originally Posted by smokedsalmon View Post
    The aoe is 400 with a range of 1600, meaning it can hit units at up to 2000 range. The previous range was 1200.
    The 400 aoe is just how wide the illuminate is not the range.
    http://dev.dota2.com/showthread.php?t=57425

  9. #9
    Basic Member
    Join Date
    Apr 2012
    Posts
    140
    Quote Originally Posted by st4n13y415c View Post
    The 400 aoe is just how wide the illuminate is not the range.
    http://dev.dota2.com/showthread.php?t=57425
    Yes, that is what I said. The center of a circle with a radius of 400 travels 1600 distance from the point at which kotl channels the spell. This means that it hits units at 2000 range. I am really not seeing the bug here. I tested this when kotl first came out, and I understand the difference between AoE and range. I have not tested this myself in the current version, but if what you reported in showthread.php?t=57425 is true, then what was reported here, is not a bug.

  10. #10
    Basic Member
    Join Date
    Dec 2011
    Posts
    11,187
    added to sticky.
    Make sure to read the Forum Rules as well as the stickied Threads of the Forum Section you are posting in.

    Contributions i'd like to highlight:
    My Suggestion: Coaching System
    My Sticky: Intended Changes List
    My Challenge: Completely Fixed Hero Challenge: Skywrath Mage

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •