Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

User talk:Cptmold

About this board

Not editable

ThatOneReaper (talkcontribs)

Hey there,

Some issues with your recent edits I have to point out:

  • Screenshots of ScummVM and DOSBox options menus are not needed. Such settings are constant from game to game and adding them to every supported game article would just clutter them up. The DOSBox Configuration Tool screenshot is the only exception to this.
    • Screenshots of configuration files are also not required. Such screenshots are more useful when tied with a complicated fix requiring config file modification.
  • Information in all articles should be written up in the context of the original systems they were designed to run on. They should not be written up in context of an emulator/wrapper, as it skews the information given. That is to say: the only settings that should be considered while filling out the tables are the ones that came with the game itself. Don't assume that the reader will be using a specific wrapper/emulator.
  • Related to the previous point, avoid general solutions like the Borderless Gaming app or forcing video settings through drivers. Game articles should only have fixes exclusive to that particular game. General solutions can be given in the relevant table field glossary pages.
  • The directory separator is different between DOS/Windows (\), OS X/Linux (/), and Mac OS (:). It's a minor but critical detail that should always be correct when dealing with multiple paths across OSes.
  • DOSBox-specific paths can be omitted from tables. This ties in with my 2nd main point.
  • For the Afterlife article, I'm not entirely sure if the 70 FPS readout is correct. Is the readout for DOSBox or the game itself?
  • Your screenshots for Enter the Gungeon should be redone if possible.
    • The readout details from MSI Afterbuner/any app overlay should not be visible. They make the screenshots look "busy".
    • The cursor should not be visible in all screenshots. You can hide the cursor by moving it off-screen to the bottom right. If the cursor can't be hidden, move it as far off-screen as possible
  • Just because a table field is not relevant to a game/will never be used, doesn't mean that it can be removed from the article. All non-modular tables must be added to an article in its entirety.
  • Key points like Very easy to run on low-end hardware and Supports the Steam Workshop are not particularly helpful. Key points should be generally game-critical information like multiplayer servers shutting down or a notice about added support for a modern OS (see Diablo II for an example).

Aside from what's on the list, your edits are good overall. Keep it up!

Cptmold (talkcontribs)

Thanks for the feedback!

  • Now looking back, I guess I should have spent a bit more time working on those Enter the Gungeon screenshots, but my first day of a new job was a bit more taxing than I imagined and I probably should have just gone to bed early and messed around with wikis the next morning.
  • In place of ScummVM screenshots, should I simply put down an information bullet saying to go to the engine:ScummVM page for screenshots, or is mentioning ScummVM enough?
  • The Afterlife screenshot was demonstrating the maximum framerate of the game itself. I had some trouble launching the Windows 9x version yesterday, so I figured maxing out the game speed (so that something was happening for every frame) would give you a framerate counter just as accurate. The point was to find what the cap was, and I found that the game could never go above 70 FPS.
  • The error with Mac/Linux format was simply incompetence. I was aware from setting up DOSBox Turbo on an Android phone that Linux based platforms used forward slashes, but I didn't know it actually mattered; for Mac, I had no idea that it used a Colon to divide instead of a Slash.
  • Some areas like Very Easy to run on low-end hardware are, admittedly, something I learned from existing pages of the site. As I used this site a fair amount before having a decent computer, I saw points like these and figured it would be good to have.
  • I'll refrain from deleting template areas from now on. Sorry about that!
ThatOneReaper (talkcontribs)

The best way to handle ScummVM support would be just a small blurb under Key points mentioning said support. The King's Quest articles are a good example of how to denote the support, along with the relevant information.

As for the key points stuff, keep in mind that some articles have not been patrolled and edited since the Editing guide became official. For the longest time, there were no defined rules on what made a good key point.

Better examples of good key points can generally be found in more frequently updated articles.

Concerns regarding your contributions' compliance with PCGamingWiki standards

Anonymous (talkcontribs)

