Rise of Nations: Extended Edition

Rise of Nations: Extended Edition

Not enough ratings
How to Add a Thumbnail to a RoN Mod on the Steam Workshop
By MHLoppy
How to use SteamCMD to add a thumbnail to an existing Rise of Nations: Extended Edition mod on the Steam Workshop using a VDF file.
   
Award
Favorite
Favorited
Unfavorite
Introduction


If you've ever tried to browse the Steam Workshop for Rise of Nations, you may have been frustrated at how none of the entries appear to have thumbnails. If you're one of the people publishing mods, perhaps doubly so. I looked into this and it appears that this is because the native mod uploader does not support thumbnails.

Nonetheless, by using a workaround, I became probably the first person to ever have a thumbnail for my RoN mod on the Steam Workshop. Let's run through how I did it.
Disclaimers and alternative viewing methods
  • This is not intended to be a tutorial on how to upload a mod itself to the Steam workshop, for RoN or any other game.
  • The method used works as of publication date - this does not guarantee it will work by the time you read the guide.
  • It is assumed for this article that you're on a modern version of Windows - older versions and Linux users: good luck.
  • My investigation into this was the first time I've ever made a RoN mod, and the first time I've ever uploaded something to the Steam Workshop, and the first time I've ever used multiple things in the method outlined later. This means I cannot reasonably be considered an expert on any of these things.

This Steam guide is a port of the same guide written on my website[mhloppy.com]. If this process ever needs to be updated, I will be prioritising that version of the guide to update first.

This guide is also available in video form:

Please note I have no plans to upload a new video each time any part of this process breaks, as I will instead just update the text-based guides (starting with the "authoritative" copy on my website); please consider the video primarily a visual aid.
Ensure you have an existing mod

As a prerequisite, you will need a mod already on the Steam Workshop. I'm showing you how to add a thumbnail to an existing Workshop item, and this method won't work without one.
SteamCMD setup and login
Since the native method of uploading RoN mods does not support the inclusion of thumbnails (but the Workshop itself does), we're going to have to upload the thumbnail via other means.

First, download SteamCMD, a utility provided by Valve for developers. Unzip the .exe into its own folder - this new folder is about to become the installation location of SteamCMD.

This next step may be partially unnecessary, but without uninstalling it all and repeating the process, I can't know for sure, so I am suggesting the full process.

