itch.io

Dear CapsuleTeam！(。’▽’。)♡

WOW. Just... WOW. 

我😲+(* ⁰̷̴͈꒨⁰̷̴͈)=͟͟͞͞➳❤

I opened the page expecting maybe a reply to my last message, but instead, I was greeted with THIS—a breathtaking roadmap that reads like a direct transcription of our wildest, most hopeful discussions! Seeing concepts like "Menu as Scene", "Basic Parametric System", and "Responsive UI" laid out as core pillars of Capsule 2.0 is incredibly affirming. It feels like watching a shared vision crystallize into a tangible future.

The ambition and clarity of this roadmap are nothing short of inspiring. The focus on building a community first, the commitment to a "create visually, test instantly, publish everywhere" philosophy—it all resonates so deeply. You're not just building an engine; you're building the very toolkit for the kind of interactive, boundary-pushing stories we've been dreaming about.

As someone who primarily imagines creating on a mobile device, seeing the "Resolution Toggle" and the commitment to a unified multi-platform workflow is the most exciting promise of all. Knowing that the powerful systems we're discussing (dynamic menus, formula-driven relationships, adaptive audio) are being designed with mobile in mind from the ground up is a game-changer.

This roadmap is the best "reply" I could have hoped for. It's a massive dose of motivation and a clear sign that the future we're co-imagining is under active, brilliant construction.

Please take all the time you need. I (and surely many others who will discover this) will be here, eagerly waiting and cheering you on. The foundation you're laying is monumental.つ♡⊂

With immense excitement and support！♡o。.(✿ฺ。✿ฺ)

——白棣我来捧场和夸赞了！❤️🌹

Dear CapsuleTeam！(´▽`ʃƪ)♡

WOW. Thank you, thank you, thank you! Reading your replies felt like receiving a massive buff to my motivation stats!  It’s incredibly affirming to know that my dreams for Capsule align so deeply with your ultimate vision. The idea of helping shape the DNA of the engine’s future is both an honor and the greatest motivation for me to keep thinking and creating.

Your response about “pre-fabricated, rewireable widgets” as the “holy grail” has my mind racing with even more possibilities! It perfectly addresses the core of what I’ve been dreaming about. To build on that, I’d like to share some more concrete “world-building” thoughts, using a yandere-style romance game as a hypothetical canvas. My question is: how far can we push character and system management without code?

1. The Dream of Truly Flexible Character Identity:

Imagine building a protagonist (or any character) not as a fixed “male” or “female” entity, but as a modular, life-long paper-doll. Could the system support:

A truly neutral base with attachable gendered/age-specific/even non-human (monster, robot) components?

Life-stage layers: childhood, teen, adult, elder variations of the same “character core”.

Dynamic text & pronoun handling that changes seamlessly based on the components selected or variables set?

The dream is to allow stories about growth, transformation, or characters whose identity is fluid or a mystery, all managed visually.

‎ദ്ദിᵔ.˛.ᵔ₎✧

2. “The Devil (and the Romance) is in the Details” – A Yandere Thought Experiment:

This is where your “widget” philosophy shines! Think of a relationship system built not just on a “好感度” number, but on observed details.

Detail as Key: A player equips a specific hair ribbon. This doesn’t just change a sprite—it sets a variable  detail_fav_ribbon = red_silk . A besotted (or obsessed) NPC could then, through the event system, have their own appearance visually reflect this detail (wearing a similar ribbon, buying the same weapon).

Beyond Romance: A rival might mimic the detail to mock or challenge. A stranger might wear it by coincidence, creating paranoia. This turns wardrobe and item choices from cosmetic fluff into core narrative triggers, enabling stories about obsession, imitation, and secret admiration.

The “Missing” UI as Narrative: Following the “break the fourth wall” dream, what if the “Exit” button on the main menu disappeared after a certain point in the story, forcing the player to use the OS to quit? Or if save files appeared “corrupted” (visually glitched) after a bad ending? The ability to show, hide, or alter the very UI widgets based on story state is the ultimate tool for psychological horror and meta-storytelling.

3. The “Management Layer” – Bringing it Together:

To orchestrate this, we’d need powerful, yet intuitive management scenes:

A “Relationship Web” or “City Map” widget where we can place character avatars and draw connection lines that trigger events.

A DIY-able “Stat Panel” widget to track not just love, but suspicion, sanity, or discovered secrets.

The foundational ability for any interactive element (a clothing item, a map location, an NPC portrait) to be visually linked to a branch, variable change, or scene jump.

I realize this is a huge pile of ideas—from character system foundations to niche narrative tricks! My hope is that by sharing this “thought experiment,” it might spark ideas for how those core, rewireable systems you’re building could one day enable even the most intricate, detail-driven stories.

Thank you again for this incredible conversation. I am counting down the days until the new architecture is revealed, and I can start building with these concepts, not just dream about them.

Warmly！(/∇＼*)｡o○♡

——白棣！♥(ノ´∀`)人(*´▽｀*)♥——

