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
Copy file name to clipboardexpand all lines: docs/getting-started.md
+15-8
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,16 @@ This guide will show how to setup a local development environment to build, test
9
9
## Installation
10
10
To contribute to our project you need to install [Git](https://git-scm.com/downloads) and a text editor. We recommend [VSCode](https://code.visualstudio.com/).
11
11
12
-
Our modules are built using [beet](https://github.com/mcbeet/beet), which allows us to automatically validate and generate part of our data packs and resource packs. However this requires some extra setup:
Our modules are built using [beet](https://github.com/mcbeet/beet), which is a Python framework that allows us to automatically validate and generate part of our data packs and resource packs.
13
+
14
+
You will need to install [uv](https://docs.astral.sh/uv/) as project manager. If you don't already have Python installed, uv will do that automatically.
Open the `GM4_Datapacks` folder in VScode. Then run `poetry install`. This will install beet and all our other dependencies.
31
+
Open the `GM4_Datapacks` folder in VScode. Then run `uv sync`. This will install beet and all our other dependencies.
25
32
26
33
You are now ready to build our modules and make changes!
27
34
28
35
## Building modules
29
36
The source of each module is stored in each `gm4_*` folder. To convert them to a valid data pack, you need to use Beet:
30
37
31
38
```
32
-
poetry run beet dev --link <world_name> --watch metallurgy *_shamir
39
+
uv run beet dev --link <world_name> --watch metallurgy *_shamir
33
40
```
34
-
*`poetry run` makes sure that the command uses the correct Python dependencies
41
+
*`uv run` makes sure that the command uses the correct Python dependencies
35
42
*`beet dev` builds the data packs to the `out` folder
36
43
*`--link <world_name>` copies the packs to a local world
37
44
*`--watch` watches for file changes and then rebuilds
38
45
*`metallurgy *_shamir` specifies the list of module IDs to build
39
46
40
47
Building the release version of all modules is also possible. It will output the zipped data packs in the `release/<version>` folder. Running this could take a few minutes!
41
48
```
42
-
poetry run beet -p beet-release.yaml build
49
+
uv run beet -p beet-release.yaml build
43
50
```
44
51
45
52
## Submitting changes
@@ -55,7 +62,7 @@ git checkout -b <branch_name>
55
62
While making changes, test the data packs in a local world:
56
63
57
64
```
58
-
poetry run beet dev --link <world_name> --watch <module_id>
65
+
uv run beet dev --link <world_name> --watch <module_id>
59
66
```
60
67
61
68
When you are happy with the changes, create a commit on the branch.
0 commit comments