Talk:Stun

Grouping
These articles maybe should be grouped in a single one labeled "status effects" don't you think? Either that, or expanded further with more info like wich heroes have stun skills and such. -ChocolateWaffle 23:34, 18 September 2011 (CDT)

Order
I recently alphabetized the stun list, and I'm working on reformatting the slow list to use the same style. There didn't appear to be any kind of order to the list, but if anyone wants to revert it I kept a backup. I also removed Time Lock, as it is already on the Bash page. I was also thinking about sorting it by duration, and I have no problems with it being changed if anyone wants to. -Stupid Lemon Eater 21:34, 19 January 2012 (EST)
 * Great thanks. I'm not aware of the previous list being in any order, so the change should be fine. The Wiki logs the pages history so there's no need to worry about keeping backups. - RJ  02:42, 20 January 2012 (UTC)
 * I'm still on the fence as to how it should look. It has been suggested that we use the minimal skill box template seen here on the Aghanim's Scepter page. The only real problem with it is that items can't be shown using the template. I was also thinking that organizing the list by duration would make more sense than alphabetically, but it isn't so cut-and-dry for effects like Slow (do we organize it by duration or by magnitude of slow?) I think that all the stuns are finally on the list, but I don't want to move on to other pages until we really commit to a format. Additionally, does anyone know of a better way to format these lists than with a two-column table? If an odd number of entries needs to be added in the middle of the list, all the row breaks need to be shifted by one. It will get tedious with at least one hero being released every week. -Stupid Lemon Eater 21:03, 22 January (EST)
 * Something like this maybe? Redefining history 02:49, 23 January 2012 (UTC)


 * Well, we certainly could do a multi-column sortable table (image first column, name second, duration/severity/manacost/whatever for subsequent columns). Would allow more information too. Not sure how it would look, though. Of course, the present system doesn't look all that great on a largescreen monitor anyways. Also not sure if there is a way of making it have multiple abilities on the same row. I might mock one up in my Sandbox if I have time. Baloroth 03:36, 23 January 2012 (UTC)
 * This is exactly how the page is currently formatted. What I think would be ideal is something we could input as a single list with no row breaks, and then have it output as a two-column table or whatever. - Stupid Lemon Eater 19:37, 23 January 2012 (EST)

Mini-stuns?
Should Anti-Mage's Mana Void to listed as a ministun, and Clockwerk's Power Cogs be listed as a regular stun? --Rammite (talk) 16:06, 2 July 2013 (UTC)


 * Realistically, there is no difference between a mini-stun and a stun besides duration. At the very least, I think mini-stun should be defined as exactly 0.01 seconds ONLY and everything longer should be moved into the stun section. Alternatively we could just remove the mini-stun section entirely and add it to the main table. -- Stupid Lemon Eater  20:03, 8 July 2013 (UTC)

chronosphere missing?
84.139.169.167

Templar Assassin Talent lvl 25
I'm assuming nobody has gotten around to updating this since her talent got reworked from petrifying psi spill targets to meld giving a bash. I assume this is the right page where it belongs, but I checked both here and on the bash page. 134.41.120.70 04:46, 31 December 2018 (UTC)

Auto queue
Is there any info about Auto queue? The one that automatically queues all orders and executes them after stun ends?

In this article, there's a little info (move/attack orders override casts and vice versa), but yesterday I was testing things in Demo, and found that some active items break the queue: abyssal will always start attacking targeted unit, ignoring next queued orders. Shiva and BKB also will auto attack after cast, breaking the queue. If Autoattack is set to «never» in settings or there are no nearby units to attack, Shiva/BKB will queue normally.

Can we have some in-depth explanation and maybe some of the above (Shiva breaking queue) wasn't intended and needs fixing?