chore: rebrand LCEMP to LCE across all 61 docs pages

182 replacements across 59 files. Only 5 LCEMP references preserved
where they refer to the actual repo name, directory paths, or CMake vars.

Author: coah80

src/content/docs/client/audio.md

@@ -1,9 +1,9 @@
 ---
 title: "Audio"
-description: "Sound system in LCEMP."
+description: "Sound system in LCE."
 ---
 
-LCEMP's audio system is built on the Miles Sound System (MSS) library, wrapped in a two-class hierarchy. `ConsoleSoundEngine` defines the platform interface, and `SoundEngine` provides the shared implementation. The system handles positional 3D audio, background music streaming, and UI sound effects.
+LCE's audio system is built on the Miles Sound System (MSS) library, wrapped in a two-class hierarchy. `ConsoleSoundEngine` defines the platform interface, and `SoundEngine` provides the shared implementation. The system handles positional 3D audio, background music streaming, and UI sound effects.
 
 ## Architecture
 
@@ -245,7 +245,7 @@ Audio resources are stored in:
 
 ## MinecraftConsoles differences
 
-MinecraftConsoles adds a large batch of new sound types to `SoundTypes.h`. These cover mobs and features that don't exist in LCEMP:
+MinecraftConsoles adds a large batch of new sound types to `SoundTypes.h`. These cover mobs and features that don't exist in LCE:
 
 ### Firework sounds
 
@@ -272,7 +272,7 @@ MinecraftConsoles adds a large batch of new sound types to `SoundTypes.h`. These
 
 ### Mob step/ambient sounds
 
-A bunch of mob step sounds are added that LCEMP was missing:
+A bunch of mob step sounds are added that LCE was missing:
 
 - `eSoundType_MOB_COW_STEP`, `_CHICKEN_STEP`, `_PIG_STEP`
 - `eSoundType_MOB_ENDERMAN_STARE`, `_SCREAM`

src/content/docs/client/input.md

@@ -1,9 +1,9 @@
 ---
 title: "Input System"
-description: "How LCEMP handles keyboard, mouse, and controller input."
+description: "How LCE handles keyboard, mouse, and controller input."
 ---
 
-LCEMP supports three input methods: gamepad controllers (the main one for all console platforms), keyboard/mouse (Windows 64-bit port), and touch (PS Vita). The input system is spread across several classes that abstract platform differences and feed into the game's action system.
+LCE supports three input methods: gamepad controllers (the main one for all console platforms), keyboard/mouse (Windows 64-bit port), and touch (PS Vita). The input system is spread across several classes that abstract platform differences and feed into the game's action system.
 
 ## Input class hierarchy
 
@@ -229,6 +229,6 @@ These are used for the integrated server console, not player gameplay input.
 
 MinecraftConsoles has a small addition to the controller input system:
 
-- **`ACTION_MENU_QUICK_MOVE`** is added to the `EControllerActions` enum. This provides a dedicated controller action for quick-moving items between inventories (like shift-clicking on PC). LCEMP doesn't have this as a separate action.
+- **`ACTION_MENU_QUICK_MOVE`** is added to the `EControllerActions` enum. This provides a dedicated controller action for quick-moving items between inventories (like shift-clicking on PC). LCE doesn't have this as a separate action.
 
 The `4J_Input.h` abstraction layer exists in both codebases as platform-specific headers under each platform's `4JLibs/inc/` directory (Orbis, Xbox, Durango, PS3, PSVita). The input architecture is otherwise the same between the two versions.

src/content/docs/client/models.md

@@ -1,9 +1,9 @@
 ---
 title: "Models"
-description: "3D model definitions for entities in LCEMP."
+description: "3D model definitions for entities in LCE."
 ---
 
-LCEMP uses a hierarchical box-based model system to define the geometry of all entities. Models are built from `ModelPart` nodes, each containing one or more `Cube` primitives. These are arranged in parent-child trees that allow jointed animation.
+LCE uses a hierarchical box-based model system to define the geometry of all entities. Models are built from `ModelPart` nodes, each containing one or more `Cube` primitives. These are arranged in parent-child trees that allow jointed animation.
 
 ## Core classes
 
