Template talk:Story infobox

Infobox

TBH, this infobox, in it's current state, is chock-full of hacky and/or unintelligible code (see the previous/following sections.) I've recreated this infobox with the following features:

• Split "Storyline" into "Race" and "Storyline"

ex: "Storyline | Commoner Human" → "Race | Human ; Storyline | Commoner

• Cleaned up "Preceded by" and "Followed by" through use of a sub template, which supports all biography options, not just the first question.
• Made first map not optional.

Code can be seen here (and the sub template code can be seen here). Examples can be seen here. Aqua (T|C) 03:31, 6 November 2011 (UTC)

"*Made first map not optional." - is it really necessary? Most of the personal story pages don't have maps, bringing them into Category:Pages with broken file links. MalGalad 11:49, 16 May 2013 (UTC) P.S. same thing for {{Event infobox}}.

Used in Living Story - is this correct?

This infobox has been used several times in the Flame and Frost: The Razing wiki entries. (1) the infobox is an old "hack" according to the author (2) it's not really ideal for Living story, needs a historical paramenter at the very least. Thoughts? --Claret (talk) 08:26, 27 May 2013 (UTC)

The personal storyline missions don't get removed,s o there's no need for a historical parameter. This template shouldn't be used for the living story missions. How other people want to approach it is up for discussion.--Relyk ~ talk < 08:35, 27 May 2013 (UTC)

My thoughts are that the wizards should create a Living story infobox, it will be needed more and more if I read ANet's intentins correctly. Dunno about tidying up this one - it works at least. --Claret (talk) 08:43, 27 May 2013 (UTC)

I'd love a Living Story infobox...the personal story doesn't quite cut it, as it doesn't really allow us to match it up with the Living Story arc. Maybe we can just use the Event infobox...I think it has everything we need (we can use the meta_event to match it to the arc). The only downside is that the Living Story instance names don't always match the name of the event inside it, so it can cause confusion down the line. Vahkris (talk) 19:13, 10 June 2013 (UTC)

I will take a coder to adapt whatever we have to the new stuff. A "meta-event" approach was tried with early Flame & Frost but was not liked. It can rapidly become too complex to easily fit there. A dungeon-like template has been suggested but I don't really know anything about them. --Claret (talk) 19:36, 10 June 2013 (UTC)

I only mentioned the meta-event setup because it results in a "Part of" entry in the infobox, like "Part of: Flame and Frost". I'd rather a more fitting infobox. The dungeon template was suggested because dungeons can have events inside them, but aren't named after the event itself. This is similar to the living story instances so far. Frankly, we just need a separate living story infobox, and a consistent naming pattern for the instances. Vahkris (talk) 19:45, 10 June 2013 (UTC)

Agreed, now who's interested?? Hint... --Claret (talk) 19:46, 10 June 2013 (UTC)

Area/Region code

This infobox apparently never got the code update that looks up the area entered and automatically puts the region in. Right now we have to have both flags or the region doesn't appear. Can anyone bring it over? I can't tell what needs to be updated. Vahkris (talk) 19:14, 10 June 2013 (UTC)

Seems to be working on 3 test pages. --Claret (talk) 19:38, 10 June 2013 (UTC)

Heh, it got a bunch of edits about 15 minutes after I made that comment, on the location parameter, looks like Yandere or Ishmael added it in real quick. Vahkris (talk) 19:42, 10 June 2013 (UTC)

Yandere fixed it, and my OCD is doing the rest. --Claret (talk) 19:43, 10 June 2013 (UTC)

SMW is still kind of new to me, so I am not always sure things work as intended. The only thing which might be good is something like a bot run which moves location2 and location3 input into a comma seperated list. I just relized that we could structure the whole code much better with the SMW especially the arraymap functionality. The code of this infobox is quite horrifing. ^^ - Yandere 19:44, 10 June 2013 (UTC)

Well if someone wanted to clean it up, that'd be good. I'm starting a slow progression through the personal story pages, adding dialogue and info as I can to try and fill it out since the Personal Story pages were noted as being rather sparse and stub-like...call it project #726 in my list. :) Vahkris (talk) 19:46, 10 June 2013 (UTC)

DPL parm check of region/region2:

{{User:Dr ishmael/dpl parm check|Personal storyline infobox|region:region2}}

For checking which pages use the parameters. —Dr Ishmael 19:55, 10 June 2013 (UTC)

