EPThttp://us.battle.net/sc2/en/forum/topic/20744935063
Cyclone bugged - Page 3
| Forum Index > SC2 General |
|
geokilla
Canada8246 Posts
http://us.battle.net/sc2/en/forum/topic/20744935063 | ||
|
Rowrin
United States280 Posts
http://us.battle.net/sc2/en/forum/topic/20744935063?page=2#31 | ||
|
TheWinks
United States572 Posts
| ||
|
Sapphire.lux
Romania2620 Posts
| ||
|
Cyro
United Kingdom20327 Posts
| ||
|
[PkF] Wire
France24238 Posts
On June 02 2016 07:12 Rowrin wrote: Hey guys, they noticed: http://us.battle.net/sc2/en/forum/topic/20744935063?page=2#31 nice | ||
|
The_Frozen_Inferno
Canada98 Posts
1. Lock-On should have a cooldown of 12 blizzard seconds (that starts when the ability ends or is cancelled) - the in-game performance matches the data editor: working as expected. However, the question is whether the data field should read 6 instead of 12 like it currently does 2. Lock-On's button calculates the duration of the ability by multiplying the values from 2 data fields [# of periodic effects * duration of periodic effects]. -> This value matches what the data editor predicts and what the in-game tool-tips states (20 blizzard seconds, 14 real seconds) 3. Lock-On's button calculates the damage of the ability by multiplying the values from 2 data fields [# of periodic effects * damage of impact effect] -> This value is NOT correct according to the data editor -> according to the DE, this should be 18*20 = 360. the in-game tooltip and liquipedia lists 400. 4. Lock-On should fire up to 20 times, 1 per second. Each attack should do 18 ranged damage. Each attack should have an armour reduction of 1. -> the in-game performance does NOT match the data editor. -> Firing period is correct -> But each attack is doing a flat 20 damage with no signs of armour reduction (400 total, as the tooltip states) *note that [Spell] type damage is simply a tag among other tags. It just so happens that there are no spell-type damage effects in the game that also have armour reduction values. However, that Sentry - Guardian Shield does not reduce the damage suggests that this is indeed a spell-type damage effect Conjecture: blizzard is doing another one of its phantom 'server-side' change to the damage field of Lock-On that does not appear in the editor for whatever frustrating reason. In the past, this has happened on many occasions Supporting evidence for Conjecture: - When I manually make a change to the value of lock-on's weapon damage to 100 with 1 armour reduction, the map prioritizes the new change over blizzard's phantom change. As expected, the in-game tool-tip correctly displays 2000 damage; the cyclone also correctly deals 100 damage and is affected by armour reduction 5. Lock-On, on the surface appears, to be an extraordinarily complicated ability with many unnecessary parts. However, about 1/3 of its parts is dedicated to the aesthetic effect of having the missiles shooting alternately from the left and then right pods. - Another 1/3 is for deciding how to make an auto-cast ability that mimics some but not all of a proper Weapon's characteristics. - The last 1/3rd accounts for how the ability can do separate things to Air or Ground units and how the single ability switches between air and ground modes **** tl;dr: Cooldown value isn't bugged; it just may not be what it's supposed to be | ||
|
TheWinks
United States572 Posts
On June 02 2016 09:22 The_Frozen_Inferno wrote: tl;dr: Cooldown value isn't bugged; it just may not be what it's supposed to be In the absence of patch notes, it should be assumed that the current behavior is a bug over an undocumented balance change. | ||
|
xongnox
540 Posts
Last time i played it, the liberator stay sieged after the abduct (he doesn't attack air and can't move).... but with no active siege zone whatsoever. | ||
|
Athenau
571 Posts
Conjecture: blizzard is doing another one of its phantom 'server-side' change to the damage field of Lock-On that does not appear in the editor for whatever frustrating reason. In the past, this has happened on many occasions The fact that the editor damage values don't match the listed damage means that the editor values are stale. The server-side damage values haven't changed since the beta ended, and were explicitly specified in the beta patch notes: October 15, 2016 Beta Balance Update All signs point to an unintended change. It may be as simple as accidentally removing the server-side cooldown value, letting the client-side value take precedence. | ||
|
eviltomahawk
United States11135 Posts
| ||
|
Charoisaur
Germany16063 Posts
| ||
|
Sapphire.lux
Romania2620 Posts
On June 02 2016 18:06 Charoisaur wrote: I'm surprised blizzard didn't notice it with all the internal testing they're doing. I'm sure they were testing us to see how much attention we pay. | ||
|
summerloud
Austria1201 Posts
On June 02 2016 18:06 Charoisaur wrote: I'm surprised blizzard didn't notice it with all the internal testing they're doing. never gets old  | ||
|
lohdon
170 Posts
[B]5. Lock-On, on the surface appears, to be an extraordinarily complicated ability with many unnecessary parts. However, about 1/3 of its parts is dedicated to the aesthetic effect of having the missiles shooting alternately from the left and then right pods. - Another 1/3 is for deciding how to make an auto-cast ability that mimics some but not all of a proper Weapon's characteristics. - The last 1/3rd accounts for how the ability can do separate things to Air or Ground units and how the single ability switches between air and ground modes The more I think about the Cyclones ability the more it becomes obvious that it is just another case of really poor design. Instead of creating a unit that is fast and can be used for hit and run with manual kiting they give it an ability that resembles the same thing but only requires you to lock on and run away while staying in range. Abilities on units exist to create more strategic and tactical depth but this ability does neither of those things. It just makes the unit harder to balance and supposedly easier to use. | ||
|
Cyro
United Kingdom20327 Posts
On June 02 2016 13:11 eviltomahawk wrote: This is a pretty big bug that they'd better hotfix faster than they slowfixed the Phoenix bug in WoL Which bug was that again? | ||
|
404AlphaSquad
839 Posts
I think it was that the phoenix remained "stunned" after the unit that was graviton beamed was killed. | ||
|
JackONeill
861 Posts
| ||
|
TheWinks
United States572 Posts
| ||
|
Sapphire.lux
Romania2620 Posts
On June 03 2016 02:53 TheWinks wrote: The bug where the cyclone fails to lock on with autocast turned on when it's amoved at something still exists too. You can see it happen at 8:40 in game 1 of TY vs Hush. When you a move it goes in to it's normal attack range of 5; if it has autocast on, then it also locks on at range 7. Don't a move if you want just lock on but use the "c" hotkey. | ||
| ||
