Void Presence Release Schedule

Config Load & List DnD

Improvements

• Centralized drag‑and‑drop re‑attachment into a dedicated helper:
  • reattachDnDForProfiles rebinds DnD for all profile‑related lists after applying a config.
• Kept list rendering via createListManager, but wired it to the shared DnD helper so newly rendered rows automatically participate in sorting.

Fixed

• Fixed an issue where drag‑and‑drop stopped working after loading a saved config by re‑initializing DnD after applyStateToUIAndLists.
• Resolved state mismatch problems so that, after loading a profile, all profile‑related lists update both their data and drag behavior consistently.
• Fixed an off‑by‑one bug in list reordering where dragging the first item onto the second would incorrectly place it at index 2 instead of 1.
• Corrected the drop index calculation so that when dragging an item downwards, the insert index is adjusted after removal, ensuring items land exactly where the drop indicator shows.

Drag Handles & List DnD

Improvements

• Added drag handle dots (······) on the left side of all list rows:
  • Details & State cycles
  • Image cycles
  • Button pairs
  • Party size
  • Time cycles
  • Recent apps
• Visual drag‑handle dots are styled in a minimal “Vercel‑like” style:
  • Six small dots ······ rotated 90° so they appear vertical on the left.
  • draggable attribute now lives only on .drag-handle, not on the whole row.
• Standardized drag‑handle across all list‑rendering helpers:
  • createRow generic helper now includes .drag-handle.
  • renderRecentApps now includes .drag-handle for recent app entries.
• Drag‑and‑drop sorting now starts only when dragging on the dots, preventing accidental drag from inputs or buttons.

Fixed

• Fixed drag‑and‑drop not working when dragstart was triggered somewhere other than the handle.
• Ensured drag handle is visually aligned and consistent across all lists and themes.

Cloud Sync & Saved Configs Layout

Improvements

• Moved the Recent Apps card above Cloud Sync, so the list of recently used Discord applications now sits closer to profile and upload actions for quicker switching.
• Moved the Author ID field into the Cloud Sync card next to the upload button, so everything related to your profile is in one place.
• Cloud Sync now groups author, name, and upload actions in a single section, reducing extra navigation in the UI.
• Moved the config name + save row into the Saved configs card, so naming and saving presets now live directly above the saved configs list where they are used.

Smart Recent Apps UX & Link Validation & Quick Client Switching

Added

• Quick “use” button for recent apps that instantly applies the selected Client ID, restarts Discord Rich Presence, and returns you to the main view.

Improvements

• URL inputs are now auto-trimmed and rejected if they contain spaces, preventing broken Discord buttons and image links from being saved.
• Log message when connecting RPC now clearly includes the Client ID in a consistent format (Connecting RPC Client ID: <id>).

Fixed

• Non-existent or invalid app IDs now show a clear status (App not found or Fetch failed) and are visually dimmed.
• Recent app rows no longer lose their disabled/“not found” state after removing other items from the list.

Persist Mode Fixes

Bug Fixes

• Fixed persist timestamp offset reset on app restart after a power loss — persistOffsetSec is now preserved in the config and no longer gets overwritten by renderer state.

UI Fixes

Bug Fixes

• Fixed card header underline overflow — line stays within card boundaries.

Stability Client ID

Improvements

• Strict Client ID validation: Now requires exactly 19 digits (length > 18) before saving to client-config.json.

Bug Fixes

• Fixed clientId: null after restart — empty strings from inputs no longer overwrite valid IDs.
• Cleaner state sync between localStorage, UI inputs, and main process config.

Atomic Writes & Stability

Improvements

• Implemented atomic config writes for all Electron‑managed JSON files:
  • All config files (client-config.json, settings.json, image-cycles.json, party-config.json, timestamp-config.json, etc.) are now written via temporary file + rename when possible.
  • This improves reliability and reduces the chance of corrupted or half‑written configuration files on Windows and Electron.
  • Atomic write layer includes retry‑based fallback and proper tmp‑file cleanup.