Added problem is that some pages use POIs as areas which is probably undesirable. --Claret (talk) 19:58, 10 June 2013 (UTC)

location2 and location3 are now part of the comma seprated list. I deleted these two parameter already from the infobox. Could some bot delete all region, region2 and region3 parameter? They are essentially useless. - Yandere 20:23, 10 June 2013 (UTC)

I updated the parm check above to show region/region2; region3 is not used anywhere. —Dr Ishmael 20:26, 10 June 2013 (UTC)

You might want to fiddle with the template to use canonical names eg Containment On Red Alert --Claret (talk) 20:44, 10 June 2013 (UTC)

Done. I had to add the property to the location infobox, so it will take a while for the job queue to process all locations. And then the storyline pages will have to wait for the cache to expire (or be purged), so it may take a bit over 24 hours to see it work. —Dr Ishmael 21:08, 10 June 2013 (UTC)

Green starburst

Any chance of possibly maybe perhaps getting the Personal Story icon () in here like the NPC infobox uses for the service? The biggest reason I can find is that the green clashes horribly with the orange header...which may be reason enough, come to think of it. I tried seeing if I could pull it from that infobox but I honestly couldn't figure out the nested logic and how it connects to it. Vahkris (talk) 20:29, 13 June 2013 (UTC)

Example of horribly clashing colors: User:Vahkris/Sandbox Vahkris (talk) 20:37, 13 June 2013 (UTC)

I like the idea. The current quest color is orange because of the dynamic events. But I agree orange and green don'T work well together. What color would you suggest? Green would not be so great on the contrast. - Yandere 20:47, 13 June 2013 (UTC)

Green is items. There is crap loads of discussion on colors themes from way back. Those are fun to read, unfortunately it's really hard to get discussion going about changing any of it.--Relyk ~ talk < 20:56, 13 June 2013 (UTC)

Red is items, AFAIK. Green is NPCs/Pets/Objects, orange is events/hearts/living story (so far), purple is Area, grey is effects/generic, brown is recipe... I think that's it. Yellow is very hard to read...is blue used? Maybe a dark blue to avoid problems with a contrast? Doesn't give the instant feeling of the Personal Story though. Green would have been awesome, even a really dark forest green, but it's pretty established already and the NPC one is pretty dark already...not sure whether a light green would work. Wonder if a dark orange would stand out enough from red and orange and not contrast. Vahkris (talk) 21:20, 13 June 2013 (UTC)

Time for a split

Isn't it time to copy the personal storyline info box and other stuff to a Living storyline infobox and stuff so that the changes can be relevant to LIVING rather than PERSONAL. I can only see the compromises getting worse. It seems accepted that Living soryline does not fit well with personal but people are constrained from working on the Living side for fear of breaking the Personal. --Claret (talk) 18:50, 23 June 2013 (UTC)

I think it would actually be more like time for a clean up. The current infobox has horrible coding, and is therefor hard to work with. The preceeded by and followed by entries could be using arraymaps and the most of the switch case statments only have some entries because it made sense back than not because the are still needed. The personal story is a very static thing, and will probably not change much in the near future. Most of the logic utilized in hear can be trimmed. But this will require some work. Splitting infoboxes resulted in a huge mess we see in item infoboxes and I am not so sure if a split here is a good idea either. - Yandere 19:02, 23 June 2013 (UTC)

Might well be true, but my point is to split them first then fix them second without having to check that one's fixes are not tripping the other's up. Just my 2¢. --Claret (talk) 19:05, 23 June 2013 (UTC)

Splitting the item infobox didn't make a mess but prevented it from being one.--Relyk ~ talk < 07:27, 24 June 2013 (UTC)

Sorry, you don't get my meaning. You shouldn't have to make changes to one story type to allow for another type. Each should be handled in its own "space". It might well be that in this case things are fine and dandy, but if and when the structure of each component is updated, it's going to be far easier if the "templates/layouts" are separate. It's going to add a whole layer of complexity to the situation. --Claret (talk) 10:40, 24 June 2013 (UTC)

I'm so late to the party that all the cake has decomposed, and the house has been demolished, but I'm here at last!

I've created {{Living world infobox}} because I agree on the principle that theres almost nothing in common between the templates. I'll rewrite this template on saturday morning. -Chieftain Alex 22:07, 23 January 2014 (UTC)

wasn't much that could be rewritten in this one; removed the living world stuff + put in spaces to make the switch statements legible. -Chieftain Alex 21:08, 24 January 2014 (UTC)

