Category: Guide Writing

  • The Most Annoying Collectible I’ve Ever Documented

    The Most Annoying Collectible I’ve Ever Documented

    The Sword of Kings from Earthbound is the clear winner in this category. A notoriously rare 1/128 chance drop from Starman Super in Stonehenge Base, which becomes unattainable after you defeat the boss there. I went so far as to look into the statistical probability of getting it, and thanks to that, I learned that even though each individual battle has a 1/128 chance, the probability actually gets better over time, simply because “fail fail fail fail fail fail fail fail obtain” becomes less and less likely the more “fails” are in there, if that makes sense. I’m not particularly good at mathematics but I’m fascinated by statistical problems like that, largely thanks to the Sword of Kings problem.

    There’s not much you can do but just keep battling Starman Supers until you get it. Good luck!

  • Revisiting an Old Guide: What I’d Change Today

    Many of my older guides were much more casual and jokey in tone, and many of the revisions I have done involved making it a little more polished. I’ve done away with a lot of jokes, but I left a few in if I felt that they fit with the tone.

    Other of my older guides were just paragraphs without section headings, and in some cases I’ve gone back and added section headings for better organization. This allows there to be a table of contents box with anchor links at the top as well.

    And of course my oldest guides have no screenshots, which is an ongoing goal for me to add.

  • My Screenshot Workflow for Walkthroughs

    My Screenshot Workflow for Walkthroughs

    Many of my walkthroughs were written before I had the ability to easily take screenshots. Now that I have a Nintendo Switch, the screenshot button makes it easy. The hard part is figuring out when to take a screenshot and what to take it of. Overall, since I separate my walkthroughs into pages for distinct sections of each game, I will save the game a lot when I know I’m approaching a transition point in the game, going from one story section to the next, for example. Some games don’t make it easy to save, so I have to be really careful with the timing, otherwise I can’t reload my save for another chance.

  • Why Boss Fight Guides Are Harder to Write Than You’d Think

    It wasn’t until I started playing Final Fantasy XIV that I realized just how much effort a game developer will put into making boss fights actually playable, how much effort goes into balancing playability and challenge. It’s thanks to what I learned by being a player of FFXIV that I came to understand how much structure there is, even in a seemingly chaotic boss fight.

    Prior to this realization, I didn’t have a good approach to a boss fight. It was all just “if the boss does this, do that”. Now, when I play through a boss fight, I keep an eye out for all the cues that game developers put into the fights that are meant to help the player figure out what to do, and I do my best to convey that in the guide.

  • How I Structure a Walkthrough Before Writing It

    How I Structure a Walkthrough Before Writing It

    Since Thonky is a personal hobby project, I take a pretty relaxed approach to structuring my walkthroughs. If I’m working on a game that has a story that goes from start to end, I always plan on have a section specifically for going through the main story. I like to always have a “Beginning the Game” article to walk the player through creating and naming a character, if the game has that, or at least how to navigate the title screen and options, for example.

    If it’s a complex game with side content, I typically plan for a second section of the guide with additional information. Usually it’s enough to just have an “additional information” section, but if there is a lot of content in the game, sometimes I break it up into content-specific sections.