Up-To-Date Greenworks Support For Construct - Custom Prebuilds

    • General Information

      Website Downloader

      Greenworks - Custom Prebuilds: Open Website ➚

      Description

      This is a community project that provides custom Greenworks prebuilds for Construct 2 and Construct 3 desktop games. These make it possible to use any NWjs release with a selected Greenworks addon.

      Features

      • Website Downloader with integrated search filters
      • Automatically compiled Greenworks Prebuilds
      • Support for most recent NWjs versions

      Website Screenshot

    • Installation Guide

      Install Instructions - Getting Started

      How to get started:

      1. Install selected Greenworks addon and NWjs release*
      2. Follow the instructions given by the selected addon*
      3. Export your project to desktop (unzip if required)
      4. Download matching prebuild files from the website
      5. Continue based on project platform below (Windows/Mac/Linux)

      *Only required if you don't have any Greenworks addon installed!

      Install Instructions - Platform Specific

      Replace Windows prebuilds:

      1. Go to exported "win32" or "win64" folder
      2. Rename "package.nw" to "package.zip" and open archive
      3. Replace the 5 prebuild files with the new ones (e.g. "greenworks-win32.node")
      4. Rename archive back to "package.nw"

      Replace Mac prebuilds:

      1. Go to exported app folder [...osx64\GAMENAME.app\Contents\Resources\app.nw"]
      2. Replace the 5 prebuild files with the new ones (e.g. "greenworks-win32.node")

      Replace Linux prebuilds:

      1. Go to exported "linux32" or "linux64" folder
      2. Rename "package.nw" to "package.zip" and open archive
      3. Replace the 5 prebuild files with the new ones (e.g. "greenworks-win32.node")
      4. Rename archive back to "package.nw"
    • Greenworks Addons

      Downloads

    • Source Code

      Links

  • Prebuilds Update - April 2020

    • <Added> Support for NWjs v0.45.0+
    • <Other> Several bugfixes and improvements
  • I have to see that documentation and assess whether to include the plugin it in my game.

    My game is already quite advanced, I don't know if it will be a lot of work to include the complement.

    I don't understand very well what file you have to download for C2. Why did you put the links of the official complement if it is very outdated ?.

    It's a great job, thanks.

  • I have to see that documentation and assess whether to include the plugin it in my game.

    My game is already quite advanced, I don't know if it will be a lot of work to include the complement.

    I don't understand very well what file you have to download for C2. Why did you put the links of the official complement if it is very outdated ?.

    It's a great job, thanks.

    Please follow the installation guide. These are basically compiled node files, which make it possible to use Greenworks with a selected NWjs version.

    No addons are being modified, that's still up to the addon developers. The changes as mentioned inside the installation guide are being done after exporting your game.

  • Great post - well done TheRealDannyyy and Armaldio!

    A few comments on my Greenworks plugin (Greengrinds.) It's free, it's an extension of the official C3 plugin. It works with nw.js and Electron (using Armaldio's Electron For Construct.)

    I added ACEs for the following Greenworks APIs: Cloud File, more Achievements, Stats, and DLC. It's also C3 only.

  • Hi, thanks for all the information. Not sure if this is the right place to ask this.

    Is there any way to test with the greenworks plugin without having a game published in steam?

    Suppose I want to see how the plugin works and do some tests but I don't have any games on Steam. Can this be done?. Is there an official DOC for the greenworks plugin?. I see that the plugin has few actions and events.

    This DOC says nothing about the events or actions of the official plugin:https://www.construct.net/en/construct-2/addons/83/greenworks/documentation

  • Hi, thanks for all the information. Not sure if this is the right place to ask this.

    Is there any way to test with the greenworks plugin without having a game published in steam?

    Suppose I want to see how the plugin works and do some tests but I don't have any games on Steam. Can this be done?. Is there an official DOC for the greenworks plugin?. I see that the plugin has few actions and events.

    This DOC says nothing about the events or actions of the official plugin:https://www.construct.net/en/construct-2/addons/83/greenworks/documentation

    Add the addon to a testing project. Use the conditions to check if Steam is ready. After doing everything that is mentioned in the docs, add the project as a Non-Steam game to your library. Since you don't have your own AppID yet, you'll have to use the official Steamworks Spaceware testing project AppID (480). This also makes it possible to test achievements later on.

    If you want to test with a more recent version of NWjs, you have to use our custom prebuilds. I've done all of this already and it worked fine. There are some issues with the overlay that require some Chromium Args to be added, check the Roundup for all details.

    I'm planning to create an entire tutorial for getting your game on Steam at some point.

  • Added support for NWjs v0.43.0. We've identified the issues caused by recent NWjs releases and fixed all prebuilds from v0.42.1 - v0.42.6.

  • Great topic, TheRealDannyyy ! Would also be very interested by the Steam roundup you're considering making. My game is releasing in February and everything works, but I fumbled a lot. A definitive primer would have really helped, and would definitely help newcomers. Btw your Big NW.Js roundup has been quite useful to me already, thanks <3

    I also felt quite restricted by the current official Greenworks ACEs so I'm considering updating to Greengrinds to support future DLCs for example.

    About the custom prebuilds I see that it enables support for more recent versions of nw.js (I'm currently using Greenworks + Nw.js 0.33.3), but could you explain the benefits to use more recent versions of nw.js ? I haven't seen this anywhere... I'm not really familiar with Node webkit updates and so far on this particular subject my position has been : "if it's not broken, don't fix it", but if I'm missing on something I might upgrade my game! ^^

  • About the custom prebuilds I see that it enables support for more recent versions of nw.js (I'm currently using Greenworks + Nw.js 0.33.3), but could you explain the benefits to use more recent versions of nw.js ? I haven't seen this anywhere... I'm not really familiar with Node webkit updates and so far on this particular subject my position has been : "if it's not broken, don't fix it", but if I'm missing on something I might upgrade my game! ^^

    Software updates always contain important fixes and performance improvements. NWjs specifically got a complete overhaul of the window tech, which fixes a lot of issues with Steam and certain types of game recorders. I never tell people to use new or specific versions of NWjs because there can always be unexpected issues and downgrading can sometimes be problematic.

    I also felt quite restricted by the current official Greenworks ACEs so I'm considering updating to Greengrinds to support future DLCs for example.

    That's pretty much up to Scirra. There are TONS of features that could be supported but I guess there aren't enough Construct Desktop/Steam developers to justify Scirra to put the work into it. I don't know how Scirra prioritizes things so your best bet is to ask them directly, that's just my opinion.

  • Added support for NWjs v0.44.0+ as usual. See'ya next month!

  • Great work.

    Sorry to bump you Ashley, and I don't want to derail the topic too much, but what is your opinion about updating Greenworks with these new "node" files and adding new functionalities to the official plugin such as the ones on the Github link TheRealDannyyy referenced just before?

    Apparently a lot of features could be supported, is the interest in exporting to Steam so low that no update is planned at all?

    Steam being the biggest PC game market you'd think we would want to make it as easy as possible to publish games on it :x

  • You can search for or post feature requests here: https://construct3.ideas.aha.io/

    In general, we're a small team and people have made hundreds of feature requests, representing years of work. Naturally lots of users are arguing that various features are essential, and so we constantly have to make tough decisions about priorities. Part of the reason we support third-party addons is so you don't have to wait for us to get round to it. If there are third-party features that cover what you need, then do take advantage of them.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Thanks. It's just that in this case everything seems already... "made". But I'm glad you hear requests and I've voted for related suggestions in the aha-board.

  • Just wanted to add that these are official node files based on the Greenworks repository, nothing is customized so they are as they come from GitHub. We'd fully allow Scirra to take advantage of this and update the addons accordingly.

    We won't create an idea since we've set all of this up already (kinda seems unnecessary at this point) but if some community members want to do it, feel free to do so and reference this topic.

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