steamworks.js-timmy 0.1.14 → 0.1.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -1,88 +1,7 @@
|
|
|
1
|
-
|
|
2
|
-
[](https://npmjs.com/package/steamworks.js)
|
|
3
|
-
[](https://opensource.org/licenses/MIT)
|
|
4
|
-
[](https://discord.gg/H6B7UE7fMY)
|
|
1
|
+
# steamworks.js-timmy
|
|
5
2
|
|
|
6
|
-
|
|
3
|
+
package with added features and newer steam API
|
|
7
4
|
|
|
8
|
-
|
|
5
|
+
yum
|
|
9
6
|
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
I used [greenworks](https://github.com/greenheartgames/greenworks) for a long time and it's great, but I gave up for the following reasons.
|
|
13
|
-
|
|
14
|
-
* It's not being maintained anymore.
|
|
15
|
-
* It's not up to date.
|
|
16
|
-
* It's not context-aware.
|
|
17
|
-
* You have to build the binaries by yourself.
|
|
18
|
-
* Don't have typescript definitions.
|
|
19
|
-
* The API it's not trustful.
|
|
20
|
-
* The API implement callbacks instead of return flags or promises.
|
|
21
|
-
* I hate C++.
|
|
22
|
-
|
|
23
|
-
## API
|
|
24
|
-
|
|
25
|
-
```js
|
|
26
|
-
const steamworks = require('steamworks.js')
|
|
27
|
-
|
|
28
|
-
// You can pass an appId, or don't pass anything and use a steam_appid.txt file
|
|
29
|
-
const client = steamworks.init(480)
|
|
30
|
-
|
|
31
|
-
// Print Steam username
|
|
32
|
-
console.log(client.localplayer.getName())
|
|
33
|
-
|
|
34
|
-
// Tries to activate an achievement
|
|
35
|
-
if (client.achievement.activate('ACHIEVEMENT')) {
|
|
36
|
-
// ...
|
|
37
|
-
}
|
|
38
|
-
```
|
|
39
|
-
|
|
40
|
-
You can refer to the [declarations file](https://github.com/ceifa/steamworks.js/blob/main/client.d.ts) to check the API support and get more detailed documentation of each function.
|
|
41
|
-
|
|
42
|
-
## Installation
|
|
43
|
-
|
|
44
|
-
To use steamworks.js you don't have to build anything, just install it from npm:
|
|
45
|
-
|
|
46
|
-
```sh
|
|
47
|
-
$: npm i steamworks.js
|
|
48
|
-
```
|
|
49
|
-
|
|
50
|
-
### Electron
|
|
51
|
-
|
|
52
|
-
Steamworks.js is a native module and cannot be used by default in the renderer process. To enable the usage of native modules on the renderer process, the following configurations should be made on `main.js`:
|
|
53
|
-
|
|
54
|
-
```js
|
|
55
|
-
const mainWindow = new BrowserWindow({
|
|
56
|
-
// ...
|
|
57
|
-
webPreferences: {
|
|
58
|
-
// ...
|
|
59
|
-
contextIsolation: false,
|
|
60
|
-
nodeIntegration: true
|
|
61
|
-
}
|
|
62
|
-
})
|
|
63
|
-
```
|
|
64
|
-
|
|
65
|
-
To make the steam overlay working, call the `electronEnableSteamOverlay` on the end of your `main.js` file:
|
|
66
|
-
|
|
67
|
-
```js
|
|
68
|
-
require('steamworks.js').electronEnableSteamOverlay()
|
|
69
|
-
```
|
|
70
|
-
|
|
71
|
-
For the production build, copy the relevant distro files from `sdk/redistributable_bin/{YOUR_DISTRO}` into the root of your build. If you are using electron-forge, look for [#75](https://github.com/ceifa/steamworks.js/issues/75).
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
## How to build
|
|
75
|
-
|
|
76
|
-
> You **only** need to build if you are going to change something on steamworks.js code, if you are looking to just consume the library or use it in your game, refer to the [installation section](#installation).
|
|
77
|
-
|
|
78
|
-
Make sure you have the latest [node.js](https://nodejs.org/en/), [Rust](https://www.rust-lang.org/tools/install) and [Clang](https://rust-lang.github.io/rust-bindgen/requirements.html). We also need [Steam](https://store.steampowered.com/about/) installed and running.
|
|
79
|
-
|
|
80
|
-
Install dependencies with `npm install` and then run `npm run build:debug` to build the library.
|
|
81
|
-
|
|
82
|
-
There is no way to build for all targets easily. The good news is that you don't need to. You can develop and test on your current target, and open a PR. When the code is merged to main, a github action will build for all targets and publish a new version.
|
|
83
|
-
|
|
84
|
-
### Testing Electron
|
|
85
|
-
|
|
86
|
-
Go to the [test/electron](./test/electron) directory. There, you can run `npm install` and then `npm start` to run the Electron app.
|
|
87
|
-
|
|
88
|
-
Click "activate overlay" to test the overlay.
|
|
7
|
+
specifically tailored for [NEODITRONIX](https://store.steampowered.com/app/3782120/NEODITRONIX/), please play it!!!!
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|