• Internal plumbing and error‑handling around live-set-party, live-set-images, and related IPC handlers now safely recover from ENOENT / EPERM filesystem errors during config writes.
• Improved readability and consistency of RPC‑related tooltips and advanced options layout across all config panels.
• State field now consistently shows (optional) placeholder text:
  • Input rows use { placeholder: 'State (optional)', value: entry.state || '' }.
  • Empty state values are represented with a clear, optional‑labelled placeholder instead of leaving misleading empty labels.
• Updated timestamps and cycle‑management helpers to reduce visual flicker and state‑jitter when toggling now / range / persist and nowMode.

Bug Fixes

• Fixed rare EPERM: operation not permitted and ENOENT: no such file or directory errors when saving:
  • image-cycles.json
  • client-config.json
  • party-config.json
  • by switching to an atomic write strategy with retries and tmp‑file cleanup.
• Eliminated accidental disappearance of the `now

Portable Auto-Update & Stability

Improvements

• Portable build now supports one-click auto-update:
  • App downloads the latest NSIS installer from GitHub Releases.
  • Installer is applied directly to the current portable folder in silent mode.
  • Void Presence automatically restarts after the update completes.
• No more manual re-downloading and unpacking for portable users.

Dependencies

• Updated Electron to 41.5.0 for improved runtime stability, performance, and up‑to‑date Chromium/Node.js versions.

New Icon

Improvements

• Added beautiful new app icon (vP geometric design)

Automatic Profile Linking & Stability

Features

• Automatic profile linking via deep link
  • Added a dynamic "Use this author in Void Presence" button on the website.
  • Clicking automatically opens Void Presence with voidpresence://auth?authorId=....
  • On app startup:
    • authorId is saved into localStorage and the config-author-input field;
    • the "Config" view is opened automatically;
    • no manual authorId copy‑paste is required — the profile is pre‑connected.

Improvements

• Reordered some UI blocks for better flow and readability.
• Added automatic redirection to the Logs and Configs pages in predefined situations (e.g. after profile linking or certain setup actions), so the user lands on the most relevant screen without manual navigation.

Dependencies

• Updated Electron to 41.3.0 for improved runtime stability, performance, and up‑to‑date Chromium/Node.js versions.

Code Structure Refactoring & RPC Reliability & DnD Fixes

RPC Reliability Fixes

• Guaranteed First Activity Push Discord RPC now always pushes config cycles activity immediately on ready via pushActivity(null). Fixed complete index reset (cycleIndex=imageIndex=buttonIndex=partyIndex=0) — first cycle guaranteed on startup.

• Session State Consistency Proper initialization of currentTitle, lastSmTcStatus/Position, and lastJsonSignature for seamless pollJsonLoop() transitions.

Drag-and-Drop Improvements

• Completely Reworked DnD Behavior attachDnD<T> generic with precise drop zones (drop-target-top/drop-target-bottom), stable hover states via dragenter/dragleave, and TypeScript-safe dataset handling. Smoother dragging, no flickering, accurate drop positioning — fully reliable across all list types.

Improvements

• Unified List Management All user-editable lists (buttons, cycles, images, party, time blocks) now share a common createListManager<T> helper. This reduces duplicated DOM-rendering and localStorage-saving code, making the config UI modules much more DRY and maintainable.

• Reusable Row-Creation Helpers Each config row (createButtonPairRow, createCycleRow, createTimeRow, etc.) is now built on top of a central createRow helper. Row-related DOM creation, event listeners, onUpdate and onRemove hooks are now centralized, improving consistency across features and reducing boilerplate.

• Config Module Organization The config-related logic has been split into clearly separated modules:

  • list-renderers – common list-handling and createListManager;
  • rows – row-creation helpers;
  • clientId-controls – clientId, intervals, toasts, drag-and-drop setup;
  • mode-controls – timestamp and “now mode” logic;
  • time-controls – time-cycles handling. This makes it easier to locate, update, and test specific pieces of the UI.

Internal Changes

• Helper-Driven Architecture Many duplicated patterns (DOM-element creation, localStorage I/O, drag-and-drop wiring) have been moved into reusable helpers instead of being scattered inline across multiple functions. This improves type-safety, testability, and makes future UI changes less error-prone.

• Type-Safe Attachment Layer DnD-attaching and list-rendering now use a generic-style pattern, so the same logic can be applied to different list types without manual code duplication. TypeScript errors are easier to catch upfront, and the structure is more predictable for contributors.

• No UI Behavior Changes From the user’s perspective, nothing has changed:

  • button adding,
  • cycle editing,
  • image/party/time configuration,
  • reorder-via-drag-and-drop behavior — all remain the same. Only the internal code structure and organization have been updated, making the codebase cleaner and easier to navigate.

Timestamp Validation Fix

Improvements

• Reliable Rich Presence Timestamps Rich Presence timestamps are now sent as Unix time in seconds (>= 1) instead of raw JavaScript milliseconds. This fixes validation errors such as: child "activity" fails because [child "timestamps" fails because [child "start" fails because ["start" must be larger than or equal to 1]]] when updating activity via SET_ACTIVITY.

Internal Changes

• Consistent Time Format for Discord All internal time calculations still use JavaScript milliseconds (from Date.now()), but before sending data to Discord, they are converted to Unix seconds using a small helper function. This ensures that the activity.timestamps.start and activity.timestamps.end fields always match Discord’s expected format and range.

• Safe Timestamp Conversion Layer A dedicated conversion helper now:

  • Converts millisecond values to Unix seconds using Math.floor(ms / 1000).
  • Ignores invalid or too small values (anything < 1), so Discord never receives zero or negative timestamps.
  • Builds a safe activity.timestamps object right before the SET_ACTIVITY request is sent.

• No Behavior Changes for Existing Features All existing behaviors (such as “now”, “range”, “persist” timestamp modes and playback progress from the media session) remain the same from the user’s point of view. Only the way timestamps are formatted for Discord has changed, making the integration more stable and standards‑compliant.

Dependency Cleanup

• Removed dotenv Dependency The project no longer depends on the dotenv package for loading environment variables.

RPC Ready & First Activity Dispatch

Improvements

• Accurate ACTIVE State The RPC status is now marked as ACTIVE only after the first Rich Presence payload has been successfully sent to Discord, instead of immediately on socket readiness. This makes the status indicator reflect real in‑Discord activity rather than just a connected transport.

Internal Changes

• ready Handler Adjusted The localClient.on('ready') handler now:
  • Reads the current NowPlaying snapshot from SMTC.
  • If a track/title or playback status is present, calls pushActivity(np) once and only then sets sendStatus('ACTIVE').
  • Updates lastJsonSignature based on the initial snapshot so that the polling loop does not immediately re‑send the same payload.

Timestamp Safety

Improvements

• Smoother Live Timestamp Editing Updated the live-set-timestamp IPC handler so that switching timestamp modes (now, range, persist) no longer forces a Discord Rich Presence restart. Mode, range, and display settings now apply live without interrupting the active RPC session, making timestamp experimentation feel more responsive in the UI.

Internal Changes

• Centralized Timestamp Config Handling All timestamp-related logic (mode, rangeMin, rangeMax, persistOffsetSec, nowMode, timeCycles) now flows through the shared setTimestampConfig helper, ensuring consistent validation, rounding, and safety checks across both regular and live update paths.

Persist Timestamp Safety Clamp

Improvements

• Safer Persist Timestamp Updates Added a guard to the persistOffsetSec timestamp configuration so that large jumps are ignored. Incoming persistOffsetSec values are still rounded to the nearest 5 seconds, but if a new value is more than 10 seconds higher than the currently stored offset, the change is discarded and the existing value is preserved. This prevents accidental or noisy updates from causing sudden, unrealistic jumps in the persisted timestamp.

Upload Button Style Patch

Improvements

• Upload Button Style Refresh Tweaked the upload button styling (via uploadBtn.innerHTML) to better match the rest of the UI, improving visual consistency and making the upload action more noticeable without changing its behavior.

Auto‑Update Overlay Fix

Improvements

• Auto‑Update Overlay Fix Fixed a bug where the inline changelog update overlay could trigger installation without a valid download URL, restoring reliable one‑click auto‑updates from inside the app.

v2.5.2 – Advanced Mode Quality Pass

Improvements

• Advanced Mode Interval Hint: Added a contextual hint recommending a 10–15 second update interval when using the advanced (music & YouTube) RPC mode, to reduce rate limits and improve stability.

UX & Polish

• Safer Defaults on Import/Export: Imported configs that lack an explicit RPC mode now default to basic, while exports always include the current mode for clearer sharing and backup behavior.

v2.5.1 – Hotfix: Drag & Drop & Stability

Bug Fixes

• Stable Drag & Drop Reordering: Fixed an issue where reordering button pairs, party size and cycles via drag & drop would sometimes not apply or visually update after dropping.
• Input Safety & DnD: Adjusted drag detection logic around inputs, so text selection no longer disables reordering while still preventing accidental drags when editing fields.
• Consistent RPC Mode Defaults: Unified default RPC mode to basic across the app (UI state, local config and Electron settings) to avoid mismatched behavior on fresh installs.

v2.5.0 – The GUI Overhaul

New Features & UI Rewrite

• Complete Interface Redesign: A fully rewritten modern GUI with a focus on a "dark & matte" aesthetic. Added smooth CSS-based transitions (fade-in, translateY) for all views and modals.
• Smart Search & Filtering: Added real-time search in the "Saved Configs" section. Instantly filter profiles by Name or Author ID as you type.

Technical Changes

• Robust Config Validation: All local config files now go through a strict normalization layer. Invalid or legacy JSON is auto‑sanitized into a safe shape, reducing crashes from broken configs.

v2.4.1 – Stability & Type Safety Patch

Bug Fixes

• Fixed Critical Crash on Config Reload: Resolved a TypeError: Cannot read properties of undefined (reading 'state') that occurred when reducing the number of entries in Cycles or Image Cycles while the app was running.
• Added Bounds Checking: The RPC module now strictly validates cycleIndex against the current array length. If the configuration is saved with fewer entries, the index automatically resets to 0 instead of crashing the update loop.

Technical Changes

• Standardized cycleIndex management across both Basic and Advanced RPC modules.
• Added safety guards to prevent unhandled promise rejections during high-frequency config writes.

v2.4.0 – Live Editing & Instant RPC Connect

Features

• Added Live Editing: changes to client ID, buttons, cycles, images, party, timestamp modes and update interval are now applied immediately to the running Rich Presence session without restarting the app.
• Updated runtime config handling so both basic and advanced RPC modules read fresh settings while running and rebuild cycles/images/party/buttons on the fly when the config is saved.
• Updated image cycles so large/small images now automatically rotate through the full image array in sync with status cycles.

RPC

• The RPC client now connects instantly on startup as soon as a running Discord instance is detected, instead of relying on a delayed, interval-based connection loop used previously.
• Reconnection after errors or Discord restarts is more predictable: the session is restarted as soon as the process is found, without unnecessary extra delays.

UI / UX

• Added helper toggles under AUTO START: “Launch app with Windows” and AUTO HIDE: “Minimize to tray on start” to make background usage more convenient.
• Added an explicit hint: “After changing the client id or update (sec), click RESTART PRESENCE.” to clarify how to apply critical RPC changes.
• Moved the controls RESTART PRESENCE and STOP PRESENCE to the very top of the window so they are always visible and easy to access.

v2.3.5 – SMTC Optimization & Runtime Update

Performance

• Optimized SMTC polling to reduce redundant updates and CPU usage during long sessions by debouncing state changes and skipping identical payloads.
• Improved SMTC track state detection to only recompute Discord Rich Presence fields when media metadata (title, artist, position, playback state) actually changes.

Internal

• Refactored SMTC update flow to share a single normalized state object between the media listener and the RPC layer, reducing duplication and side effects.
• The build configuration has been refined so that the final package now includes only compiled entry points and required runtime assets, instead of the entire project tree (source files, tooling configs, and dev‑only dependencies are excluded from the shipped bundle).

Dependencies

• Updated Electron to 41.1.0 for improved runtime stability, performance, and up‑to‑date Chromium/Node.js versions.
• Application bundle size increased by a few percent due to the runtime upgrade, but overall performance and responsiveness have improved as a result.

v2.3.2 – SMTC & RPC Performance Improvements

Improvements

• Reduced CPU usage for SMTC worker The SMTC worker now caches the media session status and updates the now-playing' file.json only for actual track changes or playback status.
  This reduces the number of accesses to the system API and writes to disk, reducing the load in the background.

• Optimized now-playing.json polling in RPC
  The Discord RPC module reads now-playing.json uses a single secure method and reuses the received data instead of re-reading and parsing the file in several places.
  Unnecessary accesses to the file system are removed, which reduces peak CPU consumption.

• Smarter Rich Presence updates
  Discord activity updates are now performed only when the track signature (name, status, position) changes, and not on every tick of the timer.
  This reduces the number of SET_ACTIVITY requests and helps you avoid hitting Discord's update frequency limits.

• Track cover caching with size limit
  A limited cache of track covers has been added to avoid requesting iTunes, TheAudioDB, and MusicBrainz during each update cycle.
  The cache is automatically cleared when the limit is reached, keeping memory usage under control.

Technical Notes

• The SMTC worker uses a short‑term media session cache and a single NowPlaying publishing path, which minimizes duplicate work.
• The RPC module relies on a single status reading function (readNowPlayingSafe) and transmits the result directly to pushActivity, eliminating repeated parsing of JSON.
• Rich Presence's delay logic between updates takes into account the minimum interval and playback status, preventing excessive updates during pause and rewind.

v2.3.1 – Timestamp Persistence & Reset Fixes

Fixes

• Correct timestamp persistence
  Saving settings via SAVE and RESTART PRESENCE no longer resets persistOffsetSec to 0.
  The current offset value (for example, 110 seconds) is now saved until the user explicitly resets.

• Reset saved timestamp is working correctly
  The reset saved timestamp button now:

• resets only the saved timestamp (the persistOffsetSec field),

• does not touch mode, rangeMin, RangeMax, nowMode and timeCycles,

  • Instantly applies new values without breaking other timer settings.

• Secure saving of time configuration
  The updated logic of setTimestampConfig now:

• merges with the current config (readTimestampConfig),

• does not overwrite persistOffsetSec if it is not passed from renderer,

  • updates only those fields that came from the form (mode, range, now‑mode, time cycles).

Technical Notes

• 'setTimestampConfignow uses the currentpersistOffsetSec' if the field was not passed from the UI.
• Calling setTimestampConfig from renderer during SAVE and RESTART PRESENCE no longer resets the internal 'saved time'.
• The timestamp reset button uses a separate path (resetPersistTimestamp + overwrite only `persistOffsetSec').

