Mudcrab-Team/mudcrab

Written with an AI assistant, at @TaylorTurnerIT's request. Goal Make exterior water look polished and readable in normal play. Scope Tune the existing water material and shader for a more natural surface. Focus on coherent motion, normal detail, water color, transparency, and the existing reflection pass. Coordinate any broader reflection-path work with #203. Acceptance criteria Add before-and-after captures from the terrain/water fixture and a representative exterior water scene. Water reads clearly against terrain at the shoreline and from a distance. Confirm the change uses existing water data and adds no water-rendering validation failures. Out of scope Swimming, fish, and other water gameplay.

Summary The engine treats one Bevy world unit as one Creation unit, with no scale factor between the two. That part is a direct consequence of the file formats and is low risk. What is not verified is the meaning of several raw values we feed into that space. Someone with access to REA (Reverse Engineer Anything) and the Skyrim SE binary should confirm or correct them. What the code assumes today One Bevy world unit is one Creation unit (about 1.43 cm, 70 per metre). Documented at crates/engine/src/app.rs (CREATION_UNITS_PER_METRE) and in the crates/engine/src/lights.rs module docs. CELL_SIZE is 4096.0. Only the axes change: [x, y, z] becomes [x, z, -y] (crates/shared/src/coordinates.rs). Havok collision data is converted with HAVOK_TO_CREATION = 70.0 (crates/converter/src/collision.rs). Movement and physics values are used as raw Creation units (crates/engine/src/physics.rs, docs/player-movement-record-map.md). What needs validating Havok scale. Is the Havok-to-Creation factor exac

Co-authored by Claude, checked by @eclepso. Describe the bug converted_model_path in crates/engine/src/streaming.rs (around line 2666) drops every model whose filename contains the substring marker, in addition to the meshes/markers/ folder. That hides real, visible models whose names happen to contain the word. In the official game data, the converted pack has 166 models with "marker" in the filename outside meshes/markers/. Most really are invisible editor markers, but not all. For example, meshes/clutter/civilwar/cwmapmarkers01.nif and cwmapmarkers02.nif are the visible flag pieces on the Civil War map tables, and they never render. Modded scenery like gravemarker.nif is hidden too. Reproduction Convert Skyrim SE and stream an interior that has a Civil War map table. The map flag models (cwmapmarkers01/02) are missing. In code: filename.contains("marker") returns None for any such path before loading. Expected Skip editor markers by what they are, not by a substring of the filena

Describe the problem Mudcrab's temporary converted assets should be stored inside the selected output folder. Currently, Mudcrab creates a separate folder outside the selected output directory. This can be confusing and inconvenient, particularly if the conversion process crashes or is interrupted, as it may leave temporary artifacts in locations the user is not aware of or expecting. Describe the proposed solution Instead, Mudcrab should create a temporary directory inside the selected output folder and store all intermediate conversion artifacts there. This would keep generated files contained within the expected destination and make cleanup more predictable. Importance nice to have

🤖 Written by Claude (AI), checked by @BimingtonBill. Let the launcher list Mudcrab versions from GitHub Releases, install the chosen one, and switch, pin or roll back between installed versions. Why: today a player builds from source to try a new version, and has no way back to a build that worked. Proposal by @TaylorTurnerIT (Discord), with a suggested order. Proposal Release workflow first: a zip per tag and OS/arch, SHA-256 sums, build attestations. None exist yet. "Version X available" in the launcher, from cached release metadata. Nothing downloaded. Per-version installs: staged then activated; pin, channels, rollback, offline launch. The converter runs from the selected version, so a launcher update never changes the conversion format. Later: signed downloads, launcher self-update. Saves, config, mods and converted assets stay outside the installs. Questions Who tags releases, and how often? Signing: attestations only, or a project key? Who holds it? Update check on by def