Farlo

Ah, I obviously should have dug a little deeper before posting! I'm actually very familiar with SMW (or was at one point), that's what STEP is using for all the mod categorization and guide tables. I'm glad to hear that you guys are doing it right, although I guess I should have expected that given how well the site is doing in general. I definitely agree that more user friendly presentation would be great to see, when I get a bit of free time this weekend I can throw together some of the basic ones and make them as presentable as you can with giant tables/lists. As far as advertising the feature, you could put a "View all games that support X" banner/link on the glossary pages or maybe even a small link in the table itself? I'm sure there are lots of interesting properties and ways to display them that I haven't noticed yet.

Hey all. So I was reading this thread over on reddit that was asking about which games are known to support high frame rates and I thought "I know who has a giant list of games with this kind of info, I'll bet there's a category for this!". Unfortunately upon arriving at the Borderlands 2 page, I was disappointed to see that categories for game properties/attributes have not been implemented. That should be fixed! When I was working on Project STEP's Wiki we wanted the same functionality: sort and categorize pages based on the properties defined in infoboxes and templates. This can be done rather easily thanks to ParserFunction's #if and #ifeq functions. I see a lot of the templates already use these functions so this may be obvious, but as an example, let's implement Category:High framerate support. Framerate support is cataloged using Template:Video settings's "high frame rate" argument. At the moment "high frame rate" is only being used to toggle the checkbox's display. We can add the following text to also categorize the game based on this argument: {{#if: {{{high frame rate|}}} | [[Category:High framerate support]] | [[Category:Limited framerate]] }} Obviously this statement can be expanded to include any number of potential values, although it looks like you're currently only using a Boolean to represent true/false. Anyways, I think this rather simple addition (if applied to most game properties) provides a lot of benefit when it comes to organizing game features, improving discoverability for users, and potentially providing some interesting statistics to ponder thoughtfully over. Thanks for reading, I'd be glad to help flesh out and implement this feature if desired.