Board Thread:Wiki discussions and announcements/@comment-3974211-20160811212848/@comment-1330314-20160812070656

I'd say in-line numbers break the flow just as badly, if not worse, as users have to constantly run through a stream of numbers even as they're trying to understand what an ability does. I imagine this is significantly worse on mobile devices, where preexisting walls of text would turn into stat soup. I'm not a fan of moving information like this to Ability Details either, because the latter is typically used for explanations on the particularities of certain mechanics or special cases, and again not for core gameplay info. Historically, Ability Details has been used to sweep unwieldy information under the rug, so to speak, and the result has been messy, difficult to read, and on occasion even ignored completely, as many users were not even aware the section existed, or didn't check when asking questions in the comments.

That tooltips do not work on mobile devices is a serious problem regardless of where range information ends up. It's central to a lot of critical information display, including the cctip template you worked on, and we can't just operate by dumping every ability-related number as is. We need a way to compress ability information in some way or another on the main section, as evidenced already by the inflated displays of some abilities (and not just range), and if we can't expect to use tooltips we're going to have a serious formatting problem. If we are to display range information in-line, I'd say specifics such as secondary ranges, missile speeds, delays, etc. should count as complex enough to be put under tooltips: a user looking up an ability on their mobile or trying to look up the wiki in-game is, in the vast majority of cases, not going to be doing much with exact knowledge of an ability's radius in in-game units, nor are they going to count the duration required to channel an effect or the like. At the very least, the cast range of an ability is meaningful as it gives an idea of how far it'll go, but in the absolute worst case, it's no major loss if every other in-line stat gets put under a tooltip, and if it is, then we'd better get back to the drawing board in displaying everything, not just range details, without tooltips.