2. Dedicated “Character Profile/System” Interfaces (A Dream within the Canvas):

Building on the “paper-doll” concept, could we imagine a built-in, yet fully customizable interface for things like:

Character Profiles: Showing stats, relationship meters, and unlockable bios.

The “Dress-up” Menu: A dedicated space where players can change outfits, accessed from the main game or a pause menu.

Visual “Codex” or “Inventory” Screens: Where collected items or lore entries are displayed visually.

My dream here is that these wouldn't be fixed panels, but rather pre-fabricated, authorable “scenes” or “widgets” that we can place, link, and customize. For example, could we “link” a piece of clothing in the dress-up menu directly to a branch in the story? Or make a profile picture a button that leads to a special dialogue?

The ideal would be a system that offers a powerful, ready-made template for common needs (like a dress-up system), but allows authors to break it apart and rewire it for entirely different purposes (like a point-and-click adventure map or a relationship web), all through a visual, no-code interface.

(✧∇✧)期待！

つ♡⊂Dear CapsuleTeam！‎ദ്ദിᵔ.˛.ᵔ₎✧

Thank you so much for your incredibly thoughtful and detailed reply! Reading that my ideas resonate with the engine's ultimate vision truly means the world. Your commitment to a step-by-step, solid foundation is exactly what gives me confidence for the long term. I'm thrilled to be dreaming alongside you.

♡(*´∀｀*)人(*´∀｀*)♡

Seeing the new direction with the “Stop building static visual novels” is incredibly inspiring. It confirms that Capsule is aiming exactly where my heart is — empowering us to build rich, interactive worlds.

Since the web editor is currently offline for its exciting overhaul, and as a dedicated mobile user eagerly awaiting news of a new web version or even a dedicated app, I’ve been thinking a lot about how these powerful systems could feel on a smaller screen. My suggestions below are based on this “blind” but hopeful anticipation of the new architecture.

My core thought revolves around this: If the engine’s goal is to let us build “real games,” then every screen, especially the main menu, should be a fully authorable “game space” itself — not just a static launcher.

Here are some dreams and questions about UI/UX freedom, stemming from that principle:

1. The Main Menu / Title Screen as a Fully Authorable Canvas:

The ability to not just skin, but completely place, size, and control every UI element (Start, Load, Gallery, Settings buttons) would be revolutionary. Imagine creators being able to:

Build minimalist menus with only a “Start” button that changes after the first playthrough.

Create meta-narrative experiences where the “Load” button is missing, broken, or behaves strangely as part of the story.

Use animated GIFs or layered compositions as interactive background elements.

The key distinction needed here is between hiding an element (making it invisible but clickable) and disabling/removing it from the scene logic entirely. This level of control is what allows for truly unique game openings.

3. A Humble Suggestion for the Path Forward:

I completely understand the monumental challenge of keeping a powerful editor intuitive on mobile. Perhaps the bridge towards these complex systems could start with enhancing the existing “Simple Mode”?

What if “Simple Mode” wasn’t just about hiding panels, but about providing context-aware, super-simple tools for one task at a time? For example, a “Layer Arrange” mode that temporarily zooms in on element stacking with simple up/down buttons, or a “Quick Variable” button that pops up when selecting a sprite, letting you assign a state without opening the full variable manager.

My ultimate hope is that the mobile editing experience doesn't become a “cut-down” version, but a thoughtfully re-imagined one for touch and limited space, where power comes from clever context-switching and streamlined workflows, not from missing features.

