Show Minecraft Java players how to explore Bedrock server content while they keep their Java client. Follow a player through real servers, appearance options, account menus, installation, and help.
Use Claude CLI with Opus 5.5 at high effort to rewrite the narrative. Check every claim against the filmed action and current player guide. Liam addresses experienced Minecraft players directly. Keep the narration concise and let the footage carry familiar actions.
Open with a real Java session on CubeCraft Bedrock. The first sentence identifies StackAnvil as a Fabric client mod that connects Java Edition to Bedrock servers. Use the first three clips to establish the mod, the Java installation, the Bedrock sign-in, and CubeCraft as a demonstration. Then play parkour. Do not explain familiar controls, NPCs, or inventories.
Connect each new section to what StackAnvil enables in Java. Keep a small client, mod, and server label visible after the scene title clears. Review the opening as a new viewer: they must understand what the product is before the server tour.
Visit Galaxite next. Use fresh footage of its world, characters, game selector, items, and emotes. Show Character Creator, Friends, and Realm Hub menus as player features. Show Economy SMP's Community story feed and weekly Timeline activity, including scrolling and week navigation. Show no unavailable Realm joins. Mention that B opens the emote wheel by default and that players can rebind it in Controls.
End with the website, the CurseForge Fabric add-on, the matching ViaFabricPlus download, and the connection steps. Emphasize Discord for help and GitHub issues for bug reports.
Exclude debug worlds, test fixtures, development explanations, technical route diagrams, Javadocs, and code contribution guidance from this video.
Record real Java gameplay on the parent's private display with zero gameplay volume. Use purposeful walks, gradual camera turns, short inspection pauses, and smooth pointer paths. Wait for the world to load before moving. Reject clips with loading failures or unintended falls through terrain.
Give each main scene its own take or a distinct chronological excerpt. Avoid overlapping footage within the main cut. Use the short composition for selected excerpts from the same shoot.
Keep credentials and account tokens private. The owner has approved showing the friends list without blurring names. Record the server, client build, connection route, action, and capture date in the ignored production manifest. Review the full trimmed clip before marking it ready.
Keep the existing forest, mint, paper, and rust palette. Use Anton for brief titles and Space Grotesk for captions and instructions.
Gameplay carries most of the story. Clear the large titles after four seconds, then retain the small context label. Installation and help graphics use aligned columns with consistent spacing. Avoid connection arrows and technology boxes.
The portrait cut has a separate script. Keep menus fully visible within their focus region. Use portraitMenus ranges for overlays during world shots. Keep subtitles and key actions away from platform controls.
Use Eleven v4 through the timestamped dialogue API. Use Liam and include the voice in the cache signature. Keep one second of decoded silence after the final aligned word, followed by the timeline hold. Derive captions from measured alignment.
Use a licensed instrumental and duck it under speech. Keep generated assets and their provenance private. Master at -16 LUFS and check the encoded true peak against the -1.5 dBTP ceiling.
Deliver landscape and portrait MP4s, burned captions, SRT and VTT files, thumbnails, and posting descriptions. Keep descriptions focused on players, downloads, and bug reporting. Credit upstream work and production assets briefly.
Run bun run posting and bun run posting vertical to export the upload package without rendering the MP4s again. The designed thumbnails use reviewed Galaxite model footage with "BEDROCK SERVERS FROM JAVA" and a "Fabric client mod" label. Inspect each image at full size and at mobile preview size.
Keep titles, introductions, and chapter group names in src/publishing.ts. Chapter timestamps come from the final timeline. Use useful player sections and merge short scenes so each chapter lasts at least ten seconds. The main description includes chapters. The Short uses its own title, introduction, and hashtags.
For authorized uploads, select Pistonmaster (@pistondev) in YouTube Studio. Verify the channel before uploading. Preserve the requested visibility and verify the saved metadata, custom thumbnails, and English caption tracks.
Inspect scene layouts and transitions. Review the complete exports and their soundtracks. Run the source checks and timing tests. Uploading is a separate action.