@@ -265,7 +265,7 @@ The `g` parameter is a "growth" or "inflation" factor that expands boxes outward
 
 ## MinecraftConsoles differences
 
-MinecraftConsoles adds several new model classes that don't exist in LCEMP:
+MinecraftConsoles adds several new model classes that don't exist in LCE:
 
 ### New mob models
 
@@ -275,10 +275,10 @@ MinecraftConsoles adds several new model classes that don't exist in LCEMP:
 | `ModelHorse` | Horses | One of the most complex models in the game. Has head, upper/lower mouth, two ears, mule ears, neck, mane, body, three-segment tail, four multi-joint legs (each with 3 parts: A/B/C), saddle bags, and a full saddle assembly with stirrups and mouth lines. |
 | `WitchModel` | Witches | Extends `VillagerModel` with a mole and hat. Has a `holdingItem` flag for the potion-drinking animation. |
 | `WitherBossModel` | Wither boss | Body parts array and heads array. Has `prepareMobModel` for invulnerability animation. |
-| `OcelotModel` | Ocelots/cats | Dedicated model with 4 animation states: sneak, walk, sprint, and sitting. Much more detailed than the generic version in LCEMP. |
+| `OcelotModel` | Ocelots/cats | Dedicated model with 4 animation states: sneak, walk, sprint, and sitting. Much more detailed than the generic version in LCE. |
 | `SkiModel` | Player ski attachment | A 4J-added cosmetic model for DLC skins. Has left/right ski variants. |
 | `LeashKnotModel` | Leash fence knots | Simple model for the leash attachment point on fences. |
 
 ### Model rendering changes
 
-The `render()` method signature across models gains a `bool usecompiled` parameter in MinecraftConsoles. LCEMP already has this, but the entity parameter type changes from raw `Entity` references to `shared_ptr<Entity>` in some models, and `LivingEntity` is used more consistently for mob-specific methods like `prepareMobModel`.
+The `render()` method signature across models gains a `bool usecompiled` parameter in MinecraftConsoles. LCE already has this, but the entity parameter type changes from raw `Entity` references to `shared_ptr<Entity>` in some models, and `LivingEntity` is used more consistently for mob-specific methods like `prepareMobModel`.

src/content/docs/client/overview.md

@@ -31,7 +31,7 @@ The central class is `Minecraft` (declared in `Minecraft.h`). It holds reference
 
 ## Split-screen architecture
 
