You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A RuneScape game client from October 2006 which has been modified to work with RuneJS, a RuneScape game server written in NodeJS and TypeScript. **This client is not for OldSchool RuneScape** - client #435 pre-dates the very first OSRS client by quite some time.
3
+
A RuneScape game client from October 2006 which has been modified to work with RuneJS, a RuneScape game server written in NodeJS and TypeScript. **This client is not for OldSchool RuneScape** - client #435 pre-dates the very first OSRS client by quite some time.
4
4
5
5
We've no interest in OSRS client hacking, this client exists as a means to develop on RuneJS game servers and will not work with other server emulators.
6
6
7
7
## Usage
8
8
9
-
Running the client can be done either with the pre-built client JAR file or by building the Java code and running it manually in an IDE.
9
+
Running the client can be done either with the pre-built client `.jar` file from this repository's [releases](https://github.com/runejs/refactored-client-435/releases) page, or by building the Java code and running it manually in an IDE.
10
10
11
11
### Pre-Built Client
12
12
13
-
Running the pre-built client requires having Java installed: https://www.java.com/en/
13
+
Running the pre-built client requires having Java installed: <https://www.java.com/en/>
14
14
15
-
Once installed, go into the `/prebuilt/`and simply double-click the JAR file to run it. Alternatively if executing the JAR does not work, the command `java -jar client-435-0.3.jar`may be used from within the `/prebuilt/` directory.
15
+
Once installed, go to the [releases](https://github.com/runejs/refactored-client-435/releases) page, download the latest release, and simply double-click the `.jar` file file to run it. Alternatively if executing the `.jar` file does not work, the command `java -jar client-435-0.3.jar`can be used.
16
16
17
17
The client will use a set of default configurations if no file is provided. The default client configuration matches up to the default RuneJS server configuration for quick and easy initial setup. It's highly advised that you generate your own RSA public and private keys for long term use.
18
18
19
-
To provide your own configurations, create a file named `client-435.conf.yaml` in your User Home directory with the following content:
20
-
21
-
```yaml
22
-
net:
23
-
address: 127.0.0.1
24
-
game_port: 43594
25
-
cache:
26
-
cacheDir: .filestore_435
27
-
rsa:
28
-
rsaPub: YOUR_RSA_PUBLIC_KEY (default dev pair provided in the example file)
29
-
rsaModulus: YOUR_RSA_PRIVATE_KEY (default dev pair provided in the example file)
30
-
login:
31
-
useStaticCredentials: true
32
-
username: a
33
-
password: a
34
-
game:
35
-
roofsEnabled: true
36
-
freeTeleports: false
37
-
debugContextMenu: true
38
-
serverDisplayName: Build 435
39
-
```
40
-
41
-
Make sure to modify the given configuration for your specific needs.
19
+
To provide your own configurations, copy the file [`./config/client-435.conf.example.yml`](./config/client-435.conf.example.yaml) to `client-435.conf.yaml` in your user's home directory, and modify the given configuration for your specific needs.
42
20
43
21
### Gradle
44
22
@@ -47,20 +25,76 @@ without the help of an IDE such as IntelliJ. Gradle is also configured to automa
47
25
48
26
The following examples use the unix executable `./gradlew`, however Windows can replace these with `./gradlew.bat`.
49
27
50
-
**Running via Gradle**
28
+
#### Running via Gradle
51
29
52
30
The `application` gradle plugin provides the `run` task, which starts up the Main client class. With this option,
53
31
arguments can be provided via `--args`.
54
32
55
-
```
33
+
```bash
56
34
./gradlew run
57
35
```
58
36
59
-
**Building a Jar**
37
+
#### Building a `.jar` file
60
38
61
39
The `jar` task can be used to build a jar, which is generated in the `build/libs` directory.
62
40
63
-
```
41
+
```bash
64
42
./gradlew jar
65
43
java -jar ./build/libs/client-435-0.3.jar
66
44
```
45
+
46
+
#### Gradle and Java versions
47
+
48
+
As of 2024-09-04, our manual builds are done with the following Gradle and Java versions - both appear to produce a similar result:
Ant: Apache Ant(TM) version 1.10.9 compiled on September 27 2020
81
+
JVM: 17.0.10 (Azul Systems, Inc. 17.0.10+7-LTS)
82
+
OS: Mac OS X 14.4.1 aarch64
83
+
```
84
+
85
+
You can also view our [GitHub actions workflow](./.github/workflows/build-and-publish.yml) to see the automated build setup.
86
+
87
+
## Creating tags and releases
88
+
89
+
Our [GitHub actions workflow](./.github/workflows/build-and-publish.yml) is configured to build a new `.jar` file upon a `tag` push event. If you create a release in GitHub, the workflow will fail, because its purpose is to *create* the release.
90
+
91
+
The proper process for creating a new build is as follows:
92
+
93
+
1.`git fetch --all` (ensures everything is up to date - helps prevent creating a tag that someone else already created)
94
+
2.`git pull origin master` (sync your local repository with the latest changes)
95
+
3.`git tag -a -s v0.0.X`
96
+
4.`git push origin v0.0.X`
97
+
98
+
Swap out `v0.0.X` for your actual version, and please try to use the `-s` flag if you can - using GPG keys to sign tags is preferred.
99
+
100
+
In a few minutes, a new `.jar` and release will be ready on the releases page!
0 commit comments