https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

The updated and correct new url would be

https://specifications.freedesktop.org/basedir/latest/

I don't know where to change this, so someone who does please update the link.

실수에 대해 사과드립니다. "SOMI"가 정확하고 존재하는 페이지이므로 혼란을 피하고 일관성을 유지하기 위해 "somi"를 삭제해 주시겠습니까?

귀하의 시간과 도움에 감사드립니다.

I updated my email address on https://sso.pcgamingwiki.com/auth/realms/PCGamingWiki/account/#/personal-info . Next time I logged in the same page it asked me to confirm the verification mail, after doing which I can see my new email on this sso page as expected. I can also see the new email on https://community.pcgamingwiki.com/settings/  as expected.

But on this page https://www.pcgamingwiki.com/wiki/Special:Preferences#mw-prefsection-personal section "Email options", it still shows my very old email with its confirmation date. Also, on page https://www.pcgamingwiki.com/wiki/Special:Preferences#mw-prefsection-echo section "Email options", it still shows my very old email, and the link Change or remove email address) says invalid special page.

Is this expected account behaviour or something I'm missing from my side?

Regards.

But I'm actually User:BRR. (all uppercase) 😔

https://www.pcgamingwiki.com/wiki/Special:Contributions/BRR

[compimg]http://pcgamingwiki.com/images/4/49/Hamiltons_Great_Adventure_-_Cover.jpg|http://pcgamingwiki.com/images/thumb/4/49/Hamiltons_Great_Adventure_-_Cover.jpg/282px-Hamiltons_Great_Adventure_-_Cover.jpg|282|402|q98|q80 - Wiki thumbnail[/compimg]

JPEG artifacts are visible all over the image, mainly on Hamilton's shirt and collar, on Sasha, and in the black area around the letters on the bottom.

Increasing the quality to q93 using Irfanview removes all visible compression artifacts at the cost of double the filesize:

[compimg]http://pcgamingwiki.com/images/1/19/Hamiltons_Great_Adventure_-_Cover_q93.jpg|http://pcgamingwiki.com/images/thumb/4/49/Hamiltons_Great_Adventure_-_Cover.jpg/282px-Hamiltons_Great_Adventure_-_Cover.jpg|282|402|q93 - 75 KB|q80 - 38 KB - Wiki thumbnail[/compimg]

The increase in filesize would be less for images with less visual complexity, such as screenshots of in-game menus.

For completeness, here is the difference between q98 (original) and q93:

[compimg]http://i.imgur.com/E0oQOxw.jpg|http://pcgamingwiki.com/images/1/19/Hamiltons_Great_Adventure_-_Cover_q93.jpg|282|402|q98|q93[/compimg]

The difference is almost imperceptible. 

I suggest a quality of somewhere between 90 and 93 as being a good tradeoff between visual quality and filesize. Note that q93 might be slightly different for media wiki than it is for Irfanview. Some trial and error might be needed.

gogwiki.com has been in read-only state for a long time. Despite being out of date, the list was a great resource for me as I wasn't even aware that many of the games (Colin McRae Rally 2005, Cryostasis, Second Sight, XIII, Death Gate) have received a digital release. I hope that the page can be officially moved here.

I've cloned the page on my profile, updated two games which have been returned for sale.

I tried to add a new "Latam Spanish" but i have not access to edit templates.

The correct would be to rename "Mexican Spanish" to "Latam Spanish". Because the latam spanish is neutral, is not mexican. Even when some games are dubbed on mexico they are on neutral spanish (latam spanish) not with mexican accent.

Is like to set the name of English to "USA English".

If not possible to rename to Latam Spanish, could someone create Latam Spanish? Actually games like Batman, Tomb Raider and a few others have Latam Spanish/Latin American Spanish as voices.

Here is an example:

https://pcgamingwiki.com/wiki/Glossary:Sound_card#Creative

Additionally, I had similar issue before, without archive.org, but with many links posted in discussion page.

I needed to write the whole response on Google Docs, then short the link, and delete https and spread the link to avoid it being detected (though blocking goo.gl seems to be a good thing, though docs.google.com link not really)

This is the response which couldn't go through:

https://docs.google.com/document/d/13X6_4OIeTsrl1xbiEae-kFpBIjn9rvPuKDLenCz959E/edit

It was here: https://pcgamingwiki.com/wiki/Topic:Ujr171qd2l17r8i8

I'm wondering if anyone else can think of any mass edit type actions that the wiki could benefit from?

Individual store pages are great because each store has their unique quirks (e.g. Amazon.com digital games can be bought from any country, you can activate Ubisoft games on Uplay using a hack, etc.)

However, we should try to standardise some of the information, by implementing a new table - e.g. Template:Digital Distribution Table

Some things to checklist:

central client - does it have a client for buying?

patching - automatic patching?

