Talk:Units

From Zero-K
Jump to navigation Jump to search

Unit summaries

I think a very brief summary of each factory could be very helpful, like:

  • Cloakbots: High DPS, fragile, relatively shorter-ranged. Several units are cloaked or have area cloaking.
  • Shieldbots: Tough, low DPS. Several units have shields and shield-related abilities such as turning shields into damage.

Etc. I would do it myself, but I know far too little of the different factories to be able to give good brief summaries.

In addition, it might be nice to automatically generate and show (similar to this script: https://github.com/ZeroK-RTS/SpringRTS-Tools/blob/master/unitguide/export_unit_templates.lua , which is some really nice functionality, kudos to Histidine91) a box plot for each of some different main statistics, such as "DPS/cost", "Hit Points/cost", "Movement Speed", "Range", "Weapon AOE". The units of each factory would then be depicted with one box in each box plot. That by itself could give an easy way to get a quick and superficial impression of how each factory compares to other factories. That said, lots of units have special abilities or special weapons, and even regular statistics can have major importance (which I think is a really nice part of Zero-K), so for at least some of those statistics, the plots might be both difficult and laboursome to automatically generate as well as possibly be very misleading, which might be worse than no impression. So this may not be a good idea and not at all worth the time or effort. — unsigned comment by 109.57.58.139

Reg. the latter part, I think statistics such as "log2(Hit Points)" (illustrating force concentration, which is relevant for striders and tanks) and "log2(cost)", and maybe "log2(Range)" instead of "Range", might be useful. — unsigned comment by 109.57.58.139

Too much html+css

Our players are already intimidated when it comes to editing the Wiki. This page has enough HTML and CSS now to scare off anyone who wants to edit it and doesn't know how to read HTML. I suggest that the page be converted to Wiki syntax and kept that way. —RandomX (talk) 02:49, 27 July 2020 (CEST)

That's a fair point that I didn't consider, I hoped to keep that amount down, but I didn't succeed without sacrificing the formatting I hoped for. I will cut down the amount of HTML and CSS. I think it would be OK to keep the image links that are also present in the different factory pages, since they should be decently simple, and I don't know whether those images can be included as is using only MediaWiki syntax (if anyone knows how to do that, please do mention it and I will use MediaWiki syntax for the images). --Someoneelsewhere (talk) 03:20, 27 July 2020 (CEST)

I have greatly decreased the usage of HTML and CSS. It looks "noisier" now, however. Does anyone have any proposals or suggestions for making it less "noisy" while keeping it to MediaWiki syntax? I must also apologize, for it seems that it is really simple to include images as is, having just the raw link works when you are just including the image, not using it as part of a link or similar. --Someoneelsewhere (talk) 04:33, 27 July 2020 (CEST)

Dear RandomX, I have partially reverted to using a bit of HTML and CSS again, and it is now not anywhere near as noisy before, however, it still does not seem quite as good as the original version. Given that you are definitely beyond any doubt much more experienced reg. this Wiki than me, would it be possible for you to improve and fix that, maybe such that the text is placed to the right of the image instead of below it, and thus increase visual coherence and decrease space wasted? I believe that could be very helpful to the section. Thank you very much in advance and best regards. --Someoneelsewhere (talk) 06:06, 27 July 2020 (CEST)