HytaleModding
diff --git a/‎.github/CODEOWNERS‎
Lines changed: 1 addition & 1 deletion b/‎.github/CODEOWNERS‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/deploy.yml‎
Lines changed: 4 additions & 4 deletions b/‎.github/workflows/deploy.yml‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎.prettierrc‎
Lines changed: 3 additions & 0 deletions b/‎.prettierrc‎
Lines changed: 3 additions & 0 deletions
diff --git a/‎bun.lock‎
Lines changed: 111 additions & 78 deletions b/‎bun.lock‎
Lines changed: 111 additions & 78 deletions
diff --git a/‎components.json‎
Lines changed: 22 additions & 0 deletions b/‎components.json‎
Lines changed: 22 additions & 0 deletions
diff --git a/‎content/docs/established-information/faq.mdx‎
Lines changed: 3 additions & 1 deletion b/‎content/docs/established-information/faq.mdx‎
Lines changed: 3 additions & 1 deletion
diff --git a/‎content/docs/established-information/server/server-first-dev.mdx‎
Lines changed: 4 additions & 1 deletion b/‎content/docs/established-information/server/server-first-dev.mdx‎
Lines changed: 4 additions & 1 deletion
diff --git a/‎content/docs/index.mdx‎
Lines changed: 2 additions & 2 deletions b/‎content/docs/index.mdx‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎content/docs/quick-start.mdx‎
Lines changed: 1 addition & 1 deletion b/‎content/docs/quick-start.mdx‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎eslint.config.mjs‎
Lines changed: 11 additions & 11 deletions b/‎eslint.config.mjs‎
Lines changed: 11 additions & 11 deletions
@@ -1,4 +1,4 @@
 * @ItsNeil17
 
 /content/docs/what-we-know-so-far/ways-to-develop/text-based.mdx @okunamayanad
-‎/content/docs/what-we-know-so-far/developer-qa-insights.mdx @Laophy
+/content/docs/what-we-know-so-far/developer-qa-insights.mdx @Laophy
@@ -1,7 +1,7 @@
 name: Deploy to GitHub Pages
 on:
   push:
-    branches: 
+    branches:
       - main
       - documentation
   workflow_dispatch:
@@ -27,10 +27,10 @@ jobs:
             source ~/.bashrc 2>/dev/null || true
             cd /opt/website/
             git pull origin ${{ github.ref_name }}
-            
+
             BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)
             COMMIT_HASH=$(git rev-parse --short HEAD)
             echo "{\"branch\":\"$BRANCH_NAME\",\"commit\":\"$COMMIT_HASH\"}" > public/git-info.json
-            
+
             bun run build
-            pm2 restart website
+            pm2 restart website
@@ -0,0 +1,3 @@
+{
+  "plugins": ["prettier-plugin-tailwindcss"]
+}
@@ -0,0 +1,22 @@
+{
+  "$schema": "https://ui.shadcn.com/schema.json",
+  "style": "new-york",
+  "rsc": true,
+  "tsx": true,
+  "tailwind": {
+    "config": "",
+    "css": "src/app/global.css",
+    "baseColor": "neutral",
+    "cssVariables": true,
+    "prefix": ""
+  },
+  "iconLibrary": "lucide",
+  "aliases": {
+    "components": "@/components",
+    "utils": "@/lib/utils",
+    "ui": "@/components/ui",
+    "lib": "@/lib",
+    "hooks": "@/hooks"
+  },
+  "registries": {}
+}
@@ -25,16 +25,18 @@ Essentially, a solid choice for game development that blends speed and reliabili
 ## 3. What are Transport Packets?
 
 Hytale will support transfer packets which can send players to other servers with a small payload for tokens/encrypted data.
+
 - Equivalent of BungeeCord in Minecraft
 - Mainly for large server networks
 
 There is no middleman, you connect directly to Server A. When you want to switch, Server A says “Here is a 4kb ticket w/inventory and stats. Go to server B”
 Leads to massive cost reduction which can be spent on devs instead of servers
 
 ## 4. Will Hytale support dedicated servers?
