<h2 id="fix:-version-1.2.1-the-&quot;stable-index&quot;-patch">Fix: Version 1.2.1 – The "Stable Index" Patch</h2>This update addresses the "Widget Shuffling" bug discovered in earlier versions.Special thanks to <a target="_blank" rel="ugc" href="https://civarchive.com/user/wrOngplanet">wrOngplanet</a> for reporting this issue.🛠 The Fix: Stable Widget IndexingIn previous versions, refreshing the browser or reloading a workflow could cause ComfyUI to "shuffle" settings (e.g., your filename becoming <code>true</code> or checkboxes turning into text).⚠️ Known Issues<ul><li>UI Focus Requirement: The "Prompt Display" inside the node only updates in real-time if the ComfyUI browser tab is currently in focus.</li><li>Why? ComfyUI (and most browsers) limit JavaScript execution for background tabs to save system resources.</li></ul><h3 id="update:-version-1.2-native-ui-display-and-internal-cleanup">🚀 Update: Version 1.2 - Native UI Display &amp; Internal Cleanup</h3>The Wildcard Saver just got a major upgrade to make your prompt engineering workflow even faster. he node now features a built-in display.The saved text is "hammered" directly into the node's UI, allowing you to see your LLM-generated prompts in real-time without needing extra nodes.<h3 id="how-to-install-v1.2:">How to Install v1.2:</h3><ol><li>Locate your ComfyUI directory: Go to the folder where you installed ComfyUI.</li><li>Open the Custom Nodes folder: Navigate to <code>ComfyUI/custom_nodes/</code>.</li><li>Drop the folder: Drag the entire <code>WildCardSaver</code> folder (containing the <code>.py</code> files, the <code>__init__.py</code>, and the <code>js</code> subfolder) into that directory.</li><li>Restart ComfyUI: Once you restart, the system will automatically read the <code>__init__.py</code> and load the new JavaScript UI features.</li></ol><h3 id="why-this-works-seamlessly:">Why this works seamlessly:</h3><ul><li>Automatic UI Loading: The <code>__init__.py</code> file contains a <code>WEB_DIRECTORY = "./js"</code> instruction. This tells ComfyUI to automatically load the <code>wildcard_saver.js</code> script into your browser for the new "Show Text" feature.</li><li>Self-Contained: Everything needed for the new native text display and the string output slot is contained within that one folder.</li><li>Fully Offline: No external downloads or internet connections are required; the node runs entirely on your local hardware. Wildcard Saver: Quick Start</li></ul>The Wildcard Saver node is a utility for ComfyUI designed to capture and store text strings—such as prompts, subjects, or styles—directly into <code>.txt</code> files. This is perfect for building your own custom wildcard libraries on the fly without leaving the ComfyUI interface. 1. Key Features<ul><li>Dynamic Saving: Convert any text input (or generated prompt) into a reusable wildcard file.</li><li>Three Save Modes: Choose between saving to your standard <code>wildcards</code> folder, the <code>output</code> directory, or a <code>temp</code> folder.</li><li>Smart Overwrite Protection: If "append" is turned off, the node automatically renames files (e.g., <code>colors_1.txt</code>) to prevent accidental data loss.</li><li>Live Console Debugging: Provides a clear visual log in your terminal showing how many lines were added and the exact file path used.</li></ul><hr /><hr /><h3 id="3.-settings-explained">3. Settings Explained</h3><ul><li>text: The string you want to save. Each new line in the text will be treated as a separate entry in the wildcard file.</li><li>filename: The name of your file (do not include <code>.txt</code>).</li><li>append: * <code>True</code>: Adds the new text to the end of the existing file.<ul><li><code>False</code>: Creates a new file. If the name exists, it adds a numbered suffix.</li></ul></li><li>save_mode:<ul><li><code>wildcards</code>: Saves to <code>ComfyUI/wildcards/</code> (Created automatically if missing).</li><li><code>output</code>: Saves to your standard ComfyUI output folder.</li><li><code>temp</code>: Saves to the temporary folder.</li></ul></li><li>debug: Set to <code>True</code> to see color-coded success and error messages in your terminal.</li></ul><hr /><h3 id="4.-reading-the-debug-logs-(console)">4. Reading the Debug Logs (Console)</h3>When debug is enabled, you will see a blue (magenta-ish) log entry in your terminal:<ul><li>Before: How many valid lines were in the file before saving.</li><li>After: The total count of lines now in the file.</li><li>Path: The exact disk location where the file was saved.</li></ul><hr /><h3 id="why-use-this">Why use this?</h3><ul><li>Prompt Harvesting: If you generate a great prompt using LLMs or randomizers, you can save it instantly to your permanent library.</li><li>Automation: Create "dataset" files for training or long-term projects by appending successful prompt combinations to a list while you work.</li></ul> Note: 'VibeCoded'

Files with SHA256: 8fa855be6ff93405556aba959e2a46ede51b83427fc1269a3fb9b5751f31fb40