v2.3.0 – Enhanced Logging & Smart RPC Modes

Features

• Superior log display system with improved visual hierarchy, color-coded severity levels, and real-time status updates for better debugging and user feedback.
• New RPC Mode toggle (Basic vs Music and Youtube) with seamless switching — Music and Youtube now intelligently detects and displays music activity (Spotify) and YouTube playback alongside custom presence data.
• Optimized SMTC Worker — conditionally loads only in Advanced mode, reducing memory footprint and improving startup performance in Basic mode.

Behavior Changes

• Smart SMTC management: Worker automatically starts/stops based on RPC mode, ensuring YouTube/Spotify integration works only when needed.
• Cleaner mode transitions: Switching RPC modes instantly restarts Discord presence with proper cleanup, preventing stale states or memory leaks.
• Enhanced logging pipeline: Main process → IPC → Renderer logs are now perfectly synchronized, with sendLog integration for critical events like SMTC worker lifecycle.

Most important

RPC Mode now shows real music and YouTube activity in Discord status!

v2.2.0 – Smarter Modes & Timestamps

Features

• Added explicit activity type selection, allowing you to switch between richer presets (e.g. “Playing”, “Streaming”, “Listening”) without manually editing the payload each time.
• Improved timestamp configuration UX: modes are now more visually distinct, and the active option is clearly highlighted in the Presence interface.