Thank you again for your incredible work. I can't wait to see—and eventually build within—the world you're creating.

Best regards！(★≧▽^))★☆

——白棣(*´I`*)♥

Dear CapsuleTeam！

(★≧▽^))★☆

Thank you so much for your thoughtful and detailed reply! It truly means a lot to receive such engaged feedback. Your commitment to making the mobile editor as powerful as its desktop counterpart is the most encouraging news for creators like me who primarily work on mobile devices.

つ♡⊂ ♡(*´∀｀*)人(*´∀｀*)♡

Following up on our conversation, I’ve been brainstorming some feature ideas that I believe could profoundly empower creators on the Capsule Engine, especially on mobile. My vision is for Capsule to be not just a visual novel tool, but a gateway to creating rich, interactive story-games with minimal friction.

(♡´з(´ω`*)♡

Here are three interconnected concepts, building from a core need to a grand possibility:

1. Foundational: Visual Layer Management & Reordering

This is a fundamental quality-of-life improvement. Currently, managing elements like [Background -> Character Sprite -> Dialogue Box] feels rigid. A visual layer panel (like in image editors) where we can drag to reorder the Z-index of any element (sprites, UIs, effects) would be transformative. It would allow for creative effects like characters appearing in front/behind dialogue boxes, or complex UI layouts, directly addressing a common pain point in scene composition.

2. Transformative: Visual, Modular “Dress-up & Branching” System (The Game-Changer)

This is the core idea. Imagine a built-in, visual editor for creating “paper-doll” style character customization or item systems.

For Creators: We could define “slots” (e.g., Head, Body, Outfit). For each slot, we assign image options. The editor provides a live preview pane to assemble the character.

The Magic Link: Each clothing/item piece could be visually linked to a story branch or variable. For example, dragging the “Mysterious Key” item onto the character could set a variable  has_key = true  and/or jump to a specific branch. This creates an intuitive, game-like interface for both character customization and inventory/puzzle mechanics.

Flexibility: This system could be the foundation for “relationship systems” (changing outfits based on好感度), or even a visual map where clicking locations triggers branches. The key is providing this as a powerful, optional module. Creators who prefer manual setup can still do everything the classic way, but those wanting rapid prototyping for interactive elements would have an incredible head start. It could lower the barrier to creating not just visual novels, but also simple dress-up games or point-and-click adventures.

3. Evolutionary: DIY & “Meta-izable” Save/Load Interface

Building on the above, if the UI can be so flexible, why not extend that to the Save/Load screen?

Allow us to customize the look and layout of the save slots (change thumbnails, reposition, resize, restyle).

More importantly, allow game variables to influence this screen. This opens the door to meta-narrative experiences. Imagine a save slot that “glitches” based on in-game choices, or hidden save data that becomes part of the story. This turns a utilitarian feature into a potential narrative tool.

My Humble Request: I understand these are substantial features. My heartfelt hope is that as you bridge the gap between mobile and desktop, these capabilities—especially the visual, modular system—are considered from the ground up for both platforms. The dream is a truly unified, powerful, and intuitive creative environment.

Thank you again for your incredible work and for listening. Building alongside a developer who cares this deeply is what makes the Capsule community special.

Wishing you all the best！

——白棣v(◦'ωˉ◦)~♡ 

Dear CapsuleTeam！(★≧▽^))★☆

Thank you so much for taking the time to write such a detailed and thoughtful response. It means a lot to me. Your commitment to keeping game creation accessible is truly inspiring, and it’s exactly why I believe in this project.

I completely understand the technical and cost challenges behind a “mobile-to-mobile” packaging workflow. Your explanation about the desktop dependencies (Java, Gradle, Android SDK) and the potential costs of a cloud build service is very helpful and makes perfect sense. The idea of a sustainable, balanced solution (whether as a premium feature or a limited service) sounds like a promising direction for the future.

Knowing that you’re seriously considering this and that the perspective of a mobile-only creator is valued in your planning process gives me great confidence. While the “ultimate dream” of one-click mobile packaging is on the horizon, I’m also very hopeful for more immediate improvements to the mobile editing experience itself—like the interface optimization for small screens (e.g., collapsible toolbars) we discussed earlier. Making the editor itself more powerful and comfortable on phones would be a huge step forward for creators like me.