I've been looking through your contributions, and while they're otherwise very good, they don't fully comply with the standards PCGamingWiki has established. I highly recommend you look through the official sample article and editing guide as they provide concise, detailed explanations and examples of those standards.

Cptmold (talkcontribs)

Alright, suggestion noted. Is there anything in particular I'm screwing up on?

Anyway, I'll make sure to take a look. Sorry if I've accidentally been messing things up, I'll take care to follow procedure from here on out.

RaTcHeT302 (talkcontribs)

Nevermind, read below.

RaTcHeT302 (talkcontribs)

Nevermind what I said, there are a few big mistakes, I think he actually wanted you to read the articles and find whatever things you did wrong by yourself but I'll try to help you a bit.

Okay so Key Points are supposed to have their own header.

This is wrong.

This is correct.

One tip which I can give to you is to give unique names to any screenshots you upload.

I have my own very easy to remember format.

{{Image| -  Settings.jpg| settings.}}

All you do is first add the name of the game. Then you take the name of the section you want to add a screenshot at, it should look like this.

{{Image|Interstate 76 - Input Settings.jpg|Input settings.}}

But yeah when I first started I used the sample article as a guideline where things should go, and you should probably try to do that too. So he's not wrong anyway, I think he wanted you to try and learn most things by yourself, seeing as this is what the wiki is mostly about, you'll have to figure out many things on your own in order to get a better idea on how things work, but that's just how anything works in life anyway.

So I'm just going to repeat it again just in case you didn't understand, you really should look at the two links he posted and maybe you can also watch other wiki articles to see how things should be done for the most part.

Here's one of my newest wiki articles where you can see some of the things I did with the images and with the notes.

Ideally you want to keep the notes short and clear.

RaTcHeT302 (talkcontribs)

From what I've seen the guide it isn't particularly clear sometimes though, if some things look strange you should probably ask about them.

Cptmold (talkcontribs)

I'm going to go ahead and stop editing for now, and take a look at the guides provided as well as some recent articles.

As far as file names go, I realized a little too late that it was shared between the entire wiki, so I'll make sure to give it some kind of unique tag (example: interstate76 Graphics.png) from now on.

Apologies for the mistakes, I'll start by correcting errors in the i'76 page based on examples and guides.

RaTcHeT302 (talkcontribs)

Yes but instead you could at least try to follow the format I gave you, the new pictures you uploaded have currently no spaces in them, and you didn't even include the whole Video Settings part, just Video or Controls.

I already suggested looking at the Transformers Devastation page seeing as there's quite a few examples in there but I'll just leave this example here again.

Anonymous (talkcontribs)

I hope the comments others left didn't put you off - believe me, your contributions are most definitely valued, and don't fear breaking something! We all do it from time to time, and since it's a wiki, someone will come around and correct you, if needed.

Just make sure to watch out for any changes others might make to your edits - it'll give you the best idea of what could be done better.

If you're ever unsure about something, even after looking at the guide, open a thread in the forums, ask in IRC, or even ask me directly - someone will always be happy to help!

Cptmold (talkcontribs)

Of course not, don't worry! I'm just a bit inexperienced, and I'm going to take a break until I can get it right. Also, I'm not worried about changes being made to what I write. I simply contribute because I want to help out, and if I do a bad job that somebody corrects and takes the credit for, that's absolutely fine by me.

Anonymous (talkcontribs)

Hi, and welcome to the wiki! I hope you'll like it here and stick around.

Sorry for the quick block and unblock just now - I accidentally caught you with a few spam bots, didn't mean to actually ban you.

Cptmold (talkcontribs)

I didn't notice, so no worries! Mistakes happen.

I signed up just to point out a few things I learned with that Tom Clancy Humble Bundle, but I think I'll be staying around to help where I can on a lot of games I've picked up over time. I really like what you all are doing, and I'll go ahead and say it's helped me out of plenty compatibility issues in the past.

There are no older topics