Behavior Changes

• Timestamp handling is now more predictable: changing the mode immediately recalculates the starting point and timer behavior so Discord more accurately reflects how long your session has been running.
• The internal payload generator now cleanly separates activity type and timestamp logic, reducing inconsistent states when rapidly switching between modes.

v2.1.0 – Smarter Time & Party Presence

Features

• Added configurable timestamp modes for Discord Rich Presence, letting you choose between live time (now), randomized ranges (range), or a persistent start point (persist) for your activity timer.
• Introduced party cycling support, allowing Rich Presence to display rotating party sizes (e.g. “2 of 4”, “3 of 5”) based on a configurable party profile.

Behavior Changes

• Activity timestamps are now generated according to the selected mode; switching modes updates how long Discord shows the session as running without requiring manual timestamp tweaks.
• When party profiles are configured, Rich Presence will automatically include party size information in the activity payload, or omit it entirely if no valid entries are present.

v2.0.5 – Config Confirm & Logs UI

Features

• Added a confirmation overlay when uploading a config to the cloud, showing the selected profile and requiring explicit user approval before upload.
• Improved the logs view layout, refining spacing, typography, and entry grouping for better readability during long sessions.

Behavior Changes

• Cloud uploads now only start after the confirmation dialog is accepted; closing or dismissing the dialog safely cancels the action without side effects.
• Log entries keep the same data, but their visual presentation has been adjusted to match the updated interface and be easier to scan.