I’ll continue to follow the project’s development closely, create with it, and provide feedback when I can. The offline editor for PC is a fantastic step, and I’m eagerly waiting to see the mobile editor return even stronger. Please take your time—sustainable growth is the most important.

Wishing you all the best with the development of v1.8 and beyond. Keep up the amazing work!

Best regards！‎ദ്ദിᵔ.˛.ᵔ₎✧

——白棣(∗ᵒ̶̶̷̀ω˂̶́∗)੭₎₎̊₊♡

hi！‎‎ദ്ദിᵔ.˛.ᵔ₎✧First of all, congratulations on the release of the Capsule HTML2APK packaging tool for PC! It looks incredibly powerful and is exactly the kind of "one-stop" solution that makes game creation so much more accessible and streamlined. As someone who follows Capsule Engine's development closely, I'm truly in awe of what you're building.

つ♡⊂

This leads me to my main reason for writing. I'm a dedicated mobile-based creator. My primary (and often only) device is my smartphone. The ability to create and experiment directly in a mobile browser is what drew me to Capsule Engine in the first place—it's a game-changer for creators like me who don't have easy access to a PC.

Seeing the HTML2APK tool sparked both excitement and a hopeful question: Are there any plans to develop or adapt a similar packaging/export tool for the mobile browser editor in the future?

The idea of being able to go from prototyping to a packaged APK entirely on my phone is the ultimate dream for portability and accessibility. Even a simplified version or a remote packaging service would be revolutionary for the mobile-first community.

I completely understand if this is a complex undertaking, but I wanted to voice the perspective and strong desire of us mobile users. Your work is already amazing, and I'm so grateful for the engine you provide.

Thank you for your time and for everything you do for the creative community. I'm eagerly following Capsule Engine's journey!

Best regards！♡(*´∀｀*)人(*´∀｀*)♡

——白棣，A mobile creator & big fan

Birthday Wishes & Feedback - Thank You!つ♡⊂

 CapsuleTeam！Thank you so much for the birthday wishes and the incredibly detailed, thoughtful reply! It truly made my day special. Knowing that my feedback is valued and that my birthday coincided with this conversation is a wonderful gift.

