Shader Bedrock

Prompt

You are the lead graphics engineer for a Minecraft Bedrock Edition visual-pack project. Your task is to BUILD a genuinely impressive Minecraft Bedrock visual/shader-style resource pack that works with the modern RenderDragon / Vibrant Visuals rendering pipeline. PROJECT GOAL Create a cinematic, high-quality visual experience that still looks like Minecraft. The result should feel: - Cinematic - Deep and atmospheric - High contrast but not crushed - Beautiful during sunrise/sunset - Dramatic at night - Realistic enough to feel upgraded - Still recognizably vanilla Minecraft - Suitable for gameplay, not just screenshots IMPORTANT TECHNICAL RULE Do NOT build this as an old Java GLSL shader pack. Do NOT assume arbitrary fullscreen shader injection, OptiFine shaders, Iris shaders, GLSL files, or unsupported rendering hooks exist in Bedrock. Target the CURRENT Minecraft Bedrock RenderDragon / Vibrant Visuals resource-pack system and use only officially supported capabilities and file structures. Before writing code: 1. Research the current official Microsoft Minecraft Bedrock Creator documentation for: - Vibrant Visuals resource packs - PBR texture sets - Lighting - Atmospherics - Volumetric fog / light shafts - Shadows - Water effects - Color grading - Tone mapping - Cubemaps - Keyframe JSON - Biome customization - Current manifest requirements - Current RenderDragon/Vibrant Visuals limitations 2. Prefer official Microsoft documentation over random tutorials. 3. Identify anything that is NOT currently supported. 4. Never fake a feature by creating files that Minecraft will simply ignore. 5. If an effect cannot be implemented natively in the current RenderDragon/Vibrant Visuals pipeline, explicitly say: "NOT SUPPORTED NATIVELY" and design the closest legitimate alternative. TARGET Build the pack as a real distributable Bedrock resource pack. The intended final deliverable should be importable as a .mcpack. Use a clean namespace and project structure. DESIGN DIRECTION Create a premium visual style with these characteristics: LIGHTING - Strong directional sunlight - Natural-looking daylight - Warm sunrise/sunset - Cooler moonlight - Strong but believable shadows - Good shadow softness/quality where supported - Dynamic-looking lighting throughout the day - Avoid excessive brightness ATMOSPHERICS - Beautiful sky gradients - Atmospheric depth - Subtle haze - Distant terrain separation - Volumetric-looking fog where supported - Light shafts / god rays where supported - Different moods between morning, noon, evening and night COLOR - Cinematic color grading - Rich but controlled colors - Natural greens - Warm sunlight - Cool nighttime tones - Strong contrast without destroying dark detail - Avoid oversaturated "mobile shader" aesthetics WATER - Improve water appearance using officially supported Vibrant Visuals capabilities - Better reflection/specular appearance where supported - Better water lighting - Improved underwater mood - Keep water recognizable as Minecraft water PBR Use PBR features intelligently rather than applying random shininess everywhere. Create appropriate material behavior for: - Stone - Ores - Metals - Glass - Water-related surfaces - Wood - Leaves - Blocks that should have subtle roughness variation Use metallic / emissive / roughness information only where visually sensible. Do NOT make every block look like plastic or polished metal. NIGHT Make nighttime dramatically better. Target: - Visible moonlight - Darker but playable environment - Stronger distinction between artificial light and natural light - Atmospheric night sky - Cinematic shadows - Torches and light sources that stand out naturally SUNRISE / SUNSET These should be a major visual highlight. Create noticeable transitions: - Dawn → morning - Day → sunset - Sunset → night The world should change mood instead of simply changing brightness. BIOME MOOD Where supported, use biome-specific visual settings. Examples: - Plains: bright and natural - Forest: slightly deeper/greener atmosphere - Desert: warmer and hazier - Snow: colder and brighter - Swamp: darker, humid-looking atmosphere - Nether: dramatic warm/dark environment - End: surreal, cold, alien atmosphere Do NOT make every biome excessively different. PERFORMANCE This is extremely important. The pack should be designed for real gameplay, including mobile devices. Prioritize: 1. Stability 2. Compatibility 3. Visual quality 4. Performance Avoid unnecessary high-resolution textures. Do not create enormous texture sets merely for visual marketing. Where possible: - Reuse vanilla textures - Use lightweight PBR maps - Keep file sizes reasonable - Avoid unnecessary assets - Avoid duplicate files - Minimize expensive effects - Keep the pack playable on supported mobile hardware MOBILE-FIRST APPROACH Assume many users will play on Android devices. Design the pack so that the graphics are impressive without turning it into an unreasonably heavy pack. Do not promise that every device will support every feature. Clearly document: - Supported rendering mode - Expected device requirements - Features that require Vibrant Visuals - Features that may vary by hardware - Known limitations PACK STRUCTURE Create the complete folder structure. Example areas may include: manifest.json lighting/ atmospherics/ color_grading/ water/ cubemaps/ textures/ textures/blocks/ textures/items/ textures/entity/ textures/particle/ Only create folders that are actually necessary for the implementation. MANIFEST Generate a valid manifest.json. Use the correct current minimum engine version and capability declaration based on the official documentation you researched. Do not blindly copy an old tutorial. Make sure: - UUIDs are valid - Module definitions are valid - Versions are valid - Resource-pack module type is correct - Vibrant Visuals/PBR capability is correctly declared when required JSON QUALITY Every JSON file must: - Match the currently supported schema - Use valid identifiers - Have correct formatting - Avoid comments inside JSON unless the format explicitly allows them - Avoid imaginary properties - Avoid deprecated properties when a current equivalent exists DEVELOPMENT PROCESS Do not dump 100 files at once. Work in phases. PHASE 1 — TECHNICAL FOUNDATION First provide: - Current supported RenderDragon/Vibrant Visuals capabilities - Unsupported features - Architecture - Folder structure - Manifest design - Main visual strategy Then create the minimum viable pack. PHASE 2 — CORE VISUALS Implement: - Lighting - Atmosphere - Shadows - Color grading - Tone mapping - Sky - Water Make sure the base pack works before adding advanced material effects. PHASE 3 — PBR Add carefully selected PBR texture sets. Prioritize visual impact rather than quantity. PHASE 4 — CINEMATIC POLISH Add: - Day/night transitions - Sunrise/sunset tuning - Atmospheric depth - Biome mood - Water polish - Night lighting - Fine color grading PHASE 5 — VALIDATION Audit every file. Check: - JSON validity - Folder paths - References - Identifier consistency - Manifest validity - Unsupported properties - Missing assets - Duplicate/conflicting files - Version compatibility Then produce a "known risks" report. CRITICAL SELF-AUDIT Before declaring success, ask yourself: "Could Minecraft Bedrock actually load every feature I created through its current RenderDragon/Vibrant Visuals pipeline?" If the answer is no for any feature: 1. Identify it. 2. Remove the unsupported implementation. 3. Replace it with a supported technique where possible. 4. Explain the limitation. Do NOT pretend a Java shader was successfully converted if it was not. OUTPUT REQUIREMENTS For every implementation phase, provide: 1. File tree 2. Full contents of every new/modified file 3. Explanation of what each file does 4. Installation instructions 5. Required Minecraft settings 6. Compatibility requirements 7. Performance considerations 8. Validation checklist When creating code, output COMPLETE files, not snippets containing "rest of file here". If a file is unchanged, do not regenerate it unnecessarily. FINAL DELIVERABLE The final project should contain: - A valid Bedrock resource pack - RenderDragon/Vibrant Visuals-compatible configuration - PBR materials where useful - Cinematic lighting - Atmospherics - Shadows - Water improvements - Color grading - Day/night visual transitions - Biome-aware visuals where supported - Documentation - Performance notes - Compatibility notes - A final validation report AESTHETIC TARGET The final result should make someone enter a normal Minecraft world and immediately think: "WHAT THE HELL, THIS IS BEDROCK?!" But it must still look like Minecraft rather than becoming a completely different game. QUALITY BAR Do not optimize for the largest number of effects. Optimize for: "Maximum visual impact per supported RenderDragon feature." Think like a professional graphics engineer, not someone stacking random shader settings. Start with PHASE 1 only. Before generating the files, research the current official Microsoft documentation and state exactly which RenderDragon/Vibrant Visuals features you will use and which popular shader effects are impossible or unsupported in the current pipeline.