v2.0.4 – Client ID History

Features

• Added a client ID history list that remembers recently used application IDs as named entries.
• Enabled inline renaming of saved apps while keeping their client IDs immutable.
• Implemented click-to-copy behavior on history items, copying the client ID to the clipboard and applying it to the active session.

Behavior Changes

• Save and Restart RPC now only adds a new history entry for a client ID if it does not already exist, avoiding overwriting names or timestamps of existing entries.

v2.0.3 – Uptime

Features

• Implemented Uptime display in the RPC payload panel

v2.0.2 – RPC Fix

Bug Fixes

• Fixed Discord RPC not starting when autoHideOnStart enabled — createMainWindow now always called on app launch
• Removed duplicate RPC clients — only one startDiscordRich call, preventing conflicts and double updates
• RPC initializes immediately regardless of window visibility, preventing empty Discord status on startup

Internal

• Always create main window in app.whenReady(), hide only if autoHideOnStart=true
• Fixed tray logic — shows existing window instead of creating duplicate RPC/window
• Tray now uses getMainWindow() + show() instead of createMainWindow() on click

v2.0.1 – Profile Cloud Upload Fix

Bug Fixes

• Fixed the Upload Current button in profile cards so it now uploads the full state of the selected profile instead of the current in-memory UI state.
• Prevented unintended mutations of saved profiles during normal session usage by building the upload payload strictly from the profile’s stored cfg.state.

