For the past month I’ve been completely obsessed with Zelda: Tears of the Kingdom and I’m almost done with the game 😭

I didn’t want that feeling of adventure and discovery to end yet, so I decided to create a fan-made cinematic reveal trailer for a fictional next Zelda game:

“The Legend of Zelda: Echoes of the Depths”

Built entirely in Melius using multiple nodes, agents, image generation, video workflows, transitions, and cinematic scene iteration, the goal was to recreate the emotional and stylized feeling of a real modern Nintendo reveal trailer while exploring how AI workflows can be used to prototype AAA game cinematics.

Disclaimer: This is a fan-made concept project. Nintendo has not announced or confirmed any such game.

Link: Project

#BuildInPublic #AI #Zelda #Nintendo #Melius

Awesome!

Title: The Graphic Novel Syndicate: A Fully Automated 60-Page Production Pipeline

Project Link: [https://app.melius.com/projects/c95de835-b21e-42cb-b77b-d11344bb6a92/canvas/feccc0eb-d8d4-4196-8dfd-21ee38fe6af0 ] Video Walkthrough: [https://youtu.be/lN5iBnjXkAw]

Project Description: Most creators use generative AI to create isolated images or short videos. I wanted to push Melius to its absolute architectural limits by building a fully automated, scalable production pipeline designed to generate a cohesive 60-page noir graphic novel. I successfully rendered 18 complete pages (over 100 panels) end-to-end, but I eventually hit the hard limits of both the UI performance (severe lagging) and my credit balance. However, the engine architecture itself is fully functional, proven, and ready to scale. It is not just a comic; it is a workflow-native engine designed for continuous storytelling.

Process Overview & Architecture (What I Used): To achieve absolute consistency without the system hallucinating or losing the plot, I structured the Melius canvas like a software backend, utilizing multiple node types:

Phase 1: The Master Brain (World Building LLM) I started with a primary LLM node acting as the "Showrunner." Given a single seed sentence, it generated a comprehensive "Story Bible," locking in the overarching plot, environmental aesthetics, and strict character design rules.

Phase 2: The Logic Parsers (Workflow Routing LLMs) To prevent data overload, the output from the Master Brain is fed into secondary, specialized AI Text Nodes. These act as logical routers. They parse the master script and isolate exact prompts for specific panels, ensuring each downstream image node receives only the precise data it needs.

Phase 3: The Render Array (Parallel Text-to-Image) The parsed prompts are fed simultaneously into a battery of Image Generation nodes (Flux/Grok). This parallel array generates the raw pages (6 panels at a time) maintaining the high-contrast noir aesthetic dictated by the Master Brain.

Phase 4: The Cinematic Climax (Start/End Frame Video & Audio) To fulfill the ">1 node type" requirement and add a massive "wow" factor, the final panels of key scenes are routed into Image-to-Video and Audio (ElevenLabs) nodes. By feeding Panel A (Start Frame) and Panel B (End Frame) into the video model, the engine creates hyper-smooth, logical cinematic transitions for the story's climax, complemented by epic sound design.

Extensiveness of Agent Use: The Melius Agent was my co-architect throughout this build. I utilized the Agent to help design the logical flow of the parsing nodes. When dealing with the massive data flow from the Master LLM to the 6-panel Render Array, the Agent helped structure the prompt extraction logic, ensuring the "spaghetti wiring" remained functional and the data routed correctly to the visual generators.

Feedback on Experience Using Melius: The Highlights & UI Experience: This is arguably the first AI agent I've encountered capable of genuinely grasping complex, high-level structural requests. While I am highly accustomed to the deep technicality of complex node-based tools like ComfyUI, Melius offers a brilliant contrast: the visual canvas is incredibly clean and accessible. The ability to visually orchestrate AI collaboration is phenomenal.

Areas for Improvement (Stress-Test Feedback): Because I pushed the platform to its limits with this massive pipeline, I found a few severe bottlenecks:

Credit Exhaustion from Deep R&D: My ultimate goal was to finalize the entire 60-page project to the highest possible polish, but I hit hard credit limitations after rendering 18 pages. I burned through a massive portion of my credits purely on R&D—extensively testing different model outputs, probing the Agent's comprehension limits, and figuring out exactly how far and how deep I could push the node architecture before it broke.

Performance & Batch Errors: The web app currently struggles under heavy production loads. By the time I reached 18 pages, I experienced choppy canvas navigation and frequent errors when queuing multiple generation batches.

Wiring Logic at Scale: In massive multi-node networks, the Agent occasionally lost track of correct connections. It would claim everything was wired perfectly, but upon explicit prompting to double-check its work, it would discover its own routing errors.

Pre-Run Cost Estimator: A massive UX improvement for power users would be implementing a built-in UI feature that analytically calculates the exact credit cost of the entire node tree before hitting "Generate," rather than relying on the Agent's estimates.

Custom LoRAs: Adding support for custom LoRAs would be the ultimate upgrade for maintaining absolute character consistency in sequential art pipelines like this one.

wow i didn't even know our agent was capable of this