Conversion from Personal storyline infobox to {{Personal story infobox}}

→ moved from Template talk:Personal story infobox

The old "fears" bit of chapter 8 still needs to be converted. -Chieftain Alex 10:28, 22 June 2015 (UTC)

Do we need to convert the articles, or template, or both? --BryghtShadow (talk) 14:34, 22 June 2015 (UTC)

Just the articles really. I guess I can run the bot again on the historicals. -Chieftain Alex 15:46, 22 June 2015 (UTC)

Tarir Causing Broken Links

There appears to be an an issue when linking Tarir, the Forgotten City in the infobox, as when to NPCs linked to stories that have it as their location, it gets weird/botches up. This can be seen on Aurene and Mordrem Alpha, it looks like it's repeated or broken or something. I'm guessing it's the comma? - Do_odleplex 22:16, 26 September 2016 (UTC)

Wrong template doodle. {{Living world infobox}} != {{Personal story infobox}}. -Chieftain Alex 23:21, 26 September 2016 (UTC)

Starting to think we're almost as good as the devs when it comes to making more and more boxes. How many boxes inside of boxes do we have, though? G R E E N E R 23:24, 26 September 2016 (UTC)

Anyway, the issue was commas screwing up {{Infobox location}}. I should run a robot to go through all the infoboxes on all the pages replacing comma separators with semicolons... not going to any time soon. -Chieftain Alex 23:29, 26 September 2016 (UTC)

I came here as City of Hope was using the personal story infobox, but if it's borked in the Living world one too, I guess it's good I wound up here by accident as both needed to be fixed. - Do_odleplex 23:34, 26 September 2016 (UTC)

Add property to story previous and next story steps

I'd like to request properties for previous and next story step names (IDs would not work because LW1). Something like "Has story previous step" and "Has story next step". --BryghtShadow (talk) 13:22, 27 August 2019 (UTC)

Done. Added Property:Has story previous chapter Edit:Property:Has story previous step and Property:Has story nextchapter Edit:Property:Has story next step (compare with the already existing property name Property:Has story chapter).

Side remark: There are also the properties: Property:Has story storyline number → Property:Has story chapter number → Property:Has story sortkey number → Property:Has story step number allowing to create this table Personal story#Chart automatically, see User:Tolkyria/Personal story, just by semantic mediawiki sorting.

Regarding LWS1, after more 6 years I can't see the idea of the chapter number property for LWS1, see the code User:Tolkyria/Personal story list for manual adjustments to how it is current presented at the NPC pages, e.g. Braham. --Tolkyria (talk) 10:39, 1 September 2019 (UTC)

Edit: Mixed up the terminology. --Tolkyria (talk) 12:00, 1 September 2019 (UTC)

Much thanks :) --BryghtShadow (talk) 05:32, 2 September 2019 (UTC)

Today's chapter title

I add the property Property:Has story chapter title which was previously built in the result format based on the story line, the chapter number and the chapter. See this edit (so we are executing it here directly in the infobox rather than performing it in each result format call of various templates, e.g. {{rewarded by}} displaying a list of stories that reward a certain item).

Finally coming to my question: What's the title from the episode 5 The Icebrood Saga: Champions Chapter 1: Truce? Is it really: Episode 5: The Icebrood Saga: Champions: Chapter 1: Truce? Sounds like an overkill to me. For a complete list of all story chapters and how the chapter titles look like in an unordered list, see User:Tolkyria/Personal story list. --Tolkyria (talk) 18:25, 17 November 2020 (UTC)

The story journal has just "Champions" like "No Quarter" or "Jormag Rising". There is no mention of the "chapters" Truth, Power, Balance, Judgement (not the parameter chapter). —Kvothe (talk) 18:42, 17 November 2020 (UTC)