+
 Yes, Hytale will support dedicated servers. This allows server owners to host their own Hytale servers on their own hardware or through third-party hosting services.
 
 Dedicated servers provide more control over server settings, mods, and performance compared to using official hosting solutions.
 
 ## 5. Will Hytale support modding on consoles?
-As of now, Hytale modding is primarily focused on PC platforms. 
+As of now, Hytale modding is primarily focused on PC platforms. 
@@ -10,6 +10,7 @@ Hytale is being developed with a "server-first" approach. This means that the se
 In a server-first architecture, the server is responsible for managing the game world, enforcing rules, and processing player actions. The client connects to the server to receive updates about the game state and to send player inputs. This approach helps ensure consistency and fairness in multiplayer environments, as the server has control over the game logic.
 
 ## Benefits of Server-First Development
+
 - **Consistency**: Since the server is the authoritative source, all players experience the same game state, reducing discrepancies and cheating.
 - **Scalability**: Server-first architectures can be more easily scaled to accommodate large numbers
     of players, as the server can manage resources and distribute load effectively.
@@ -18,9 +19,11 @@ In a server-first architecture, the server is responsible for managing the game
 - **Only One Version**: There won't be a version selector for the Hytale Client, meaning that server owners do not need to support multiple versions and can rely on everyone being on the latest client. This will help both server owners and modders.
 
 ## Implications for Modding
+
 Modders will primarily interact with the server-side components of Hytale. This means that mods will often focus on altering game logic, rules, and behaviors that are managed by the server. Client-side modifications are not allowed (as of the information given right now).
 
 Overall, the server-first approach in Hytale aims to create a robust and fair multiplayer experience while providing modders with powerful tools to customize and enhance the game.
 
 ## Conclusion
-The server-first development model is a key aspect of Hytale's architecture, ensuring a consistent and secure multiplayer experience. Modders should focus on server-side modifications to fully leverage the capabilities of this approach and create engaging content for players.
+
+The server-first development model is a key aspect of Hytale's architecture, ensuring a consistent and secure multiplayer experience. Modders should focus on server-side modifications to fully leverage the capabilities of this approach and create engaging content for players.
@@ -11,9 +11,9 @@ Hytale is a voxel-based sandbox RPG game by **Hypixel Studios**, as described on
 
 Hytale has been built from the ground up with modding and user-generated content in mind.
 The goal of **Hytale Modding** is to provide an excellent resource such that anybody
-is able to mod Hytale for themselves, regardless of skill level or specialization. 
+is able to mod Hytale for themselves, regardless of skill level or specialization.
 
 It is important to note that modding Hytale is not restricted to programming plugins.
 Programming, visual scripting, texturing, 3D modelling, modifying assets, etc. are all modding.
-<u>In Hytale, anyone can be a modder.</u>
 
+<u>In Hytale, anyone can be a modder.</u>
@@ -3,4 +3,4 @@ title: Quick Start
 description: Setting up a standard Hytale project.
 ---
 
-Lorem Ipsum
+Lorem Ipsum
@@ -1,6 +1,6 @@
-import { dirname } from 'path';
-import { fileURLToPath } from 'url';
-import { FlatCompat } from '@eslint/eslintrc';
+import { dirname } from "path";
+import { fileURLToPath } from "url";
+import { FlatCompat } from "@eslint/eslintrc";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
@@ -10,17 +10,17 @@ const compat = new FlatCompat({
 });
 
 const eslintConfig = [
-  ...compat.extends('next/core-web-vitals', 'next/typescript'),
+  ...compat.extends("next/core-web-vitals", "next/typescript"),
   {
     ignores: [
-      'node_modules/**',
-      '.next/**',
-      'out/**',
-      'build/**',
-      '.source/**',
-      'next-env.d.ts',
+      "node_modules/**",
+      ".next/**",
+      "out/**",
+      "build/**",
+      ".source/**",
+      "next-env.d.ts",
     ],
   },
 ];
 
-export default eslintConfig;
+export default eslintConfig;
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	`+{`
	`2`	`+ "plugins": ["prettier-plugin-tailwindcss"]`
	`3`	`+}`