MV, Steam achievements & You (And also how to update nw.js!)

SGHarlekin · 2025-02-09T09:40:20+0900

I've seen a bunch of people still struggling with the easy task of getting steam achievements to work, so I'm going to attempt to write somewhat of a guide here. I've currently got 2 games on steam, both with working achievements. So let's begin. https://github.com/greenheartgames/greenworks/releases This is the greenworks.js. Put that into your game's main directory, not plugins. The build releases say for which nw.js and steamworks sdk they are. If you can't find your nw.js version here, it's time to update your nw.js. Essentially navigate to https://nwjs.io/ , hit downloads>previous releases, scroll down to the version you want. (in my case v94.) Download both of the links which are purple in this screenshot. The "sdk" version goes into your nwjs-win-test folder, the regular version goes into your nwjs-win folder within your rpg maker files (Not your project folder!). "Sdk" has the dev console enabled, the regular doesn't. When updating, delete the contents of your nwjs-win/nwjs-win-test folders, but keep the package.json in nwjs-win and keep the www folders in both locations. Unpack the freshly downloaded nw.js version into their respective folders, rename the "nw" file to "Game" and done. A little extra tip: With newer nw.js, it is possible that the game will tell you something about a "name" missing. To fix that, go into your project folder, open the package.json with something like notepad++ and enter anything under "name". Pro tip: Using the x64 files makes your rpg maker game be able to use more than 4gig of ram! Now back to the achievements! https://github.com/Hudell/mv-plugins This is the actual plugin by Hudell. Put into your projects plugin folder, activate in plugin manager. It's missing the help file, that's why there's this shifty looking google drive link that contains this help file in the form of an html document: OrangeGreenworks Documentation.rar Now we need the actual steamworks SDK files: Steamworks - Build & Distribute Your Games on Steam Steamworks is a set of tools and services that help game developers and publishers build their games and get the most out of distributing on Steam. partner.steamgames.com this is only accessible if you got a steamworks account as far as I'm aware, but you should be having one of those already if you plan on releasing anything on steam. Download the version that's matching the greenworks files you downloaded with the first link of this guide (In my case 1.6). in this archive, you'll find all the necessary lib files. Navigate to steamworks_sdk_160.zip\sdk\public\steam\lib and you'll find these folders: Navigate to your project and create a folder named lib in your main directory, then navigate into each of these folders on the screenshot and copy the files inside into your projects lib folder. Be aware that you'll have to rename the linux x64 file to libsdkencryptedappticket64, otherwise it's going to overwrite the regular linux file. Next, navigate to steamworks_sdk_162.zip\sdk\redistributable_bin\win64 and put those 2 files into your project's lib folder as well. (If you're trying to develop for another OS, you can add those in the other folders too.) If you don't plan on making a linux / mac release, you can skip all of them except for the windows ones. (guide on how to release on linux/mac not included) If you have not yet created an appid (meaning you haven't shilled out the 100 bucks yet), you can create a text document named steam_appid and place it where your greenworks.js is located. Inside that text document put the number 480, which is used as a placeholder appid for games not yet submitted to steam. Note: Do remove said .txt file once you actually deploy your game. (Thanks to @emogal for finding out this detail.) Once you got all that done, open rpg maker, make sure your orangegreenworks plugin is activated, start your playtest and open the dev console (F8). If it says Steam user: "YourSteamUsername" it's good to go. Bonus tip: Navigate to the steamworks setting of your game, installation>general installation and add this as an argument: This will enable the steam overlay for your game. And that should be it. If you're still not able to have it working, let me know.

● ARCHIVED · READ-ONLY

Started by SGHarlekin Feb 9, 2025, 12:40 AM 25 posts Page 2 of 2 View original ↗

Arcaines

#21 Aug 20, 2025, 03:16 PM Source

Hey Harlekin,

So I followed the guide, the best I could, (Kids distracting me)

I've got the game to play but when I press f8 I get this on the console log. No mention of my steam name.

It mentions it's missing something but it's in the right folder?
SGHarlekin

#22 Aug 20, 2025, 04:33 PM Source

Martin_Arcainess said:
Hey Harlekin,

So I followed the guide, the best I could, (Kids distracting me)

I've got the game to play but when I press f8 I get this on the console log. No mention of my steam name.

View attachment 347841It mentions it's missing something but it's in the right folder?

View attachment 347842
If it can't "find" the file, the problem is usually the wrong combination of the plugin/nw.js/greenworks. Did you make sure to use the same versions I linked?
Arcaines

#23 Aug 21, 2025, 04:27 PM Source

SGHarlekin said:
If it can't "find" the file, the problem is usually the wrong combination of the plugin/nw.js/greenworks. Did you make sure to use the same versions I linked?

I'm currently using Greenworks v0.21.0 for NW.js v0.100.1 and downloaded NW.js Normal and SDK.
Copied/pasted the Steam SKD 1.62 folders over and I'm still getting this error.

At this point the only thing I can think of trying is a older version.
SGHarlekin

#24 Aug 21, 2025, 04:37 PM Source

Well yeah, as outlined in the guide, you need to use the correct versions. If you don't I can't really help you. :rswt
Arcaines

#25 Aug 21, 2025, 06:04 PM Source

So I tried an older version 0.940 to match yours and playtest ain't even working now. Really am not sure what's up with this.

EDIT:

The only I can seem to get working for the play test is the latest version. All other versions won't even boot up play test.

Edit:

All good and happy now ^^