Open up Command Prompt (I ran command Prompt as admin on my first run, but I don't know if that's required or not unless you're in a privileged folder), and navigate to the folder you just unzipped steamcmd.exe to. In my case this was
D:\Misc\steamcmd

Update: Although I can't verify whether needed for the initial install process, I was able to update the example thumbnail with Command Prompt not running as admin.

TIP: You can change drive letters from C: to D: (or whichever other drive) by just typing the drive letter (e.g. "D:" without quotes), and then use "cd <path>" (no quotes, replace path with e.g. D:\Misc\steamcmd) to change directory to that location.

From Command Prompt, run steamcmd.exe.

If this is your first time running steamcmd.exe, your Command Prompt will fill up with a lot of stuff after you enter this.

Doing this will cause it to download and install a bunch of files, and the progress will be tracked in the Command Prompt window.

Once it's completed, you should end up with a
Steam>
prompt, as you are now running SteamCMD from Command Prompt.


Log into Steam, replacing the below with your username, password, and Steam Guard 2FA code if you have it (if you're not using Steam Guard, ignore the part at the end)

login USERNAME PASSWORD XXXXX

Doing this will sometimes log you out of normal Steam if it's running. I don't know why it's inconsistent, but just be aware that it can happen.
Creating and publishing a VDF file
Next, follow Valve's directions to create and upload a VDF file. This will involve:

  • Creating a blank .txt file (outside of Command Prompt) in the same folder as SteamCMD
  • Putting specifically formatted text inside the file, as shown by Valve
  • Changing the file (by simple renaming, with file extensions enabled in Explorer) from a .txt file to a .vdf file

Please note that within this file, do not remove the quotes unless also removing the text inside of them. The quotes are an essential part of the file's formatting.

Below I've outlined each of the values in the VDF file. Note that some of these are mandatory and some are optional. For lines such as
description
, removing these from the VDF file will simply keep whatever description already exists for the mod on the Workshop. If you keep lines such as this in the VDF file, the new values you're entering here will replace existing entries already published on the Workshop.

    appid
  • For appid, you will need to change "480" to the id of the game your mod has been uploaded for. In RoN's case this is "287450" - in case you need to use this guide for a different game, this value can be found using the game's Steam store page URL or Workshop page. This field is mandatory.

    publishedfileid
  • For publishedfileid, change it to the ID for your mod - as above, this value can also be found by going to your mod's workshop page and looking at the numbers at the end of the URL. This field is mandatory.

    contentfolder
  • contentfolder will need to be the local file path to your mod. For example, this could be D:\SteamLibrary\SteamApps\common\Rise of Nations\mods\Elephant test classical 13e (minutemen). For this and the next field, you may or may not need to use double backslashes (e.g. D:\\Thumbnails\\thumbnail.jpg) - the documentation suggests that you do, but things worked fine for me with just single backslashes. YMMV. For our purposes, this field is not required.

    previewfile
  • previewfile is the thumbnail for your mod. As far as I know, the file can be a png, a jpg, or even an animated gif file. Just make sure the file isn't too large (I suggest definitely under 1MB max, but ideally well under 500KB), and remember that the preview on the Workshop is a square, so you may want to crop your thumbnail down to a square if it isn't one already. I don't know if there's a resolution limit, but I suggest a max of 512x512 or thereabouts unless you have a specific reason to want a higher resolution, since people will only see an image of 200x200 when browsing mods, and slightly higher than that when on the page for the mod itself. This is the thumbnail file, so is mandatory for our purposes (but otherwise optional if you're not adding a thumbnail).

    visibility
  • visibility is the visibility setting of your mod. 0 is public, and I believe 1 is friends only, and 2 is hidden. I'm not sure if you can select "unlisted" with this field via this method, but you could try setting it to "3" and letting us know what happens. Remember you can always change this later via the Workshop itself. For us this field is not required.

    title
  • title is self explanatory. If your title here does not exactly match the existing title on the Workshop, this will become the new title. For us this field is not required.

    description
  • description is the mod's description on the Steam Workshop, and will override any description you have already written for the mod if included. For us this field is not required.

    changenote
  • changenote is the change note that will be visible on the Workshop for this "new" version of the mod. If you only change a mod's metadata (not the mod data itself), then the change will not be considered a new version and this field will be ignored. For us this field is not required.

Here are a couple of example VDF files so you know what they should look like:




After you've completed changing the required fields, save the file, then change it from a .txt file to a .vdf file if you didn't already do so (you'll need to have file extensions enabled to see the file type).

Now we can upload it using the below command, replacing FILENAME with the name of your own VDF file. We're assuming your VDF file is located in your SteamCMD directory.

workshop_build_item FILENAME.vdf

If your VDF file is incorrectly formatted etc, you will see an error such as the one initially displayed here.

Update: For VDF files that include spaces in the file name or file path, surrounding the whole file path in double quotes may be needed.
Finishing up
At this point, your mod should now have a thumbnail, congratulations! Check your mod on the Steam Workshop to verify that everything worked as expected and that the thumbnail is correctly displaying.

To exit out of SteamCMD, use
quit
After it's exited you can close the Command Prompt window.

Closing words
I'd like to make a special shoutout to Roxette on the Keen Software House forum[forum.keenswh.com] for being a goldmine of information for this article - most of the steps I've listed are simply adapted from information they provided for a different game.

After knowing that SteamCMD was a critical ingredient in the thumbnail recipe, I also found guides from [OS] Janine and xdshot covering the same topic. Should both this guide and the "master" version of this guide on my website ever fall into disrepair, those resources may be of use.

Hopefully you found this helpful! You can see my submissions for RoN to the Steam Workshop showing off thumbnails here:
https://steamcommunity.com/id/MHLoppy/myworkshopfiles/?appid=287450

If you'd like to support my efforts financially:
https://patreon.com/MHLoppy
https://ko-fi.com/MHLoppy

Here are my other obligatory links:
1 Comments
Gman Oct 6, 2023 @ 2:10pm 
Thanks very, helpful guide 10/10 helped a lot