Now why this give_up value exists I don't know, but probably it has to do with some extreme edge case that causes issues. This is less than the give_up value mentioned (1850, which is less than the total possible units). When MK was added, Seer Stone didn't exist and so you could only increase cast range by so much (I believe ~1600 units total, at the time?). The most likely explanation is due to (a lack of) regression testing issues. Nothing else in the game behaves this way. Look at it from the user's standpoint: You have an ability that goes on cooldown if cast from too far away, with no warning whatsoever. In this this scenario, I would say this is working-as-designed but not necessarily working-as-intended. Similarly, something that's working-as-designed but not necessarily working-as-intended could be considered a feature (a prime example would be stacking-it wasn't intended to happen, but was deemed by the developer as not a bug and left in). Something that's working-as-designed can be a bug in the sense that it's not intended.
There's a difference between working-as-designed vs working-as-intended. Oceanic Esports Dota Championships 4h 42m Lilgun XctN MESA League Season 1 3h 12m Renewal KBLDS Oceanic Esports Dota Championships 2h 42m Neon Orca Oceanic Esports Dota Championships 42m LBZS MG.T Bo3 | Caster: YuHengTV | !tourney 542 YuHengTVĪsia New Star Cup season 3 LIVE Tiger God Cookie Tiger God vs Cookie | Asia New Star Cup Season 3 | Playoff. Techies Funeral Precession 739 SirActionSlacks Livestreams Last games before patch!! !nordvpn !Gamerzclass 8279 Topsonous
0 kommentar(er)