Okay, just finished downloading, I see. So the parameter chapter set in the story infoboxes should be simply "Champion" (right now it was initially set to Truce - which redirects to Chapter 1: Truce, currently it's a little bit awkward when using a redirect as chapter parameter - I changed it to Chapter 1: Truce) and hence the chapter title used in result formats should be also simply Episode 5: Champions? Or should we add the suffix Chapter 1: Truce somehow in the result formats? --Tolkyria (talk) 19:00, 17 November 2020 (UTC)

Ingame I actually do not find any mention of "Chapter 1 Truce" (with any combination of ; : _). But it makes sense to split the releases and keep the pages e.g. "Chapter 1: Truce". So a suffix would probably make sense. —Kvothe (talk) 19:11, 17 November 2020 (UTC)

Indeed, I'm curious how Chapter 2 will look like. Well, probably it will be episode 6 anyways as technically having different meta reward completions, etc... might not even be possible otherwise.

I updated the chapter title to the current mainpage title: "Champions — Chapter 1: Truce" (used in result formats) and replaced the parameter chapter with "Champions" (matching in-game). --Tolkyria (talk) 19:25, 17 November 2020 (UTC)

LWS1 revisited

How should we treat the SMW properties for the new and the old LWS1 episodes? See my sandbox for a substituted query (in late March) and a live query.

The questionable properties are:

• Property:Has story storyline number - this property simply states the storyline number, e.g. Personal Story is 0, LWS1 is 1, LWS2 is 2, ..., End of Dragons is 10.
  • Suggestion: In my opinion we should clearly split the historical and the current story line, so for example we could set the historical to 1.9 and the current one to 2. Edit: I now tend to set the historical storyline to 2 and the new relaunched storyline to 2.5, this should be more straight forward and somehow group them better (e.g. then one could ask for greater equal 2 and smaller 3 to get all LWS1)
• Property:Has story chapter number - this one describes the story chapter (or episode number), for LWS1 it's not that straight forwards as Alex added this numbers several years after the release (see also Property:Has story chapter title)
  • Suggestion: If we relabel the storyline number as described above, then there's no reason to change the old historical numbering, for the new one we would simply count through the released episodes.
    • Edit: Cleaned up, see below, no edit needed anymore.
• Property:Has story chapter title - this one lists the story chapter title that is called by query templates (e.g. {{rewarded by}} to return the full episode title.
  • Suggestion: The historical episodes use a huge switch to adjust Property:Has story chapter number to their actual in-game episode numbering (maybe due to some mislabeling, but also due to several "Special Events"). To avoid any confusion we could add prefix "(Historical)" in front of the title. The new episodes could simply use naming scheme from the other LWS, namely "Episode 1", ...
  • For example:
    • The historical story Braham: Help from the Legions could display the title: "(Historical) Episode 3: Flame and Frost: The Razing"
    • The new story A Quiet Celebration could display the title: "Episode 1: Flame and Frost"
• Property:Is part of storyline - this property gives the storyline name, here "Living World Season 1".
  • Suggstion: In order to avoid confusion we could set the story infobox parameter to "storyline = (Historical) Living World Season 1" which would be displayed exactly like this with an unlinked "(Historical)". Internally it would be still handled as "Living World Season 1" as this property is a page property which requires the existance of the according page name (the storyline sort property would handle order the accordingly).

--Tolkyria (talk) 08:07, 20 April 2022 (UTC)

I cleaned up the mismatch between the internal chapter numbers and the displayed episode numbers, see this edit (after adjusting the chapter number on all LWS1 pages). --Tolkyria (talk) 18:51, 20 April 2022 (UTC)

Still to do: Has story storyline number (I prefer 2 for the old and 2.5 for the new) and Has story chapter title (we could add the prefix "(Historical)" based on the infobox status = historical).

Not necessarily: Is part of storyline (no change needed, actually this should be fine, with the historical status box).

--Tolkyria (talk) 18:51, 20 April 2022 (UTC)

Summary of my edits:

• Property:Has story storyline number - Adjusted storyline number in the infobox to sort first the historical LWS1 and then the current episodes in order to sort it chronologically by their release.
  • The infobox sets it to 2 if storyline = Living World Season 1 and status = historical.
  • The infobox sets it to 2.5 if storyline = Living World Season 1 and status is not set to historical.
• Property:Has story chapter number - Adjusted the story chapter numbers on the story pages directly, the original LWS1 story chapter numbers match the episode numbers, simplified the code in the infobox.
• Property:Has story chapter title - Adjusted the story chapter title (used e.g. in {{rewarded by}}) to list the prefix "Historical". For example, the historical story step Braham: Help from the Legions now displays the chapter title: "Historical Episode 3: Flame and Frost: The Razing" used in query templates, compare with the new story step A Quiet Celebration which has the usual chapter title: "Episode 1: Flame and Frost".
  • The infobox adds the prefix "Historical" if storyline = Living World Season 1 and status = historical to this property.
• Property:Is part of storyline - No changes needed.

--Tolkyria (talk) 09:40, 21 April 2022 (UTC)