Template talk:Level infobox: Difference between revisions

From Halopedia, the Halo wiki

Line 22: Line 22:


:I wouldnt be against that. We just need to remember to update stuff like this lol.-[[User:CIA391|CIA391]] ([[User talk:CIA391|talk]]) 15:42, April 13, 2019 (EDT)
:I wouldnt be against that. We just need to remember to update stuff like this lol.-[[User:CIA391|CIA391]] ([[User talk:CIA391|talk]]) 15:42, April 13, 2019 (EDT)
::As per CIA391. It'll be a big task to constantly update the infobox to accommodate changes in the canon timeline.— <span style="font-size:14px; font-family:Arial;">[[User:Subtank|<span style="color:#FF4F00;">subtank</span>]]</span>  03:42, April 14, 2019 (EDT)

Revision as of 02:43, April 14, 2019

Is there a way to not display certain rows in levels in which they are not applicable (such as all-cinematic levels)? --Dragonclaws(talk) 23:43, January 10, 2010 (UTC)

I have wikified the code and made all fields optional. Fields not filled ("not applicable") will not produce a table row.

I've also added a new field nowalk to toggle the "need walkthrough" message. Presumably the message is not intended to be a permanent fixture. However this means every use of the template needs to be gone over to toggle it where it needs to be. If that's no good, it can be modified to display the message by default, and be manually toggled off.

EDIT: Looks like this was accounted for in the previous code. Appropriate message should now appear automatically. - Meco (talk, contribs) 01:20, January 11, 2010 (UTC)

New Field

If we have a field for weapons and vehicles, shouldn't we add a new field for Equipments (in Halo: CE and Halo 3) and Armor abilities for Halo: Reach? —S331 Bubbleshieldhud.svg (TalkContributions) 05:25, 29 May 2011 (EDT)

It gives more information on what players can do. I really want to do this myself, but I want to make sure first I can. —S331 Bubbleshieldhud.svg (TalkContributions) 11:08, 31 May 2011 (EDT)

Major changes

Just to let everyone know that this template will change drastically by this Friday. It will be something similar to the Multiplayer level infobox. The "Enemies", "Weapons" and "Date" field will be removed; the first two is simply a list and that should be moved to their walkthrough component instead, while the latter is simply not accurate as it appears.— subtank 07:55, 1 May 2012 (EDT)

No date? I've always thought the field was rather relevant. Not to the casual player, but to people who like to view these events against the backdrop of the fiction as a whole. Or should the information on the date be explained in the introductory paragraph instead? --Jugus (Talk | Contribs) 04:30, 4 May 2012 (EDT)
It's not entirely relevant; emphasis on "entirely". The problem is that some/most levels take place within the same time, making it quite useless. Halo 1 and Halo 3: Recon are the best examples to illustrate this. In addition, the infobox is capable of presenting the levels in a chronological order via its Prev/Next fields, just like how we did with all Halo 3: Recon's levels.— subtank 12:23, 4 May 2012 (EDT)

Concurrent field

We have the Previous and Next boxes for linking the next missions in the campaigns, but would anyone be opposed to adding a Concurrent field for listing missions that take place at the same time as the current one? Primarily, Halo Fireteam Raven runs parallel to Halo CE's campaign, and I think being able to denote that in the infobox would be good. BaconShelf (talk) 15:36, April 13, 2019 (EDT)

I wouldnt be against that. We just need to remember to update stuff like this lol.-CIA391 (talk) 15:42, April 13, 2019 (EDT)
As per CIA391. It'll be a big task to constantly update the infobox to accommodate changes in the canon timeline.— subtank 03:42, April 14, 2019 (EDT)