Update README.md

README.md

@@ -1,33 +1,30 @@
-🎒 1. datapacks/ — Minecraft’s built-in modding system
+# 📦 Datapacks & Dev-World Overview
 
-Datapacks are Minecraft's official way to add game logic without mods.
-They let you create custom:
+## 🎒 1. `datapacks/` — Minecraft’s Built-In Modding System
 
-Recipes
+Datapacks are Minecraft’s **official way to add custom game logic** without installing mods.  
+They allow you to create:
 
-Loot tables
+- 🍲 Recipes  
+- 🎁 Loot tables  
+- 🗺 Structures  
+- ⚙️ Commands/functions  
+- 🌌 Dimensions  
+- 🏆 Advancements  
+- 🌱 Worldgen features  
+- 👾 Mob behavior (via loot/function triggers)
 
-Structures
-
-Commands/functions
-
-Dimensions
-
-Advancements
-
-Worldgen features
-
-Mobs (via loot, behavior triggers, etc.)
-
-They live inside:
+Datapacks live inside:
 
+```
 world/datapacks/
+```
 
+(or inside any other world folder you choose).
 
-or in a custom world folder of your choice.
-
-Example structure:
+### 📁 Example Structure
 
+```
 world/
   datapacks/
     my_custom_pack/
@@ -35,77 +32,79 @@ world/
       data/
         minecraft/
         mypack/
+```
 
+### ⚡ How Datapacks Work
 
-How they work:
-
-When the server starts, Minecraft automatically loads all datapacks in that folder.
-
-You can reload them live with:
-
+- When the server starts, Minecraft **automatically loads** all datapacks in that folder.
+- You can reload them live with:
 
+```
 /reload
+```
 
-Why track them in Git?
+### 🧠 Why Track Datapacks in Git?
 
-Because datapacks are basically tiny “mods” made out of text files.
-Git lets you:
+Because datapacks are basically **tiny mods made from text files**, Git gives you:
 
-Version your changes
+- Full version control  
+- Rollbacks for bad experiments  
+- A safe way to iterate  
+- Easy syncing between machines  
+- A complete history of every change  
 
-Roll back bad ideas
+> **Note:** Minecraft 1.1 did not support datapacks yet — but this structure is useful for future worlds or modern servers.
 
-Experiment
+---
 
-Collaborate
+## 🌍 2. `dev-world/` — A Safe Testing Sandbox
 
-Deploy from laptop → server instantly
+`dev-world/` is **not** a built-in Minecraft feature.  
+It’s a folder **you create** to safely test changes without risking the real world.
 
-Keep a history of your custom world logic
+### 🎯 Purpose
 
-For a Vanilla 1.1 server, datapacks didn’t exist yet — BUT if you're doing a modern-style organization or planning forward, Git still handles it well.
+Use this sandbox world to test:
 
+- Dangerous commands  
+- Datapack functionality  
+- Worldgen changes  
+- NBT edits  
+- Anything experimental  
 
+### 📁 Example Structure
 
-🌍 2. dev-world/ — A safe test world
-
-This is NOT a built-in Minecraft feature — it’s a practice/testing world folder that YOU create.
-
-Purpose:
-👉 To test datapacks, commands, NBT edits, worldgen changes, and dangerous experiments without ruining the real world.
-
-What it looks like:
-
+```
 dev-world/
   level.dat
   region/
   playerdata/
+```
 
+This mirrors your real `world/` folder.
 
-Basically the same as your real world/, but:
+### 💡 Why a Dev World?
 
-You can reset it anytime
+- Reset it instantly  
+- Duplicate it whenever needed  
+- Safely break anything  
+- Prototype new features  
+- Avoid griefing or corrupting the main world  
 
-You can duplicate it
+### 🔧 How to Use `dev-world/`
 
-You can try insane commands
+In your `server.properties`, set:
 
-You can prototype datapack functionality
-
-You can test structures/commands with no consequences
-
-How to use it:
-
-You temporarily point your server to use dev-world instead of world.
-
-In server.properties:
+```
 level-name=dev-world
-
-
-
+```
 
 Start the server → it loads the dev world.
-When you’re done testing, switch back:
 
+When you're finished testing, switch back:
+
+```
 level-name=world
+```
 
+---