Various changes and additions to Contribution doc (#1097)

Author: catter1

docs/getting-started.md

@@ -4,14 +4,15 @@ This guide will show how to setup a local development environment to build, test
 ## Table of contents
 * [Installation](#installation)
 * [Building modules](#building-modules)
+* [Common issues](#common-issues)
 * [Submitting changes](#submitting-changes)
 
 ## Installation
 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/).
 
 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.
 
-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.
+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. We currently use Python 3.10.
 ```sh
 # MacOS, Linux, or Git Bash (recommended)
 curl -LsSf https://astral.sh/uv/install.sh | sh
@@ -40,7 +41,7 @@ uv run beet dev --link <world_name> --watch metallurgy *_shamir
 ```
 * `uv run` makes sure that the command uses the correct Python dependencies
 * `beet dev` builds the data packs to the `out` folder
-* `--link <world_name>` copies the packs to a local world
+* `--link <world_name>` copies the packs to a local world (filepath to the world's directory)
 * `--watch` watches for file changes and then rebuilds
 * `metallurgy *_shamir` specifies the list of module IDs to build
 
@@ -49,6 +50,14 @@ Building the release version of all modules is also possible. It will output the
 uv run beet -p beet-release.yaml build
 ```
 
+## Common issues
+When building the modules, sometimes you will encounter odd errors.
+
+If you get an error about a beet plugin exception, many times it can be resolved simply by refreshing the beet cache.
+```
+uv run beet cache --clear
+```
+
 ## Submitting changes
 To submit changes to our modules, start by creating a branch. This allows us to review every change separately and allows you to make other changes in the future. Make sure you are on the `master` branch when you do this.