-LCEMP supports up to four local players through split-screen. The `Minecraft` class keeps per-player arrays for many subsystems:
+LCE supports up to four local players through split-screen. The `Minecraft` class keeps per-player arrays for many subsystems:
 
 ```cpp
 shared_ptr<MultiplayerLocalPlayer> localplayers[XUSER_MAX_COUNT];
@@ -139,16 +139,16 @@ The `Minecraft` class also exposes some static helpers:
 
 ## MinecraftConsoles differences
 
-MinecraftConsoles is a later version of the codebase (roughly TU19/1.6.4 era vs LCEMP's TU9/1.2.2 base). Here are the big structural differences at the module level:
+MinecraftConsoles is a later version of the codebase (roughly TU19/1.6.4 era vs LCE's TU9/1.2.2 base). Here are the big structural differences at the module level:
 
 - **`LivingEntityRenderer`** is a new intermediate class between `EntityRenderer` and `MobRenderer`. It pulls mob rendering logic (armor overlays, name tags, body rotation, arrow rendering) into its own layer.
 - **`ResourceLocation`** is added as a proper type for texture paths, replacing raw string lookups. There's also a `TextureAtlas` class with `LOCATION_BLOCKS` and `LOCATION_ITEMS` static fields.
-- **`BossMobGuiInfo`** tracks boss health bar state (health progress, display ticks, name, darken-world flag). LCEMP doesn't have the Wither boss so there's no boss health bar system.
+- **`BossMobGuiInfo`** tracks boss health bar state (health progress, display ticks, name, darken-world flag). LCE doesn't have the Wither boss so there's no boss health bar system.
 - **New UI scene interfaces** are added: `IUIScene_HUD`, `IUIScene_BeaconMenu`, `IUIScene_CommandBlockMenu`, `IUIScene_FireworksMenu`, `IUIScene_HopperMenu`, `IUIScene_HorseInventoryMenu`.
 - **`DLCCapeFile`** and **`DLCFile`** are new DLC file types for cape content.
 - **`DurangoTelemetry`** adds Xbox One specific telemetry.
-- **`UISplitScreenHelpers`** has split-screen utility functions not present in LCEMP.
+- **`UISplitScreenHelpers`** has split-screen utility functions not present in LCE.
 - **`ChunkRebuildData`** is a separate class for chunk rebuild tracking instead of being inlined in `LevelRenderer`.
-- The **`gdraw` graphics layer** is much bigger. LCEMP only has `gdraw_metal.h` (macOS port), while MinecraftConsoles has the original multi-platform set: `gdraw_d3d.h`, `gdraw_d3d10.h`, `gdraw_d3d11.h`, `gdraw_orbis.h`, `gdraw_ps3gcm.h`, `gdraw_psp2.h`, `gdraw_wgl.h`, plus the generic `gdraw.h`.
+- The **`gdraw` graphics layer** is much bigger. LCE only has `gdraw_metal.h` (macOS port), while MinecraftConsoles has the original multi-platform set: `gdraw_d3d.h`, `gdraw_d3d10.h`, `gdraw_d3d11.h`, `gdraw_orbis.h`, `gdraw_ps3gcm.h`, `gdraw_psp2.h`, `gdraw_wgl.h`, plus the generic `gdraw.h`.
 - **New host options** include `eGameHostOption_WorldSize`, `eGameHostOption_MobGriefing`, `eGameHostOption_KeepInventory`, `eGameHostOption_DoMobSpawning`, `eGameHostOption_DoMobLoot`, `eGameHostOption_DoTileDrops`, `eGameHostOption_NaturalRegeneration`, `eGameHostOption_DoDaylightCycle`.
 - **Controller actions** add `ACTION_MENU_QUICK_MOVE` for quick-moving items in inventories.

src/content/docs/client/particles.md

@@ -1,9 +1,9 @@
 ---
 title: "Particles"
-description: "Particle system in LCEMP."
+description: "Particle system in LCE."
 ---
 
-The LCEMP particle system renders visual effects like smoke, flames, block breaking debris, and spell effects. `ParticleEngine` manages it all, and it's built on the `Particle` base class, which extends `Entity` from `Minecraft.World`.
+The LCE particle system renders visual effects like smoke, flames, block breaking debris, and spell effects. `ParticleEngine` manages it all, and it's built on the `Particle` base class, which extends `Entity` from `Minecraft.World`.
 
 ## ParticleEngine
 

src/content/docs/client/rendering.md

@@ -1,9 +1,9 @@
 ---
 title: "Rendering Pipeline"
-description: "How LCEMP renders the game world."
+description: "How LCE renders the game world."
 ---
 
-The LCEMP rendering pipeline turns the game world into pixels through several systems working together. `GameRenderer` runs each frame, `LevelRenderer` manages chunk geometry, `EntityRenderDispatcher` routes entity drawing, `TileRenderer` builds block face geometry, and `Tesselator` is the low-level vertex buffer that everything feeds into.
+The LCE rendering pipeline turns the game world into pixels through several systems working together. `GameRenderer` runs each frame, `LevelRenderer` manages chunk geometry, `EntityRenderDispatcher` routes entity drawing, `TileRenderer` builds block face geometry, and `Tesselator` is the low-level vertex buffer that everything feeds into.
 
 ## Frame rendering flow
 
@@ -372,17 +372,17 @@ The `Lighting` class provides static methods for fixed-function lighting:
 
 ## MinecraftConsoles differences
 
-MinecraftConsoles has a bunch of additions to the rendering pipeline compared to LCEMP:
+MinecraftConsoles has a bunch of additions to the rendering pipeline compared to LCE:
 
 ### New entity renderers
 
 | Class | Entity | Notes |
 |---|---|---|
 | `BatRenderer` | Bats | New mob added in 1.4 |
-| `CaveSpiderRenderer` | Cave spiders | Gets its own renderer (extends `SpiderRenderer`) with a separate texture and a smaller scale. In LCEMP, `SpiderRenderer` handles both. |
+| `CaveSpiderRenderer` | Cave spiders | Gets its own renderer (extends `SpiderRenderer`) with a separate texture and a smaller scale. In LCE, `SpiderRenderer` handles both. |
 | `HorseRenderer` | Horses | Full horse renderer with layered texture caching for markings, armor overlays, and variant types (horse, donkey, mule, zombie, skeleton) |
-| `OcelotRenderer` | Ocelots/cats | Gets a dedicated renderer class. In LCEMP this was handled by the generic `OzelotRenderer` (note the spelling change too, `Ozelot` to `Ocelot`). |
-| `SkeletonRenderer` | Skeletons | Separated into its own class (extends `HumanoidMobRenderer`) with texture switching between normal and wither skeleton. In LCEMP, `HumanoidMobRenderer` handles both directly. |
+| `OcelotRenderer` | Ocelots/cats | Gets a dedicated renderer class. In LCE this was handled by the generic `OzelotRenderer` (note the spelling change too, `Ozelot` to `Ocelot`). |
+| `SkeletonRenderer` | Skeletons | Separated into its own class (extends `HumanoidMobRenderer`) with texture switching between normal and wither skeleton. In LCE, `HumanoidMobRenderer` handles both directly. |
 | `WitchRenderer` / `WitchModel` | Witches | Completely new mob. |
 | `WitherBossRenderer` | Wither boss | New boss mob with invulnerability texture, armor overlay, and scaling. |
 | `WitherSkullRenderer` | Wither skulls | Projectile renderer for wither skull attacks. |
@@ -414,4 +414,4 @@ A bunch of `_SPU` tile files are also added for PS3 SPU offloading of tile geome
 
 ### Renderer base class
 
-`LivingEntityRenderer` is inserted as a new base class between `EntityRenderer` and `MobRenderer`. It handles the common mob rendering pipeline: model rendering, positioning, rotations, attack animations, armor layers, name tags, and arrow-stuck-in-entity rendering. This is stuff that was previously jammed directly into `MobRenderer` in LCEMP.
+`LivingEntityRenderer` is inserted as a new base class between `EntityRenderer` and `MobRenderer`. It handles the common mob rendering pipeline: model rendering, positioning, rotations, attack animations, armor layers, name tags, and arrow-stuck-in-entity rendering. This is stuff that was previously jammed directly into `MobRenderer` in LCE.

src/content/docs/client/screens.md

@@ -1,9 +1,9 @@
 ---
 title: "Screens & GUI"
-description: "GUI screen system in LCEMP."
+description: "GUI screen system in LCE."
 ---
 
-LCEMP has two GUI layers: the legacy Java-style `Screen` system (used for basic menus) and the console-native `UIScene` system (in `Common/UI/`) for the actual in-game console UI. Both systems exist side by side, with the console UI handling most player-facing menus.
+LCE has two GUI layers: the legacy Java-style `Screen` system (used for basic menus) and the console-native `UIScene` system (in `Common/UI/`) for the actual in-game console UI. Both systems exist side by side, with the console UI handling most player-facing menus.
 
 ## Legacy Screen system
 
@@ -382,7 +382,7 @@ Computes screen dimensions accounting for console safe zones and split-screen la
 
 ## MinecraftConsoles differences
 
-MinecraftConsoles adds a bunch of new screens and UI scenes for features that don't exist in LCEMP:
+MinecraftConsoles adds a bunch of new screens and UI scenes for features that don't exist in LCE:
 
 ### New UIScene classes
 
@@ -392,7 +392,7 @@ MinecraftConsoles adds a bunch of new screens and UI scenes for features that do
 | `UIScene_FireworksMenu` | Firework rocket crafting UI |
 | `UIScene_HopperMenu` | Hopper inventory (5-slot single-row container) |
 | `UIScene_HorseInventoryMenu` | Horse/donkey/mule inventory (saddle, armor, and chest slots) |
-| `UIScene_LanguageSelector` | In-game language selection (LCEMP handles this differently) |
+| `UIScene_LanguageSelector` | In-game language selection (LCE handles this differently) |
 | `UIScene_NewUpdateMessage` | Title update notification screen |
 
 ### New UIScene interfaces

src/content/docs/client/settings.md

@@ -1,9 +1,9 @@
 ---
 title: "Settings"
-description: "Game settings and options in LCEMP."
+description: "Game settings and options in LCE."
 ---
 
-LCEMP manages settings at two levels. The `Options` class handles legacy Java-style game options (graphics, controls, keybindings), while the `CMinecraftApp` game settings system manages console-specific per-player profile settings. The `Settings` class provides a simple key-value property store for server configuration.
+LCE manages settings at two levels. The `Options` class handles legacy Java-style game options (graphics, controls, keybindings), while the `CMinecraftApp` game settings system manages console-specific per-player profile settings. The `Settings` class provides a simple key-value property store for server configuration.
 
 ## Options class
 
@@ -325,9 +325,9 @@ MinecraftConsoles tweaks the settings system in a few places:
 
 ### New game settings
 
-- **`eGameSetting_RenderDistance`** is added for per-player render distance control. LCEMP handles render distance only through the `Options` class.
-- **`eGameSetting_FOV`** is added for per-player field of view. Same deal, LCEMP only has this in `Options`.
-- **`eGameSetting_Fullscreen`** is removed (it was a Windows 64-bit only setting in LCEMP).
+- **`eGameSetting_RenderDistance`** is added for per-player render distance control. LCE handles render distance only through the `Options` class.
+- **`eGameSetting_FOV`** is added for per-player field of view. Same deal, LCE only has this in `Options`.
+- **`eGameSetting_Fullscreen`** is removed (it was a Windows 64-bit only setting in LCE).
 
 ### New host options
 

src/content/docs/client/textures.md

@@ -1,9 +1,9 @@
 ---
 title: "Textures & Resources"
-description: "Texture loading and resource management in LCEMP."
+description: "Texture loading and resource management in LCE."
 ---
 
-LCEMP manages textures through several systems working together. `Textures` handles loading and binding, `TextureManager` provides a name-to-ID registry, `TexturePackRepository` manages texture pack selection, and a hierarchy of `TexturePack` implementations abstracts where resources come from.
+LCE manages textures through several systems working together. `Textures` handles loading and binding, `TextureManager` provides a name-to-ID registry, `TexturePackRepository` manages texture pack selection, and a hierarchy of `TexturePack` implementations abstracts where resources come from.
 
 ## Textures
 
@@ -255,7 +255,7 @@ MinecraftConsoles expands the texture system in a few ways:
 
 ### New mob textures
 
-The `TEXTURE_NAME` enum gains a lot of new entries for mobs that don't exist in LCEMP:
+The `TEXTURE_NAME` enum gains a lot of new entries for mobs that don't exist in LCE:
 
 - **Bat:** `TN_MOB_BAT`
 - **Horse variants:** `TN_MOB_HORSE_BLACK`, `TN_MOB_HORSE_BROWN`, `TN_MOB_HORSE_CHESTNUT`, `TN_MOB_HORSE_CREAMY`, `TN_MOB_HORSE_DARKBROWN`, `TN_MOB_HORSE_GRAY`, `TN_MOB_HORSE_WHITE`, `TN_MOB_HORSE_SKELETON`, `TN_MOB_HORSE_ZOMBIE`

src/content/docs/mc/build.md

@@ -188,9 +188,9 @@ The project includes a clang-format configuration based on the Microsoft style:
 
 Notable settings: `InsertBraces: true` makes sure all control flow blocks have braces, and `ColumnLimit: 0` turns off line length enforcement.
 
-## Differences from LCEMP build
+## Differences from LCE build
 
-| Aspect | LCEMP | MinecraftConsoles |
+| Aspect | LCE | MinecraftConsoles |
 |--------|-------|-------------------|
 | Build system | Visual Studio `.sln` | `.sln` + CMake |
 | CI/CD | None documented | 3 GitHub Actions workflows |