Internal

• Updated config-page.ts to add a dedicated handler for per-profile cloud upload that mirrors the global Upload Current

v1.5.3 – Clean Drops & New UI

Bug Fixes

• Resolved global drag overlay bug where the drop highlight persisted when dragging files outside the window boundaries.
• Improved drag-and-drop reliability by adding explicit window boundary checks and blur event handling.

UI Polish

• Introduced a refreshed black-and-white interface with cleaner layouts, sharper contrasts, and more consistent component styling across the app.
• Updated navigation, status chips, and log views to better highlight success, warning, and error states while keeping the UI minimal and focused.

v1.5.2 – Presence & Config Polish

Improvements

• Added update checks when opening the app from the system tray, so users who start minimized still get notified about new versions.

UI & Config

• Updated the config details modal so long lines no longer wrap and are truncated with an ellipsis, keeping sections readable even with verbose values.

v1.5.1 – Update Flow Cleanup

Changes

Removed the built-in auto-update helper due to unstable behavior and unnecessary complexity in production. The app now falls back to a simple version check and a link to the latest GitHub release, letting users decide when to download updates manually.

Bug Fixes

• Eliminated app-update.yml errors and other side effects caused by the auto-update setup in Windows builds.
• Simplified startup logic so version checks and RPC logging behave consistently in both dev and packaged releases.

