Jump to content

"Not Applicable" Option for Settings Templates

Recommended Posts

I've seen multiple ways of dealing with settings which are N/A or Not Applicable, most of which are not preferable for various reasons. Sometimes editors will just delete the "unknown" and leave that line blank, or simply delete the line entirely. Both of these aren't preferable both for wiki automation using bots and simple aesthetics.


I'd like to propose an N/A option alongside the current true, false, and unknown options. This would be usable for multiple cases. Games which don't use the mouse wouldn't require mouse acceleration, games which don't have voice acting wouldn't require subtitles, and games which are 2-dimensional wouldn't require an FOV slider. I think this would be much better for unifying all settings templates across all pages, so that there aren't any pages which have only a few rows on their table due to the irrelevance of many of the settings.



Link to post
Share on other sites

This sounds like a good plan. This would also help catch cases where standard rows like multi-monitor have been removed. The template could automatically display the N/A symbol for blank/absent parameters until existing pages are updated.

Link to post
Share on other sites

Awesome, so generally the consensus is that this has no negative consequences? Would anyone be able to make such an image so we can implement it in our templates? I would do it myself, but I don't have access to Illustrator at the moment and GIMP just goes over my head.

Link to post
Share on other sites
  • 3 weeks later...

"?!" couldn't be replaced by a simple question mark?

like here


it really let you feel that there's something missing there, imo

whilst i think that not applicable field should simply be hidden..


if i'm playing super mario 2D, i won't ever look for a fov hack, so since the row is useless it shouldn't be shown

Link to post
Share on other sites

I'm sorta torn. I can see that having a N/A field for certain fields can be informative, but putting N/A for lots of fields can clog up an article.


Totally removing lines however could possibly leave some doubt in the user.


I'm leaning towards including fields and just leaving them N/A, but we gotta consider the trade off of potential clutter.


A potential middle ground could be include fields that are a part of some or most games in the particular genre/style of a game, but not fields that aren't really expected (i.e. fov in a 2d platformer)


Also, why not make N/A a slightly muted orange? That way it sticks out but doesn't sear your eyeballs.




Also, random aside: Keep the interrobang for unknown. If only because it's a fun word to use in any conversation.

Link to post
Share on other sites

For consistency amongst the design I definitely thing the Unknown icon should stay.


I can see how this could potentially add clutter, but I feel that the tables wouldn't, because they're well-contained in their borders, become cluttered by this addition.

Link to post
Share on other sites
  • 1 month later...
This topic is now closed to further replies.
  • Found PCGamingWiki useful? Please consider making a Donation or visiting our Patreon.
  • Who's Online   2 Members, 0 Anonymous, 389 Guests (See full list)

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Forum Statistics

    Total Topics
    Total Posts
  • Create New...