Using Greenworks for Steam Publishing

29

Index

Tagged

Features on these Courses

Stats

7,536 visits, 18,912 views

Tools

Share

Translations

This tutorial hasn't been translated.

Create a translation

License

This tutorial is licensed under CC BY 4.0. Please refer to the license text if you wish to reuse, share or remix the content contained within this tutorial.

Published on 14 Apr, 2022.

Final Notes

When you've made all the necessary changes, you can re-zip your game folder and it's ready to upload to Steam! Bear in mind though, that the steps will need to be repeated for every platform you plan on publishing to - so if you want your game to run on Mac, Windows32, and Windows 64 for example, you should have three different versions ready.

Remember if you've changed the extension on your package.nw file, to change it back to .nw before publishing!

Finally, when it comes to testing your achievements etc. Greenworks requires Steam to be running in the background with a logged-in user to work. Also, if the app ID is not valid and installed, Greenworks won't work either.

If you want to watch a video from a Construct user who's published to Steam, YouTube has you covered, like this one for example.

Good luck with publishing to Steam!

  • 20 Comments

  • Order by
Want to leave a comment? Login or Register an account!

  • Can you teach how to upload DLCS?

    I have no idea how to do it

  • These flags no longer work for Steam overlay on most recent supported greenworks / nw.js

  • I can't add files to the package.nw files after renaming them to zip files or when using third party tools like 7Zip or Winrar. I can normally add files to other zip files, but these seemed to be locked down.

  • Can this be updated now that NW export includes the Steam options? I have no idea which steps to follow, and which to ignore.

      • [-] [+]
      • 2
      • Laura_D's avatar
      • Laura_D
      • Construct Team Community Manager
      • 2 points
      • *
      • (1 child)

      I currently have quite a big to-do list, but when I get time I'll look into updating it.

      In the meantime, the manual outlines what the Steam options are in the NW.js dialog: construct.net/en/make-games/manuals/construct-3/interface/dialogs/nw-js-options

      So as a starting point, I'd assume you don't need to manually add the in-process-gpu arg if you check Export for Steam.

      The Enable Devtools checkbox should handle whether the game allows F12 to open devtools, so you don't need to add the devtools arg if you're leaving that unchecked I think.

  • Who can help me make a construct 3 for my Game development unit , some one reach out pls.

  • Load more comments (13 replies)