v1.5.0 – Auto Updates & Cloud Polish

Changes

Expanded the version system with optional auto‑update flow and refined cloud config UX, building on top of the 1.4.x version check and warnings.

New Features

• Optional auto‑update helper that can silently check GitHub Releases and prompt the user to download the latest installer
• In‑app log entry when an update download is initiated, with clear info / warn levels for update flow events
• New log messages for Discord RPC lifecycle (connect, disconnect, errors) with proper severity levels to improve debugging
• Added structured logging for cloud config uploads (success / failure) to make diagnosing Firebase/network issues easier

Improvements

• Centralized logging in the main process with typed LogLevel (info, warn, error, success) and consistent renderer styling
• Refined RPC module to use log levels for all reconnection and error cases, reducing “silent failures” in the background
• Further cleanup of Electron main process into main/, ipc/, logging/, cloud/, and updates/ modules for better maintainability
• Small UI tweaks in the Logs view for better readability of warnings vs errors, especially around version and RPC issues

Bug Fixes

• Fixed rare race conditions where RPC timers and restart intervals could overlap and cause redundant reconnect attempts
• Resolved cases where version checks or RPC errors could log before the window was ready, ensuring messages reliably appear in the Logs tab
• Improved error handling around GitHub and cloud requests so temporary network issues no longer affect core Discord RPC behavior

v1.4.2 – Version Check & Warnings

Changes

Added GitHub version check on startup with in‑app warning logs and status indicator when a newer Void Presence build is available.

New Features

• Automatic check for latest release on GitHub at app launch, using the current app version from app.getVersion()
• Warning log entry when a newer version is detected, highlighted as warn in the Logs view
• New OUTDATED_VERSION RPC status with orange status chip and dot, indicating that an update is available
• Per-log level support (info, warn, error, success) from the main process, with colored indicators in the renderer

Improvements

• Visual warning indicator on the Logs tab (tab dot highlight) that auto-clears after a short delay when new warn/error logs appear
• Consistent log styling for warn level (border, background, dot color) matching existing error/success semantics
• Minor refinements to status mapping and status‑dot gradients for clearer Discord connection states
• Refactored the renderer into a more modular structure with clear separation of concerns
• Introduced a dedicated renderer/ folder for UI logic, state handling, and view wiring
• Moved IPC and Electron bridge logic into bridge/ and ipc/ modules for safer main–renderer communication
• Split configuration handling into config/ (load/save, validation) and profiles/ (profiles list, active profile, cloud payload)

Bug Fixes

• Cleaned up unused RPC restart code paths and timers to avoid redundant reconnection attempts
• Fixed edge cases where logs could be emitted before the main window was ready, causing messages to be dropped
• Ensured safer handling of failed GitHub API requests so that update checks do not break the main RPC flow

v1.4.1 – TypeScript Renderer & Cloud Stability

Changes

Full TypeScript renderer and improved cloud config upload stability.

New Features

• Rewrote renderer.js to TypeScript with strict typing for Window, electronAPI, VoidPresenceCtx, cycles, and buttons
• Added strict data validation before saving and uploading configs (clientId, cycles, images, buttons)
• Improved drag & drop UX for profile import: visual overlay and protection against accidental text dragging

Improvements

• Fixed TypeScript issues (FileList → File, nullable fields for cycles and images)
• Centralized and cleaned up localStorage usage for configs, intervals, and auto-start/auto-hide flags
• More reliable logging of RPC and cloud upload errors directly in the log viewer, with clear success/error states

Bug Fixes

• Fixed cloud config upload: valid Firebase payload format and proper HTTP error handling
• Resolved cases where empty or partially filled buttons/cycles could break config saving
• Fixed drag & drop issues where the overlay could remain active or not trigger on first file drop

v1.4.0 – Cloud Config Upload & Firebase Integration

Changes

Cloud config upload – users can now upload and share their Discord presence configurations directly to the cloud.

New Features

• Added Cloud Upload button with name/author inputs that persist via localStorage
• Full Firebase Realtime Database integration for config storage and retrieval
• IPC handlers for secure main/renderer communication (upload-config)
• Frontend validation and loading states during upload process