standalone installers - does it offer as an alternative?

international/regional - can you buy or activate the games from another country?

Interested in hearing what else would be involved.

It would be helpful to have a property so that we can build a proper list (instead of this manual one: https://pcgamingwiki.com/wiki/List_of_games_on_Xbox_Game_Pass)

Xbox Play Anywhere - also a property to show cross-platform Xbox purchases - so that we can standardise this notes field. This isn't 100% identical to the Windows Store property, but will have a lot of overlap. 

Thoughts - advantages/disadvantages?

http://hastebin.com/dozayizuxa.css

I can't fix the notifications color issue when hovering on a link though, seeing as most links on the wiki use the same class.

We are looking for an enthusiastic and talented server administrator to help maintain our website, including:

• MediaWiki - which powers the main wiki where 90% of traffic comes

• IP Board - which runs our forum, blog and files download system

Job specifications:

• Update and maintain MediaWiki and IP Board

• Maintain installed MediaWiki extensions such as Cargo/SMW

• Maintenance of regular automated backup

• Maintenance of other aspects including the dev site, Matomo (analytics) and ‘sidewikis’

• Other bug fixes and requests when required

• Keeping documentation up to date

• Provide basic training for a backup secondary administrator

Essential technical requirements:

• Basic Linux knowledge

• LAMP stack

• Some MediaWiki experience

Desirable technical traits:

• Experience of hosting other similar projects will be an advantage.

• To see examples of problems that the server admin might need to address in the future, see our Trello board.

Tech stack:

• “high availability”

• Ubuntu

• mySQL/MariaDB

• Apache

• PHP

• Varnish (caching)

• HAProxy

• Hetzner (cloud hosting) - the new server admin will inherit a load balancing multi server cloud setup

• MediaWiki

• IP Board

Person specifications:

• Have an interest in PC gaming

• Availability to fix emergency downtime in a timely manner

• Good problem solving ability

• Good communication skills

• Available via email, Discord and Trello

• Must follow our code of conduct and be professional, courteous and discreet

• Follow strict best practice for password security

• Speak or write English well

Further details:

This role that will begin December 2018/January 2019, with fully completed documentation and a handover from the previous system administrator.

This is a part-time contractor role which mostly involves light maintenance of existing systems, with most of the work being concentrated on major updates of MediaWiki and IP Board once a year. We are paying for at a negotiable monthly rate (in the low hundreds of USD per month) depending on experience, please get in touch for more details.

Please send either a resume/CV and/or email to andytizer@pcgamingwiki.com

Interviews will begin from December 17th onwards.

If you have a specific question or would like to discuss further it will most likely be fastest to contact Andytizer on Discord via private message.

I've been holding this on for some time adding stuff and keeping it up-to-date with wiki templates, but now I'm not sure what could be improved/added so I'd appreciate if someone has some FEEDBACK
AA Test article
 
Changes:

• Listed all known AA methods
• Used the info icons to make everything cleaner
• Divided them into Traditional and Post-Processing
• Added info about their developers and GPU support
• Added several new references to everything I could. (More may be needed and maybe less "biased" ones)
• Removed Nvidia Inspector flags and moved them to Nvidia Inspector article

Some things to note:

• Comparision images still use the old-ass image template and ugly wiki tables. I am not sure if the new templates can reproduce them without being overly huge or aligned to right
• Types of Anti-Aliasing isn't prettiest, but I think it should stay in some form
• ATI/AMD specific stuff needs to be looked over by someone who owns either as I can't verify anything as Nvidia user

Post any suggestions here in this thread please and DON'T EDIT THE ARTICLE DIRECTLY ELSE IT'LL GET MESSY

Related threads:

- https://community.pcgamingwiki.com/topic/1880-steamworks-drm-in-articles/

- https://community.pcgamingwiki.com/topic/1075-analysis-why-steam-isnt-drm/

- https://community.pcgamingwiki.com/topic/1640-availability-steam-drm/

Instead of revisiting /exactly/ the same discussion (which were focused on Steam as a DRM) I instead wanted to discuss what /purpose/ the DRM column is currently intended to serve, and how to best go about it.

Right now when you hover your mouse over the DRM column you get the description: "DRM required to play the game"

That description is short, and to the point. It also only cares about >the DRM of the game<, and nothing else. Meaning it doesn't care about launcher, websites, or anything, really. It cares about the game itself and nothing else. This mirrors pretty much what I think all gamers are mostly all about when they discuss DRM: "What DRM-specific restrictions limits my use of the game itself?"

>The game< is the focus. Not how you access the content that makes of said game initially.

I bring this up mostly in the case of where publishers (such as Paradox Interactive with their Paradox Launcher) starts to provide DRM-free versions of their games through their own services. These are games that you can do whatever you like post-download. You can move them to another computer, you can run them offline, you can effectively treat them as DRM-free in every meaning of the word, post-download/install (aka "after you've accessed said content").

It is, I think, dishonest to list games that have no DRM preventing your use of them post-download as having DRM, while then turning around and treating every single title from GOG as "DRM-free", despite those having similar initial limitations albeit in a different form.

Therefor we come back to the question: What /purpose/ is the DRM column intended to serve?

Is it to blatantly push the narrative that GOG is the only place that provides DRM-free games, solely because their download interface "only" requires standard HTTP connection and a semi-modern browser to access? Or is it to actually provide readers with meaningful information on what restrictions and limitations they might face after having downloaded/installed a game?

For example, I can't on good faith list Tyranny and Stellaris as "account-based DRM" on the Publisher row, because neither of those games enforces an account requirement post-download/install. You can take that game folder, archive it, ship it to the most closed off machine in the world with no Internet connectivity, and play the game just fine without ever needing an account or online connection to do so. They are, in every meaning of the word, DRM-free. Yet we're supposed to list them as account-based DRM solely because they require an account during the initial access of said game content (hint, so does GOG) ?

What I believe the average gamer want to know when they discuss DRM in relation to their games are what restrictions are applied >after< having accessed said content. Not what's required of them to access said content initially.

I want that column to basically mirror the copy-protection of a game itself, and not the platform the game is downloaded through. To use a different explanation: if a game could be pirated simply by copy/pasting the folder to someone else then it is in effect DRM-free, and should be listed as such, regardless of how the game was first initially accessed and downloaded.

The current way of treating the DRM column as a mirror of the Source column serves no purpose. Right now if the store is Origin we set DRM == Origin. If the store is Steam we set Steam as the DRM. If it's Twitch we set Twitch as the DRM. If it's GOG we set DRM-free instead (special treatment, woohoo!). And if it's publisher we set account-based instead. This is not helpful for anyone, as the Source column already suggests as much. Nobody cares what hops you have to go through to access the content that makes up the game. What everyone cares about is what restrictions/limitations that content have after you've gotten your hands on it.

Right now, linking to the "list of games with HDR support" page resulted in a massive "wall-of-link:"

http://pcgamingwiki.com/w/index.php?title=Special:Ask&x=-3Cq-3E-5B-5BCategory%3AGames-5D-5D-20-5B-5BHigh-20dynamic-20range%3A%3Atrue-5D-5D-20OR-20-20-3Cq-3E-5B-5BHigh-20dynamic-20range%3A%3Ahackable-5D-5D-3C-2Fq-3E-20-3C-2Fq-3E%2F-3FDeveloped-20by%2F-3FPublished-20by%2F-3FRelease-20date%2F-3FAvailable-20on%2F-3FHigh-20dynamic-20range&format=template&limit=100&template=Feature%2Frow&introtemplate=Feature%2Fintro&outrotemplate=Feature%2Foutro&offset=&mainlabel=

Instead of using this, could we transition the whole template (and all searchable features) over to using defined "list of games with XXXX support" pages instead? So each time a new feature is added, an appropriate "list of XXXX" page gets created as well with the semantic search query embedded, and the feature template hooked to link to that page?

It would have these positive consequences:

- easier-to-read links

- encourages sharing (the current "wall-of-a-link" is not really shareable)

- allow search engine robots to traverse them and make them findable on Google etc (more visitors, more ad clicks, more $$$$$, lol)

- allow us to add basic information on top of the list, sorta like this test page of mine: https://pcgamingwiki.com/wiki/User:Aemony/List_of_games_with_HDR_support

- in case of a very small list, the list could instead be listed in a section of another article, which then the feature template linked to.

I do not know the full scope of the challenge nor how many pages it would affect, but I imagine it's quite a lot. But would it be worth pursuing? "The Lists of PCGW" as I'd like to call them are one of the largest resources PCGW have, and they're sadly currently being heavily underutilized due to various limitations and missed opportunities. This change would bring us a bit on the way to a "list-full" future where PCGW's lists are the links to share, and not outdated PC Gamer links or a similar list on Wikipedia.

The reasons for all this well, seem obvious:

• Preserving gaming history. ATI/AMD's TruForm marks the first time a real-time tessellation implementation was seen in video games.
• Enabling retro games to look their best. When a game's 3D assets were designed around TruForm (i.e. C&C Renegade), it put them a visible step above the competition.
• Unique publicity opportunity. This would be the first major "game fix" project sponsored by PCGamingWiki. Also, more fixes = more visit = profit :P

And there's even more things that in my opinion would be worth to ask to an advanced developer, besides truform:

• Aureal3D sound API
• Proper DirectX ≤ 8 support on Windows ≥ Vista wasn't a windows problem
• Xinput controllers having both triggers working in DirectInput games Xinput plus is a thing

Then of course there would be plenty of channels where the "offers" could be advanced: Reddit, Wine mailing lists, Vogons are the first which come to my mind
So, is this somewhat feasible? Am I asking too much?

Thanks for reading

• Availability on its own not just row.
• Language in its current state is just "row". There should be whole one too as in Sample article.
• Image shortcut still uses [[File:]] instead of {{Image|}}
• {{code|}}

1. Paragraphs don't look like they should. There's currently no visible margin between them, so they look like line-breaks instead. There should be a margin of about 1em between paragraphs inside texts.

2. If you view the site in fullscreen, the lines of text stretch across the whole screen width, which makes reading hard. I suggest to put in a max-width of around 800px for at least p, ol and ul.

Those two points would already go a long way to improve readability. If you want explicit CSS rules that work across the whole site without breaking stuff, I can provide those.

So technically this is correct, you can force at least basic FXAA, AF and force enable/disable vsync in 99% of cases. Question is that should this be considered as hackable method at all? I would almost say that only if it's for some reason not possible to use GPU panel or it needs some extra steps like differend DX mode or compatibility flags, field should be left either true/false unless game has some game specific methods for things. Because if this was standard thing for all articles, there wouldn't be false status on any articles. 

Another one is borderless fullscreen mode. It's nice to have that kind of info available, but at least my testing with borderless fullscreen software has been that basically all games supporting windowed mode works with it, so it would maybe be better to only mention those programs if they do not work for some reason. 

Affiliate links are fine and I presume that are the largest single source of revenue as well.

The ad networks don't curate or verify the ads their customers want to run and malware occasionally spreads via internet advertising, in addition to obvious personal data exposure. PCGW uses at least doubleclick.net.

The actual size is ~ 2,6 GB after downloading. Is the size rounded?

example: https://community.pcgamingwiki.com/gallery/album/117-deadly-premonition-brightness-setting-comparison-pcps3/

.xom, .sve, .pro, .cde, .fqh

The website doesn't allow uploading such files and I have to compress them for no real reason. Can the file type restrictions be disabled completely? I tried uploading `SaveGame.xom` today.

Feeds:

USD: https://s3.amazonaws.com/gmg-epilive/US%20Dollar.xml

GBP: https://s3.amazonaws.com/gmg-epilive/Sterling.xml

EUR: https://s3.amazonaws.com/gmg-epilive/Euro.xml

Seen a few listings with games with top view having the unknown variable in that option, I wonder if N/A is a proper choice for those games.

Besides that it would also help recognize which library the Linux user needs to install in order to either get the game to work or compile the the binary file in case if the games source code is available (Such as Aquaria).

Key points summarize important information regarding a game. What is considered important varies from game to game, but there are some general rules to follow:

• Key points are reserved for very important points. Each article should have at most 5 points.
• The points provided should be information that regards major issues with the game (compatibility issues, critical bugs/crashes, non-functioning multiplayer, etc.), invasive DRM, availability enhancements/limitations, and any possible benefits (free game, open source, community activity, etc.)
•  As mentioned earlier, any point that could be considered subjective must have a reputable reference.

examples in articles (note that usernames in revisions aren't related):
http://pcgamingwiki.com/w/index.php?title=Watch_Dogs_2&oldid=310275
http://pcgamingwiki.com/w/index.php?title=Gears_of_War_4&oldid=313741
http://pcgamingwiki.com/w/index.php?title=Forza_Horizon_3&oldid=309888

http://pcgamingwiki.com/w/index.php?title=Prince_of_Persia:_The_Sands_of_Time&oldid=322326

http://pcgamingwiki.com/w/index.php?title=Half-Life&oldid=312250

https://pcgamingwiki.com/w/index.php?title=Viva_Pi%C3%B1ata&oldid=310797

https://pcgamingwiki.com/w/index.php?title=Black_%26_White_2&oldid=412793

I think that certain subjective key points such as "a good PC port", "great performance" and "lots of options" shouldn't be added - users can make their own conclusions based on the available information. I try to remove them from articles, but some users keep reverting my edits and I won't engage in "editing wars".
There has been some quite incomprehensible ones such as "Doesn't suffer the issues of previous Ubisoft PC ports" for Watch Dogs 2 (still on the front page as the featured article information is perhaps only fetched once).

Do you agree?

http://community.pcgamingwiki.com/files/file/835-condemned-criminal-origins-missing-sounds-fix-steam/

http://community.pcgamingwiki.com/files/file/874-silent-hill-2-fmv-enhancement-pack/

Motivation: we all know that for most games (except games like CS:GO) achieving a FPS over 60fps (60hz monitor in this case ofc) will make NO difference than having it capped at 60, and causes computers to render frames that never gets used, also causing computers to run hotter and more. I know that v-sync does the job but sometimes you just don't wanna use it.

pls fix 👌