commit 52ec89eb9a79e14ce1f04a0b01d7c1f4ffde1c63
Author: merith-tk <merith@merith.xyz>
Date:   Sat Nov 16 16:37:10 2024 -0800

    main

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..83275b2
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,7 @@
+*.umap
+*.uasset
+*.ubulk
+*.uexp
+*.uptnl
+*.utexture
+*.ucache
diff --git a/.mappings/IntoTheRadius2-5.3.1-0+UE5.usmap b/.mappings/IntoTheRadius2-5.3.1-0+UE5.usmap
new file mode 100644
index 0000000..18ec79b
Binary files /dev/null and b/.mappings/IntoTheRadius2-5.3.1-0+UE5.usmap differ
diff --git a/.scripts/lfs.sh b/.scripts/lfs.sh
new file mode 100644
index 0000000..f3d787f
--- /dev/null
+++ b/.scripts/lfs.sh
@@ -0,0 +1,33 @@
+#!/bin/bash
+
+# Set the size threshold in bytes (e.g., 10MB = 10 * 1024 * 1024)
+THRESHOLD=$((10 * 1024 * 1024))
+
+# Ensure Git LFS is initialized
+git lfs install --skip-smudge
+
+# Find large files in the current commit and throughout history
+echo "Identifying large files exceeding $((THRESHOLD / 1024 / 1024))MB..."
+large_files=$(find . -type f -size +${THRESHOLD}c ! -path "./.git/*")
+
+if [ -z "$large_files" ]; then
+  echo "No files larger than $((THRESHOLD / 1024 / 1024))MB found."
+  exit 0
+fi
+
+# Track large files with Git LFS
+for file in $large_files; do
+  if git check-ignore -q "$file"; then
+    continue
+  fi
+  echo "Tracking large file with Git LFS: $file"
+  git rm --cached "$file" >/dev/null 2>&1 ## Untrack the file from git
+  echo "[LFS]" $(git lfs track "$file")   ## Track the file with git-lfs
+done
+
+# Add changes to .gitattributes
+if [ -f .gitattributes ]; then
+  git add .gitattributes
+else
+  echo "No .gitattributes file found; no changes made."
+fi
diff --git a/.scripts/setup-precommit.sh b/.scripts/setup-precommit.sh
new file mode 100644
index 0000000..3fc0a61
--- /dev/null
+++ b/.scripts/setup-precommit.sh
@@ -0,0 +1,16 @@
+#!/bin/sh
+# File: /e:/Workspace/Fmodel/Exports/.scripts/setup-precommit.sh
+
+# Create the .git/hooks directory if it doesn't exist
+mkdir -p .git/hooks
+
+# Write the pre-commit hook script
+cat <<'EOF' >.git/hooks/pre-commit
+#!/bin/sh
+sh ./.scripts/lfs.sh
+EOF
+
+# Make the pre-commit hook script executable
+chmod +x .git/hooks/pre-commit
+
+echo "Pre-commit hook has been set up to run 'sh ./.scripts/lfs.sh'"
diff --git a/.vscode/settings.json b/.vscode/settings.json
new file mode 100644
index 0000000..c1bca0d
--- /dev/null
+++ b/.vscode/settings.json
@@ -0,0 +1,34 @@
+{
+  // Default Editor Settings
+  "editor.formatOnSave": true,
+  "files.insertFinalNewline": true,
+  "files.trimTrailingWhitespace": true,
+  "editor.tabSize": 2,
+  // Exclude Unreal Engine files from the file watcher
+  "files.watcherExclude": {
+    // Unreal Engine
+    "**/*.umap": true,
+    "**/*.uasset": true,
+    "**/*.ubulk": true,
+    "**/*.uexp": true,
+    "**/*.uptnl": true,
+    "**/*.utexture": true,
+    "**/*.ucache": true
+  },
+  // Prevents the editor from trying to show the Unreal Engine files in the file explorer
+  "files.exclude": {
+    // Unreal Engine
+    "**/*.umap": true,
+    "**/*.uasset": true,
+    "**/*.ubulk": true,
+    "**/*.uexp": true,
+    "**/*.uptnl": true,
+    "**/*.utexture": true,
+    "**/*.ucache": true
+  },
+  // Associate Unreal Engine plugin files with JSON
+  "files.associations": {
+    "*.uplugin": "json",
+    "*.upluginmanifest": "json"
+  }
+}
diff --git a/readme.md b/readme.md
new file mode 100644
index 0000000..982b130
--- /dev/null
+++ b/readme.md
@@ -0,0 +1,64 @@
+
+# ITR2 Modding Community Repository
+
+> Branch: `main`
+
+- The `main` branch serves as the "template" branch for all extractions.
+- Branches like `v0.12.0b/pc0-1` are shortened versions of their corresponding file names (e.g., `pakchunk0_s1-Windows.pak` for **beta v0.12.0**).
+  - **Naming Convention:**
+    - `pc` stands for `pakchunk`.
+    - The number after the dash (e.g., `-1`) matches the `-sX` suffix from the original file name.
+    - File extensions (`.pak`, `.utoc`) and the platform (e.g., Windows) are excluded for brevity.
+- A `combined` branch is planned for manual merging of assets, provided none of the files overwrite one another.
+
+---
+
+## Important Notice for All Members
+
+This repository is **exclusively for the Into the Radius 2 (ITR2) modding community**. All files, tools, and assets in this repository are intended for use within this community **only**. **No files** from this repository should be leaked or shared outside of this group. Doing so violates the terms of access and the trust of the modding community.
+
+---
+
+### Asset Export Information
+
+The files in this repository have been extracted using **FModel** to provide reference material and assist in mod creation for **ITR2**.
+
+- Branches are created directly from `main`, **not sequentially from previous branches**.
+- **Verification Steps:**
+  The extraction process involves combining `pak` and `utoc` files:
+  - **Step 1:** Extract the `pak` file.
+  - **Step 2:** Extract the `utoc` file on top of it.
+
+---
+
+### Strict Restrictions on UAsset and UBulk Files
+
+- **Do not push `.uasset`, `.ubulk`, or similar files** to this repository under any circumstances.
+- Uploading such files will result in the **immediate revocation of access** to this repository.
+- Unauthorized distribution of assets will be **reported to the ITR2 developers**, which could result in further legal or community actions.
+
+---
+
+### Access to UAsset Files
+
+If `.uasset` files are required for reference, approved members can request access to a **private MegaSync share** containing the dumped files.
+
+- Contact a repository administrator for access.
+
+---
+
+### Modding Guidelines and Best Practices
+
+1. Use this repository exclusively for **Into the Radius 2** modding.
+2. Do not use these assets for other purposes or games.
+3. Follow all ethical and legal guidelines in your mod development.
+
+---
+
+### Final Warning
+
+We value the contributions of our modding community and the creativity it brings. However, maintaining the integrity of this repository is critical. Violating these terms will result in **immediate loss of access** and potential legal consequences.
+
+---
+
+This version integrates the new branch information, clarifies extraction details, and adheres to the community's rules. Let me know if further adjustments are needed!