Category: meta

As the Classic fever was building, I enjoyed reading Belghast’s excellent post on communication and admiring the great screenshots from his early Warcraft days.

It made me want to dig out my old screenshots from Burning Crusade, but unfortunately they were locked away in Picasa somewhere. I had assumed that they were lost forever due to Google sunsetting Picasa some time ago, but a small amount of research revealed that you could still get them if you could logon to the Google account associated with your Picasa account. Luckily enough I still had that logon and before long I had recovered all the pictures.

Now that I had the images, it seemed like a good time to reconstruct the old guild blog, which was a two year history of my first Warcraft guild and our adventures in Burning Crusade, Wrath of the Lich King, and, in particular, Karazhan. The blog was also on a Google property – Blogspot. But the broken images made it no longer useful, plus Google’s propensity to shut services down meant it could disappear at any time. It was the same account as Picasa, so I could easily logon and download the post history as an XML file.

I decided the best plan would be to try and migrate the blog to a static Hugo blog and host it on a Galumphing subdomain, which would mean merging the Blogspot text with the Picasa images.

Thanks to the internet magic of 2019, there are plenty of tools for doing the Blogspot to Hugo migration. The most promising looked to be this Blogger to Markdown tool written by palaniraja on Github. I installed it on a Mac and it worked flawlessly, miraculously producing a directory full of Hugo formatted markdown files. It even had a very nice feature that merged the blog comments into the single markdown post file, making it much easier to publish as a static archive of the original blog (comments being the bugbear of static site generators).

Next I followed the very simple Hugo Quick Start steps, and was very surprised to find it worked first time. I chose a theme – Solar – that was similar to the original blog, and before long had the site up and running locally and started configuring it in real-time with the Hugo server.

I did a pass of comment formatting (some of the dates were a bit mangled), and tweaked some of the settings – publishing the full test of each post instead of a summary, and putting it in chronological order so you could read it from start to finish (which is the reverse of a standard blog setup). I also added Wowhead tooltips for good measure, which slows things down marginally on load but with a static site it seems a fair trade-off. Otherwise I left it as it was.

The final step was merging the local images back into the blog. That was unfortunately a more manual process, as I had to remove a lot of Picasa HTML cruft, but it didn’t take too long with some judicious Notepad++ mass replacements.

I published the site again, and there it was: Midnights Children, in all it’s non-apostrophed glory. Just seeing it again hit me with a huge nostalgia wave, and reading the posts complete with images of glory and despair was even better. There’s probably only 5 people who are still interested, but for them it’s a reminder of a special time and a special friend.

Epilogue

Coincidentally after doing all this, I read that UltrViolet at Endgame Viable was embarking on a very similar project, albeit more about consolidating multiple online identities and blogs.

I totally agree about the WordPress dilemma – it’s a great platform in a lot of ways, but it’s very slow and kind of stodgy, especially when compared to static sites. It is however very easy to setup, has a strong support ecosystem, and importantly has integrated comments and associated spam protection (assuming you want comments, that is).

I was tempted to move this blog to something simpler, but stumbled trying to find something that elegantly incorporated comments. Disqus seems to be the most common choice, but it seems to have pretty major privacy problems, and all the open source commenting engines seem pretty flakey and hard to configure and maintain.

Like UltrViolet, I’ve stuck with WordPress, self hosting and using Markdown for writing the posts (so it can easily be migrated if need be), and disabling the frustrating new block editor. I even did a test migration of this blog to Hugo using the same tool as above and it worked just as well. Which gives me confidence that I’m not super locked-in should a nice simple option present itself.

I wish Endgame Viable well! It was certainly worth the time for me, though this was more an archival project than a living blog.

#Blaugust28

One of the questions I had when pondering the rare mob collection project was how to improve the quality of the screenshots – pictures or it didn’t happen, after all.

After a bit of hunting around, I found that there a few console only settings in Warcraft related to the screenshot quality. If you type these commands in the chat window and press enter, they are changed permanently everywhere. (You don’t get any feedback that anything happened, but it does work.)

The first is choosing between JPG (the default) and TGA. TGA is a lossless format, so the image quality is higher and non compressed, but it is a fairly arcane format – you’d want to convert it to something more useful like PNG to use it on WordPress et al. In any case, the command to change it to TGA is:

/console screenshotFormat tga

And to switch back to JPG:

/console screenshotFormat jpg

Sticking with JPG is more convenient, but the default quality is pretty average. The good news is there’s another console setting that bumps up the JPG quality until it’s barely different from the TGA files (confirmed by much internet commentary). Wowheads screenshot submission guidelines state the default JPG level is 3, but we can bump it all the way up to eleven 10:

/console screenshotQuality 10

I tried this and while the difference is noticeable if you look closely, it’s not as huge as you might expect. One byproduct is the filesize grows from about 500KB to 2MB, but with some judicious resizing the filesize gets more reasonable.

So it seems changing the quality setting is not quite enough. Which means learning more about doing some post processing on them. There are some great photography-inspired tips in this excellent article on Blizzard Watch which seems a good place to start.

Aside from the framing tips, the main advice seems to be about adjusting colours and contrast, to get the details to really pop and sparkle. The main problem I see is that the screenshots are too dark, so I played around with an image of our second RFC run to see what could be done. Here’s the default shot:

Using Irfanview (which admittedly is more of a viewer than an editor), I mucked around with adjusting contrast and saturation, but in the end found that the ‘auto adjust colours’ setting did a pretty good job:

Finally I used the ‘sharpness’ setting to see what that would do:

Hm. I like that you can see more once it’s adjusted, but it does wash it out a fair bit. I guess using the default settings isn’t a great plan – more to learn and more experimenting to come. Either that or I should just start taking screenshots in daylight…