Template talk:Map infobox
Contents
Categorize by gametype
Can someone who knows what they're doing make it so it automatically categorizes maps by gametype? Add [[Category:{{{gametype}}} maps]] or whatever to it. -- Nineaxis
00:59, 10 August 2010 (UTC)
- Done. -Shine () 01:03, 10 August 2010 (UTC)
Include capture timings for cp maps
I find it quite distubing when I see tables like the one on the Egypt article, which looks incredibly poorly formatted, and it seems like informtion which might as well go in the infobox (collapsed). What do others think about this? ~ lhavelund (t ▪ c) 03:42, 16 October 2010 (UTC)
Image width parameter
Currently, there is no way (as far as I know) to adjust the size of the map picture in the infobox; it is always 300 pixels wide. This often causes text in the infobox to widen it and create white spaces in-between the picture and the infobox's sides. This is more common in translated pages, but also occurs in EN articles too.
In Dutch, "Ammo boxes" is "Ammunitiepakketten". This pushes everything in all parameters a lot to the right, so if you have a map developer with a big name or just a map with all three sizes of ammo boxes, you have things like the infoboxes in Frontier/nl and Snowplow/nl.
As previously said, this doesn't affect just Dutch or translated articles: maps that have the HHH listed as a hazard, maps with developers with big names like Precipice and Yukon, and even maps with big file names like Maple Ridge Event have their infoboxes stretched wider than the map picture.
Would this be a parameter with a merely cosmetic impact? Yes, it would. Do we want an ugly wiki, though? :B - BrazilianNut (talk) 05:46, 28 October 2019 (UTC)
"release-date" and "last-updated"
First, I think we should get rid of last-updated - we already have the Update history for that.
Second, I think we should use release-date the same way we use {{Item infobox}}'s released parameter - i.e., with "{{Patch name|M|D|YYYY}}" (and "<br>([[Update]])" if applicable). - BrazilianNut (talk) 16:01, 30 May 2021 (UTC)
Add a "map surface area" parameter?
I know that this probably is not a very useful thing to know. But having some kind of a proper, factual measurement of the map's size could go a long way in conveying the reader just how large/small a map is. Currently, the only way to get a size estimate is to glance at the map overview, which isn't a very useful thing since various overviews are taken at different resolutions and cl_leveloverview levels. This should not be a hard thing to measure either. I think there exists a console command which automatically measures all the standable area of the map and spews it out in hammer units squared. Lolimsogreat21 (talk) 21:51, 2 May 2025 (UTC)Lolimsogreat21
- I don't think this is information the average user wants to or needs to know. Images themselves help give a reference for how big maps are too, not just the overviews.
| s | GrampaSwood
(talk) (contribs) 21:53, 2 May 2025 (UTC)