@User:Ddfairchild Is it possible to auto-format type parameter into a clickable link as follows? [[Starship Catalogue - {{{type}}}]]

Trajos (talk) 16:02, 22 July 2020 (UTC)

I believe it's possible. The only question I'd have about doing it is that we have historical pages for our Starship Catalogues. So if you happened to be looking at a starship from Visions and clicked this auto link, it would take you to the current catalogue page, not the one where the ship actually showed up. Now you could jump to the proper fighter catalogue page from there, assuming you remembered which version you were coming from. Don't know if that would be confusing or not. Thoughts? Thanks! Ddfairchild (talk) 16:13, 22 July 2020 (UTC)
I see your point, I think a link would be more beneficial for an average user. Users of latest version (who I'd imagine constitute the vast majority of users) will benefit unconditionally, while the minority of users of earlier versions would still benefit, as they would be taken to latest page then need to do an extra click at the top of the page to go to their version. If they are earlier version users - they are probably quite used to checking that the page is about their version already. Trajos (talk) 16:26, 22 July 2020 (UTC)
I've made the change. I've got to figure out how to handle Frigate types, as we don't have a catalogue page for those. But the link will work for the vast majority of our pages. Thanks. Ddfairchild (talk) 16:56, 22 July 2020 (UTC)
Thank you for that. Feel free to share an example page for a frigate and I can have a look for some ideas if you want, but I think either a red link (non-existent page), or a stub page would be alright? Trajos (talk) 17:46, 22 July 2020 (UTC)
I've created the needed pages to handle a frigate catalogue here Starship Catalogue - Frigate. Thanks! Ddfairchild (talk) 05:27, 23 July 2020 (UTC)
Good stuff. Btw it looks like there is quite a bit of duplication of information between the catalogue and the main page - and this is a more general problem not specific to just frigate ship type. This presents 2 problems: the need to update both pages and the risk that information may diverge if someone only updates one page but not the other. I think there are 2 possible solutions:
  • Make catalog page stub-like with just a one-line summary linking to the main page + containing the table, or
  • Merge catalog page into a sub-section of the main page, perhaps making it a collapsible as it may get quite long over time.
I'd say option 1 seems better (as it is less radical for one and also if the table is long - a separate page would be more convenient anyway). What do you think? Trajos (talk) 11:14, 23 July 2020 (UTC)
I probably did add a bit too much info on the frigates, I've simplified it a bit. However, I did a quick check of the other catalogue pages.
We have a brief 1-2 sentence description of the type of ship so the user knows what they'll see in the catalogue.
We have a brief 1-2 sentence description of the inventory size. This helps the user understand the multiple tables on the page, which are broken down by inventory.
I don't know how we can make it much simpler than that <g>. Forcing the user to jump back and forth between the two pages would be problematic IMHO. Thoughts?Ddfairchild (talk) 15:46, 23 July 2020 (UTC)
Thanks - that looks pretty close to my "option 1", I think this is decent now as it is simple enough to avoid duplicating too much information. Some unrelated requests below.

Useful enhancements for both template and its /doc:

  • seed: is an existing template parameter, but it's missing from /doc - do you think you could add it to /doc so people know it exists? Example usage: Akyoto's_Victory.
  • location: Says Point of Interest the starship is located in, like Trading Post, Space station, Space Anomaly, Space battle, Star system - additional options could be Freighter, as that's where I bought some of my ships - a legitimate alternative to "Trading Post or Space station", and also Crashed ship - to indicate it was found on a planet.
  • Galactic coords: Since this is a rather obscure feature for new players, how about changing the header into the link: [[Galactic_Coordinates|Galactic coords]] to help the readers (I noted that /doc already has the link - so all good there).
  • type/subtype could you make those as links in the /doc, so someone willing to add a new ship can easily verify the correct value they need to enter here? type of starship (Shuttle/Fighter/Hauler/Explorer/Exotic/Freighter/Frigate).
  • subtype a link would be nice here too: subtype for Freighters.
  • inventory it says size of inventory (Small/Medium/Large) - but even I have no idea which one is small or which one medium, so would be good modify the /doc to say that e.g. "small is 5x5 or less" etc (just need to determine the exact grid size, cos 5x5 is just my example). Also - for freighters apparently the values are Tiny/Small/Normal/Capital - from game files. But again I'm not sure what the specific grid size is for each one.
  • class - would be nice to display this as an icon when rendering the template, e.g. CLASS.S.png looks nicer than just S. Template could also validate that field then and show an error if it's value is not in C, B, A, S list.
  • damage / damageB (and also shield(B) + warp(B)) - it says "damage bonus", but people seem to just enter it as an absolute value (e.g. 69.9 might be absolute value for damage, while looking at the savefile it says damage 9.873745874365). So maybe worth elaborating that this is explicitly not the number seen in game GUI, but specifically the number shown in savegame.
  • validation: for fields taking a value from a list (e.g. type, subtype, class etc) maybe worth adding validation, so if someone makes a typo and enters say "Freightor" - the template will render a red error message for that value, e.g. Wrong ship type {{{type|}}}, acceptable types are: Shuttle/Fighter/Hauler/Explorer/Exotic/Freighter/Frigate.

Trajos (talk) 18:00, 23 July 2020 (UTC)