Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Nicereddy

  1. I've been really busy with college, haven't been able to work on the wiki much. Sorry guys.


    I'll try working with Soeb over the weekend to get the skin open source'd on GitHub so others can contribute fixes if they're so inclined. Otherwise, it may be a bit before things get fixed. I realize these are relatively simple fixes, but my time has been almost entirely eaten up by other commitments lately. Again, apologies.

  2. When I started following the editing guide creating a new page and saw some inconsistencies between the sample article and editing guide, I saw some differences between the two and made a thread about it in sample article's page.


    However, I started seeing more differences and inaccuracies between the two, so I thought a forum may be a better place to discuss it.


    I'm going to list what caught my eye, but I'll also list the things that should be fixed in both of those places, since both of them are for view only:

    • "wikipedia" and "winehq" places are swapped in infobox; it's in different order in sample article's cheat sheet than it is in editing guide
    • "steam appid side" parameter is missing in the sample article's cheat sheet
    • square enix cloud syncying option is missing in save game cloud syncing table in sample article's cheat sheet
    • API and middleware tables are missing in the sample article's cheat sheet, seems it was already mentioned before, but not answered AFAIK. They are in the base article body though and editing guide does not say anything about the tables being optional
    • Sample article's cheat sheet for series pages uses {{SUBST:PAGENAME}} while the editing guide do not use it
    • Sample page's "genre information" links to the now-dead Style Policy page
    • links in "General information" in sample article does not match what the editing guide recommends (i.e. GOG links should be over Steam links). Editing guide does not mention nothing about the point: "If still relevant, state where bugs can be reported."
    • A small discrepancy in availability type, in example GOG.com is written as Gog.com (no uppercase)
    • The "Which is the 'best' version of the game to get?" under availability point is not present or explained in editing guide
    • I'm a bit puzzled about the patches section in essential improvements. Editing guide is really vague about it, only saying to place "Patches (both official and unofficial)", while sample article says [only?] "Include If There is a benefit in using an older patch". For example Brigade E5 is patched to latest 1.13 version on Steam, but my retail version is not. Following what the sample article says, I should not upload a link to patch 1.13? Or should I anyway? I'm confused x.x
    • Intro skip methods section is missing in sample article entirely
    • The order of utilities and modifications is swapped between sample article and editing guide (patches-utilities-mods in sample article vs patches-intro skip-mods-utilities in editing guide)
    • Configuration file(s) location table is missing in sample article body (not cheat sheet), and while we're at it, cheat sheet (and editing guide) says "Save game data location" while body simply "Save game location"
    • Some of the newly added table options are missing the appropriate "See <something>" section and matching headers. While we're at it, should we always use "See <something>" instead of just fill the notes, or only for really long explanations? Nor sample article or editing guide explains it
    • Sample article does not use the new way of treating fan translations for Spanish example
    • Creative Senz3D table features "class="generic-table-notes-cell" colspan="2"|"
    • "Other information" guidelines differ in sample article vs editing guide

    P.S. There are other minor differences between the two, especially when it comes to the formatting of missing data in cheat sheet - for example sample page's cheat sheet fills steam id with "000000" while they are blank in editing guide. Those are less of an issue, as they will get replaced anyway and will not reflect the final page's look in any way.

    Thank you for taking the time to give us this feedback. When you've edited the wiki for so long, you stop noticing all these small issues, good to have a new pair of eyes on it :)

  3. Apologies for taking so long to get around to this, been busy with college stuff.

    • Fixboxes have better vertical spacing between lines now.
    • The Recent Changes page has much better vertical spacing now.
    • Soeb fixed the DRM sidebar.
    • I think I've fixed some of the font weight issues people were having, not able to test without a Windows computer, unfortunately.

    I haven't fixed the infobox yet because that's a more complex issue than the others, I'll try and get around to it soon.

  4. ThatOneReaper requested they be changed back to blue during the skin's development, and I didn't feel too strongly about the white background being inherently better. As this is entirely a matter of preference, I'd like to see if one is preferred over the other by the community. Feel free to chime in with your preferences, everyone.

  5. Another thing. Why is Warner Bros. Interactive Entertainment on 2 lines? In old skin it fit just perfectly. I assume OS X, Linux in that image is same issue. As seen on Arkham Knight page.



    (btw sorry for hijacking this thread, but didn't want to make new one for regressions :()


    Some other spacing issues I thought had been seen but I guess not.



    Is this ever going to be fixed?



    I've taken note of these three in the issue tracker, will see about fixing them tomorrow when I have more time.

  6. I'm not alone i'm guessing in that I was very fond of the old site layout and format on Windows/Firefox. And I am sad to see it go.


    I will adjust however. One thing I really miss a lot is seeing the latest edits right on the front page. But like I said. I'll adjust!


    Thanks for the work.

    Thank you for having an open mind :)


    I'll miss the edits on the front page as well, I'm kind of thinking we should bring them back, or at least make a link to them more prominent.

  7. I'm going to have to agree with Ratchet with regards to the line height issue on Recent Changes, with more padding it's much more readable IMO. I'll add that to the bug tracker, bug me about it if it isn't changed by the end of the weekend.


    With regards to the other comments, I'm more than open to criticism, and I don't mean to imply that my work is "infallible", but certainly there are more productive ways of giving feedback than telling us "it doesn't look very finished yet"? Soeb and I have developed this entirely in our free time over the last seven months, and it is discouraging to see this kind of reaction.


    I was told the font rendering was a problem, but never directly, and I tried repeatedly to fix the problem, but unfortunately the CSS font-rendering property, messing with letter-spacing, or switching out the font never seemed to fix things. As I've recently started college, and only have my MacBook with me, I have no access to a Windows machine to test with. Unfortunately, because of this I'm not able to fix the issue myself at present.


    We intend to open source the skin within the next few days, so if anyone wants to submit a patch to try to fix it, that'd be greatly appreciated. Currently I'd like to avoid using a fallback to Helvetica/Arial as a fix for the problem, if possible, but unfortunately we may have to do that. This brings with it its own problems, as Helvetica has different line height, letter spacing, etc. than Open Sans.

  8. Was the new design never tested on anything else other than Chrome and Mac? The font rendering looks completely different on Windows. Some elements are pretty much broken on Firefox.

    It was tested in Firefox on Mac and Firefox on Linux as well. The font rendering problems are caused by Windows' font rendering, and can't be fixed without messing up the text for OS X/Linux users.

  9. After more than six months in development, we’re very happy to announce that our new PCGamingWiki skin is ready for release!


    The skin has been developed primarily by our admins Nicereddy and Soeb, who handled the front-end design/development and back-end development (server, MediaWiki upgrades, etc.) respectively.As always, you can support our work and help pay for the site's hosting costs by becoming a patron on Patreon. It'd be greatly appreciated!


    What's new

    A lot, to the say the least!


    Faster load times, decreased content payload

    The home page, for example, has gone from 92 requests, more than 1000 KB of content, and a load time of 8.97 seconds all the way down to 26 requests, 686 KB of content, and a 2.33 second load time. A huge performance gain!


    Game article pages have also seen significant improvement. Our article on Half-Life 2 has gone from 76 requests, 443 KB of content, and a load time of 4.47 seconds down to 26 requests, 370 KB of content, and a load time of 2.60 seconds.


    Your load times may differ slightly depending on network speed, how hard our servers are currently being hit by traffic, and device/browser. The above statistics were the average of 5 tests each in Chrome 43, with a logged-in user (therefore without ads) on August 23, 2015 using a 2014 Retina MacBook Pro.


    Based on Google's PageSpeed Insights test, we've made significant strides with regards to speed and UX on all platforms. Our previous home page's scores on Mobile Speed, Mobile UX, and overall Desktop were 64, 60, and 74 respectively. With the redesigned home page, the scores for Mobile UX and overall Desktop have become 96 and 82 respectively, an increase of 44 points overall! Mobile speed hasn't changed – and therefore isn't listed - because the majority of the points knocked off are from ads, which causes the score to jump randomly between as low as 55 and as high as 72.


    How did we manage to get such an insane speed boost?

    There were a lot of places where the wiki wasn’t doing things as optimally as we would have liked. We used separate files for every one of our icons, embedded information about posts on our forums in the sidebar of every page, and had a lot of extra, unnecessary stuff left over by MediaWiki.


    In order to decrease the number of resources browsers download to load our articles, we’ve embedded almost all of our icons into the CSS stylesheets, combining dozens of files into one stylesheet.


    We’ve also optimized the icons to be as small as possible while still looking essentially the same, credit to Soeb for his painstaking work on that front.

    A lot of unnecessary resources have been cut off, which also contributed significantly to the savings.


    Mobile support with responsive design

    We want to make our content accessible to as many people as possible, so now the site is optimized for mobile devices as well as desktop. If you run into a problem with a game, it’s probably a lot easier to get on your phone and follow a step-by-step solution from there than it is to constantly switch between your browser and a game. Or if you’ve got a Steam Machine hooked up to your TV, checking for a fix on your phone is a lot easier than trying to use the built-in browser/keyboard with a controller. There are lots of other use cases for PCGamingWiki on a phone or tablet, and we think this’ll be pretty useful for a lot of people.


    This also makes us, at least as far as we know, the first wiki ever to utilize a fully responsive design! Responsive design means that everyone gets the same content, no "m.pcgamingwiki.com", the content just changes to better fit the browser window.


    Editing guide

    After a year of work, ThatOneReaper deserves a huge amount of recognition, as well as congratulations, for his efforts in creating a comprehensive guide to editing PCGamingWiki. After multiple unsuccessful past attempts by other editors, this is a big deal, and will be a great help to future editors. Thank you to everyone who contributed to its development over the last year with their feedback and suggestions! If you’re interested in contributing information and fixes to the wiki, the Editing Guide is the perfect place to start.


    Comparison images




    Home page






    Half-Life 2 article





    Borderlands 2 Input Settings





    Donate page





    Mobile site

    Posted ImagePosted Image


    Miscellaneous improvements

    The header's user information has been condensed into a simple dropdown userbar, heavily inspired by a cancelled Wikimedia extension built for Wikipedia. The Table of Contents has been moved to a floating button which expands when pressed. If you're not a fan, this feature can be disabled in Preferences. Clicking images now opens them in a lightbox, thanks to the MediaViewer extension. And of course, every aspect of the wiki's design has been polished, improved, and iterated upon.


    Thank you

    Thank you to each and every of our editors – whether you’ve made five edits or five thousand – your contributions are greatly appreciated, by other editors as well as the community as a whole.


    If you’d like to support us, and help us better serve you all with faster servers, better loading times, and more comprehensive coverage of new titles, we’d love for you to check out our Patreon.


    Thank you for the tremendous support over the last three and a half years, we hope this update helps make the wiki even more useful to the PC gaming community.


    - The PCGamingWiki Team


    Click here to view the article

  10. We don't have such a list.


    The wiki is meant as a neutral database for PC games. Having a list that shames specific developers would go against our base ideology.


    There's also the issue of what can be considered "shady". Not every potential case is clear cut.

    Pretty much this. We try to remain neutral in most cases.

  11. At that point, I would say bigger point would be that program isn't updated in years, instead of it not being foss. They are still selling the product, so in their eyes of course open sourcing it would seem bad at least at the moment. Also that if program isn't updated in long time, userbase will slowly move away when there's newer, better and more modern alternatives available. Just shame with many cases it seems to be bandicam for some bloody reason... 


    I would say that if there are several similar programs available, where one is open source, It's good to be noted. That's the reason why I use 7zip over winrar personally, rar is awful format in that front. But having negative note on every proprietary program would simply be insane. I would also say that programs like steam are in state they basically can't be open sourced and there can't be alternatives. 


    I disagree with it not being possible for the Steam source to be released. If they have some proprietary third-party software embedded inside, that I can understand, but Valve has done quite a bit of open source work in the last few years, I don't think Steam is necessarily an exception.


    The value of Steam isn't really in its client, that thing barely works half the time (on OS X, at least), it's in the selection of games, sales, friends already on the service, and features which can't easily be duplicated, e.g. Steam Workshop. Open sourcing it shouldn't really hurt their bottom line.


    Admittedly though, based on my attempt at making a skin for the Steam client once upon a time, I'm not sure I even want to see the source to that thing :P

  12. I'm unsure how to feel about this. The copyright of abandonware titles isn't technically owned by anyone, as the company who made the game has been dissolved, shut down, etc. So we can't be sued by anyone, technically.


    That said, it's still not legal to cover, and is something we should be wary of condoning for caution's sake.


    Also, I am not a lawyer.

  • Create New...