Improvements

• Removed demo configs – app now relies entirely on real cloud data
• Enhanced error handling with detailed logging for upload failures
• Clean localStorage management (save inputs, clear after success)
• Updated Firebase module to use push() for unique config IDs

Bug Fixes

• Fixed upload not working – replaced direct fetch with proper IPC → Firebase flow
• Resolved event listener issues on upload button (removed invalid 'input' listener)
• Corrected main process handler to use Firebase SDK instead of raw REST API
• Fixed preload.js exposure for electronAPI.uploadConfig

Installation

Download the latest version "v1.4.0" and extract it to any location.
Your existing configurations from v1.3.2+ will continue working seamlessly. Local configs auto-sync with cloud on first launch.

v1.3.2 – Tray Fix & Branding Refresh

Changes

Tray behavior fix – the window now correctly moves to the tray only when closing, while the minimize button keeps it visible in the taskbar.

Improvements:

• Updated window behavior: clicking minimize no longer hides the app to the tray and now works as a regular taskbar minimization
• Refreshed the app logo to the latest version across all platforms and icons

Bug Fixes:

• Fixed a bug where minimizing the window would hide it to the tray instead of minimizing it to the taskbar
• Performed minor internal cleanup around window and tray event handling

Installation

Download the latest version "v1.3.2" and extract it to any location. Your existing configurations and profiles will not work if you upgrade from v1.3.1 or lower.

v1.3.1 – Import & Profiles Polish

Changes

Smarter profiles workflow – importing and managing presets is now simpler and more transparent directly from the config view.

Improvements:

• Updated the + config button so it now opens an import dialog for loading JSON profiles instead of immediately creating an empty config
• Added a full‑window drag & drop mode: you can drop a .json file anywhere on the app, with dashed borders around the edges when the drop zone is active
• Made import feedback clearer with a dedicated modal that explains the expected format and highlights imported cycles, images, and button pairs
• Profile cards now include a dedicated Export button for quickly saving any stored preset as JSON
• Minor UI polish to modals and the profiles list for cleaner spacing and more readable labels

New Features:

• Profile import via both file picker dialog and global window drag & drop
• Per‑profile export directly from its card, without needing to run a global export of the current state
• Automatic application of imported state in the editor (cycles, images, buttons) right after a successful import

Bug Fixes:

• Fixed rare desyncs between saved profiles and the active editor state after importing configs
• Fixed drag & drop issues where text selection inside inputs could unexpectedly trigger row dragging
• Resolved minor visual glitches when rapidly opening/closing modals and switching between tabs

v1.3.0 – Session & Controls Update

Changes

Richer session controls – managing Void Presence is now more convenient and transparent directly from the main view.

Improvements:

• Added a dedicated Stop Presence button to gracefully disable the current session without quitting the app
• Refined status indicator with clear states like DISABLED, RESTARTING, DISCONNECTED, etc., reflected in both the status chip and logs
• Improved copy for edge cases such as missing Client ID or cycles, with clearer hints on what needs to be configured
• Logs continue to update even after Presence is stopped, making it easier to trace errors and state transitions
• Better profile preview content: config cards now use the first cycle’s details and state to show what each profile will broadcast before you load it

New Features:

• One‑click full Rich Presence shutdown without restarting Void Presence
• Auto Hide mode to automatically hide the window to tray after starting the session
• Clearer live view of the current payload (object, buttons, state) when switching profiles or stopping the session
• Profile details view now exposes all saved cycles (details + state), images, and button pairs, so you can inspect configs without activating them

Bug Fixes:

• Fixed rare issues with status display after manually restarting Presence
• Fixed frequent problems of screen freezing or Not responding
• Fixed UI behavior when clearing the payload so the state correctly resets back to Idle
• Fixed cases where profile details (cycles list) could desync from the active state when rapidly switching configs
• Minor layout and live‑update fixes when loading profiles and applying new configs

Installation

Download the latest v1.3.0 release and extract it to any location. Your existing configurations and profiles will keep working as before, with the new session controls and profile details available right away after updating.