Remove leftovers.

COMPILE.md

@@ -2,77 +2,4 @@
 
 ## Visual Studio
 
-1. Clone or download the repository
-1. Open the repo folder in Visual Studio 2022+.
-2. Wait for cmake to configure the project and load all assets (this may take a few minutes on the first run).
-3. Right click a folder in the solution explorer and switch to the 'CMake Targets View'
-4. Select platform and configuration from the dropdown. EG: `Windows64 - Debug` or `Windows64 - Release`
-5. Pick the startup project `Minecraft.Client.exe` or `Minecraft.Server.exe` using the debug targets dropdown
-6. Build and run the project:
-   - `Build > Build Solution` (or `Ctrl+Shift+B`)
-   - Start debugging with `F5`.
-
-### Dedicated server debug arguments
-
-- Default debugger arguments for `Minecraft.Server`:
-  - `-port 25565 -bind 0.0.0.0 -name DedicatedServer`
-- You can override arguments in:
-  - `Project Properties > Debugging > Command Arguments`
-- `Minecraft.Server` post-build copies only the dedicated-server asset set:
-  - `Assets/MediaWindows64.arc`
-  - `Assets/Textures/res`
-  - `Data/Saves`
-
-## CMake (Windows x64)
-
-Configure (use your VS Community instance explicitly):
-
-Open `Developer PowerShell for VS` and run:
-
-```powershell
-cmake --preset windows64
-```
-
-Build Debug:
-
-```powershell
-cmake --build --preset windows64-debug --target Minecraft.Client
-```
-
-Build Release:
-
-```powershell
-cmake --build --preset windows64-release --target Minecraft.Client
-```
-
-Build Dedicated Server (Debug):
-
-```powershell
-cmake --build --preset windows64-debug --target Minecraft.Server
-```
-
-Build Dedicated Server (Release):
-
-```powershell
-cmake --build --preset windows64-release --target Minecraft.Server
-```
-
-Run executable:
-
-```powershell
-cd .\build\windows64\Minecraft.Client\Debug
-.\Minecraft.Client.exe
-```
-
-Run dedicated server:
-
-```powershell
-cd .\build\windows64\Minecraft.Server\Debug
-.\Minecraft.Server.exe -port 25565 -bind 0.0.0.0 -name DedicatedServer
-```
-
-Notes:
-- The CMake build is Windows-only and x64-only.
-- Contributors on macOS or Linux need a Windows machine or VM to build the project. Running the game via Wine is separate from having a supported build environment.
-- Post-build asset copy is automatic for `Minecraft.Client` in CMake (Debug and Release variants).
-- The game relies on relative paths, so launching from the output directory is required.
+## CMake (Windows x64)

CONTRIBUTING.md

@@ -1,60 +1,13 @@
 # Scope of Project
-At the moment, this project's scope is generally limited outside of adding new content to the game (blocks, mobs, items). We are currently prioritizing stability, quality of life, and platform support over these things.
 
 ## Parity
-We are attempting to keep our version of LCE as close to visual and experience parity with the original console experience of LCE as possible. This means that we will not be accepting changes that...
-- Backport things from Java Edition that did not ever exist in LCE
-- Swap out LCE visuals for Java Edition or Bedrock Edition style visuals
-- Change LCE defaults in favor of different defaults if it changes the experience
-  - For example, increasing mob spawn limits without increasing the area mobs can spawn within, aka increasing mob density past what was the original console experience
-- Redesign UI components different than LCE
-- Break controller support, or otherwise do not support play with a controller
-- Add custom texture packs or DLC that never existed in LCE
-- Add any gameplay content (block, item, mob) that has no existing point of reference in any official LCE build
-
-However, we would accept changes that...
-- Fix legitimately buggy or inconsistent behavior in LCE that causes unexpected outcomes
-  - For example, mobs clipping outside of walls, clipping through the world, broken mechanics
-- Add features to better support multi-platform use of LCE, such as video and control settings
-  - These menus need to respect the visual style of LCE, though.
-- Replace existing UI systems with SWF-free rendering techniques that are as visually and functionally identical as possible
-- Improve the quality of assets (such as sounds) while preserving their contents
-  - For example, upgrading the quality of all music in-game while preserving any unique cuts / versions, or faithfully remaking those unique cuts / versions with higher quality assets
-- Backport things like modern skin rendering
-- Change the code from using non-stitched textures to individually named texture PNGs and stitching at runtime
-- Adding menus to better support custom dedicated servers with their own fixed IPs
-- Add support for things like Steamworks Networking and other P2P networking and auth strategies
-- Improve Keyboard and Mouse control support
-- Add minimal, non-invasive Quality of Life features that don't otherwise compromise the LCE experience
-  - For example, adjusting certain crafting recipes or change item behaviors like non-stackable doors 
-
 
 ## Current Goals
-- Being a robust Desktop version of LCE
-- Having proper controller support across all types, brands on Desktop or Desktop-like platforms (Steam Deck)
-- Improving stability as much as possible
-- Fixing as many bugs as possible
-- Enabling Desktop multiplayer options
-  - LAN P2P Multiplayer
-  - Splitscreen Multiplayer
-  - WAN Servers (IP:Port connectivity)
-  - Platform-based P2P Connectivity
-    - Steam Networking
-    - GameDate?
-    - Maybe more?
-- Refining rendering settings, renderer options, as well as reaching rendering parity with true LCE
-- Having workable multi-platform compilation for ARM, Consoles, Linux
-- Being a good base for further expansion and modding of LCE, such as backports and "modpacks".
 
 # Scope of PRs
-All Pull Requests should fully document the changes they include in their file changes. They should also be limited to one general topic and not touch all over the codebase unless its justifiable. 
-
-For example, we would not accept a PR that reworks UI, multiplayer code, and furnace ticking even if its a "fixup" PR as its too difficult to review a ton of code changes that are all irrelevant from each other. However, a PR focused on adding a bunch of commands or fixes several crashes that are otherwise irrelevant to each other would be accepted. 
-
-If your PR includes any undocumented changes it will be closed.
 
 # Use of AI and LLMs
 We currently do not accept any new code into the project that was written largely, entirely, or even noticably by an LLM. All contributions should be made by humans that understand the codebase.
 
 # Pull Request Template
-We request that all PRs made for this repo use our PR template to the fullest extent possible. Completely wiping it out to write minimal information will likely get your PR closed.
+We request that all PRs made for this repo use our PR template to the fullest extent possible. Completely wiping it out to write minimal information will likely get your PR closed.

README.md

@@ -7,20 +7,13 @@ Just another project.
 
 - **Windows**: Supported for building and running the project
 - **macOS / Linux**: The Windows nightly build will run through Wine or CrossOver
-- **All Consoles**: There is no support for consoles. It will be removed later to clean up the code, save space, and improve compilation time.
 
 ## Build & Run
 
 1. Install [Visual Studio 2022](https://aka.ms/vs/17/release/vs_community.exe) or [newer](https://visualstudio.microsoft.com/downloads/).
 2. Clone the repository.
 3. Open the project folder from Visual Studio.
-4. Set the build configuration to **Windows64 - Debug** (Release is also ok but missing some debug features), then build and run.
-
-### CMake (Windows x64)
-
-```powershell
-cmake --preset windows64
-cmake --build --preset windows64-debug --target Minecraft.Client
-```
-
-For more information, see [COMPILE.md](COMPILE.md).
+4. Wait for cmake to configure the project and load all assets (this may take a few minutes on the first run).
+5. Set the build configuration to "Debug" or "Release".
+6. Pick the startup project.
+7. Build and run the project.