Greengrinds plugin - expanding access to Greenworks / Steam APIs

2 favourites
  • 8 posts
From the Asset Store
Vintage steam pixels for your UI! 125 unique assets in a single pack!
  • C3 Addon Greengrinds

    I added a new free C3 addon to support more Greenworks/Steam APIs (Cloud File, Stats, more Achievement, and DLC APIs), with an example project. I needed this for a project I was working on and decided to share in case it helps other folks who also need more APIs beyond the official Greenworks plugin (which you should definitely try out first, in case that's all you need.)

    Actions and conditions:

    See addon website for more details and documentation. If you see issues please report on the addon's github, so we can track and close: issue list.

    Example project (using the test '480' steam_appid.txt for Spacewar.)

    Other tools used for this project:

    c3IDE - a great IDE for creating C3 Addons

    Electron for Construct - Electron for Construct - a great tool to build Electron executables of your game.

    Thanks to Construct Discord community for support and testing (InsaneHawk, Armaldio, Piranha305, Chadori, Erigatoshima and others!)

  • Cool addon Mikal. You implemented more features than the official Greenworks plugin by Construct Team. The original one wasn't usable, it's great that you have changed that and allowed real implementation for Steam games on Construct 3.

    I hope this encourages people to make Steam games on Construct 3 now.

    Very well done! ✨👍

  • thank you for sharing. it looks better than official greenworks plugin.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Well, I'm going to have a very deep look at your plugin since I really want to publish my next game on Steam with achievements.

    Thanks for this gem, and those detailed explanations!

  • Update: release

    • Added ResetAllStats (reset_achievement) API ACEs (not documented yet on the Greenworks docs, but I can see it in the source and it seems to work.)

    Thanks for the comments also, appreciated.

  • Update: release

    No change to ACEs. Changed electron path to greenwork.js and greenworks / steam binaries to match new (1.3.1) Electron For Construct greenworks plugin created paths (Electron For Construct app build is automating the process of adding in the correct greenworks, steam libraries and app id.)

  • Update release

    No change to ACEs. In plugin JS code, add additional path for greenworks libraries, so remote preview is possible with Mac build using

  • Update release

    Added Greenworks DLC ACEs (see )

    I am mainly using Electron for Construct to integrate C3 and Greengrinds / Greenworks / Steam into an executable. Electron for Construct also has the side benefit of download and using the appropriate Greenworks binary (*.node file) for the version of Electron you are building for.

    If you need to use a later version of nw.js, you can try replacing the *.node in your output directory/package with one of these that match the version of nw.s you build with. They were built by Armaldio's nice CI build service (if you use them, don't forget to Donate!)

    (Use release 0.2.8 from the above for all of the DLC ACEs to be enabled.)

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)