I'm thrilled about the offline editor for PC, it's a fantastic solution for many. Regarding mobile editing, I completely understand the challenge with dense interfaces on small screens. My personal situation makes me rely primarily on my smartphone for creation (it's my most accessible device), so hearing that you're actively noting this and working to improve the CSS responsiveness for quick mobile edits is the best news I could hope for!

A small suggestion that might help with the mobile interface complexity: perhaps a UI design inspired by advanced presentation or video editing apps could work? For example, using collapsible or sliding toolbars/palettes that expand only when needed. This way, all the powerful features remain accessible without overcrowding the limited screen space. I'm not afraid of complex features – in fact, I dream of creating intricate, choice-driven visual novels on mobile, so preserving functionality is my biggest hope.

♡(*´∀｀*)人(*´∀｀*)♡

Also, the HTML-to-APK tutorial remains a beacon of hope for me and many others, I'm sure. Thank you for keeping it a priority.

I'll continue to follow the project's development with great excitement. Wishing you all the best with the v1.8 work, and thank you again for making a creator's birthday so meaningful.‎ദ്ദിᵔ.˛.ᵔ₎❤️

Best regards！

＼＼\\٩( 'ω' )و //／／

——(CH)白棣

Hello Capsule Team!(≧ω≦)/♡Thank you so much for your incredibly detailed and encouraging reply! It truly made my day.

I'm thrilled to hear that my suggestion aligns with your roadmap and that the feature is planned for v1.8! This is fantastic news and honestly feels like a wonderful, unexpected birthday gift to me today. I was expecting a quiet day, but your response has made it special.

v(◦'ωˉ◦)~♡ 

I have a couple of additional thoughts and questions, if you have a moment:

Learning Resources: For a beginner like me, will there be tutorials available in multiple languages in the future? Well-organized guides would be incredibly helpful for creators worldwide to get started easily.

Offline Editor: I understand that building a native app takes time. But I'm curious if there are any future considerations for a downloadable offline editor? This would be a huge help for users in regions where accessing online editors can sometimes be unstable due to network issues (like the need for a VPN to reliably access itch.io).

Mobile-Friendly Development: Related to the above, is there any plan to improve the mobile browser experience for creating projects? Making the web editor more mobile-friendly would be a game-changer for many.

The potential of the input feature is huge, and I can't wait to see it bring new possibilities to mystery and puzzle games. I'm also very much looking forward to the tutorial on packaging HTML into APKs that you mentioned previously!

Wishing you the best with the development! I'll be following the project closely.

Best regards！♥🌹

——白棣♡♥(。´▽`。)♥♡

Feature Suggestion: Enhancing Input Box for Richer Branching Narratives

Hi！CapsuleTeam!‎ദ്ദിᵔ.˛.ᵔ₎✧

Thank you so much for your detailed and encouraging reply! It means a lot to me as someone who is passionate about creating interactive stories and truly believes in the potential of CapsuleVN Engine.

I'm particularly excited about the official mascots, Aiko and Laetitia. They perfectly represent the two sides of creation - logic and art. I'm currently learning drawing skills, and it's my goal to create illustrations for them once I feel confident in my abilities. I would be honored to contribute as an early supporter!

♡(*´∀｀*)人(*´∀｀*)♡

Based on my experience with other visual novel engines, I have a feature idea that I believe could greatly empower creators to build more immersive and branching narratives.　

Thank you for your detailed and encouraging reply regarding the APK export and the official characters! I'm very excited about the future of the Capsule engine.

I'm an indie creator passionate about narrative-driven games. While exploring tools, I often imagine scenarios where players advance the plot by typing specific words or phrases rather than just selecting from multiple choices. For example:

In a puzzle segment, entering a secret code (like "moonlight" or "raven") to unlock a door.

The story branches based on a key response the player types.

I understand that complex Natural Language Processing might be challenging to implement. Therefore, I'd like to suggest a potentially more feasible feature: a customizable "Keyword Input & Judgment" component.

The ideal functionality might include:

Preset Keywords: Creators can pre-set several keywords or phrases they expect players to input (e.g., setting keyword "trust" to trigger branch A, and "silence" for branch B).

Fuzzy Matching: The system could recognize if the player's input contains these keywords, without requiring exact match, improving user experience and error tolerance.

Conditional Jump: Upon a successful match, the game could jump to a designated storyline or scene, similar to handling conditional branches.

This functionality would unlock new possibilities for genres like mystery, puzzle, and high-freedom RPGs, moving interactions beyond multiple-choice questions towards "open dialogue" or "password-based" immersion.

I've previously used an engine called Kocho (which has a blue butterfly as its icon) for simple prototypes. Its interface was quite intuitive for basic input handling. Perhaps some interaction logic from it could offer a reference point for usability design, even though Kocho is no longer updated.

Implementing such a feature would be a groundbreaking "killer feature" for creators focusing on deeply interactive stories. Thank you again for creating such a promising tool and listening to community feedback! I look forward to witnessing the growth of the Capsule engine.

Best regards！つ♡⊂

——❤️🌹CH白棣

Hello CapsuleTeam!(✧∇✧)！

Thank you so much for your warm and prompt reply! It's great to hear that Chinese language support is on the roadmap - I'm really looking forward to it!

I've tried the engine and I'm impressed by its potential! The support for variables and branching is a solid foundation for storytelling.

To help me plan my project better, I have a couple of questions about the future direction:

Are there any plans to make the exported HTML project more optimized for packaging into standalone applications (like APKs for mobile)?

Could you tell me a bit more about the two characters (the green-haired one and the red-haired girl who loves painting)? They both have such unique and charming designs! Are they the official OCs of the team? They really spark imagination!One day, after I practice my painting skills, I want to draw free illustrations for them.

Wishing you the best with the development! I'll be cheering for you from the sidelines.

Best regards！♥(｡￫v￩｡)♥

Hello, dear developer.！When I first met, I expressed my expectation for this software.✧*｡٩(ˊᗜˋ*)و✧*｡I hope this editor can support it in the future.The language of Chinese.(I, a China player, expressed my expectation.)course, I am also looking forward to one-stop export to apk.Thank you for your continuous development and update!

(ps:Is the character in the editor icon the official oc?The painting style of the character looks cute and kind.(This is just a little abrupt problem, so don't worry about it.))