Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prebuild for NW.js 0.49.2-0.53.0 doesn't function correctly #575

Open
utunnels opened this issue Jan 26, 2025 · 4 comments
Open

Prebuild for NW.js 0.49.2-0.53.0 doesn't function correctly #575

utunnels opened this issue Jan 26, 2025 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@utunnels
Copy link

Describe the bug
Prebuild for NW.js 0.49.2-0.53.0 doesn't function correctly like it used to do. Many APIs don't return correct results or don't recognize arguments passed from JavaScript.

To Reproduce
Steps to reproduce the behavior:

  1. Download the prebuild file from https://greenworks-prebuilds.armaldio.xyz/
  2. Download greenworks v0.14.0 release from https://github.com/greenheartgames/greenworks/releases
  3. Replace the node file with the downloaded node file from step 1
  4. Download steam sdk 1.50
  5. Make an empty NW.js with a blank html, put the files include steam_appid.txt with correct appid in correct place
  6. Run the project using NW.js 0.49.2, with steam running and logged-in.
  7. Execute var greenworks = require('./greenworks') from the console
  8. Execute greenworks.initAPI(), console output false
  9. Execute greenworks.isSteamRunning(), console output false
  10. Execute greenworks.getAchievementNames(), console output correct results
  11. Execute greenworks.getAchievement('Your achievement id here', function(){}), the app throws an exception 'Bad arguments'.

Expected behavior
Step 7 should output true, step 8 should output true, step 11 should not throw 'Bad arguments' exception.

Desktop (please complete the following information):

  • OS: Windows 11 x64
  • Asset infos: steam client, steam sdk 1.50, NW.js 0.49.2

Additional context
The website(https://greenworks-prebuilds.armaldio.xyz/) shows the file's last update date as a year ago. I also checked prebuilt node files from a game released before the time, the author indicated they used prebuilt files form the same site, and the files functioned correctly. I assume the prebuilt files were changed 1 year ago.

@utunnels utunnels added the bug Something isn't working label Jan 26, 2025
@Armaldio
Copy link
Member

Hey there

First of all, NW.js 0.49 is 5 years old
It is unsupported from my side at this point

Second, you said you downloaded greenworks 0.14 (which is 6 years old)
The prebuilds from this repository are most likely built using a different steam SDK version that the one used to build the 0.14

Since your using NW.js, I would highly recommend either switching to electron or another runtime, or switch to the prebuilds compiled by greenworks itself

Let me know if you have any more questions

@utunnels
Copy link
Author

Hello thanks for the reply. If it is not supported it's OK. Actually the version was used by some RPG Maker MV users who think nw.js v0.49.2 is stable for their plugins. And I'm a bit curious because the prebuild file on the site used to work (more than 1 years ago).
If it is no longer supported maybe I can just make a backup of the old file. Again, thanks for the quick response.

@Armaldio
Copy link
Member

You can always switch the release tag to access the old files

@utunnels
Copy link
Author

Yes I did. That is how I found the node file for nw.js 0.49.2. Like I said above, the file was changed. Because I compared to the file downloaded from the site some years ago, the sizes are different. I guess the files were rebuilt some time ago. By the way, I also tried the one for nw 0.49.1 (just one version behind), and found no problems. I haven't tried other versions newer than them though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants