Void Presence Application Release

Localization & Interval Control

New

• Multi-language support — Void Presence now natively supports English, Russian, and Turkish. All UI strings and toast notifications adapt dynamically based on the selected user locale via i18next.
• Enforced interval initialization — added absolute structural validation for the core activity update cycle. The system now guarantees a safe fallback by actively forcing a 30-second default if settings are missing or invalid.
• Cross-platform Discord detection — the RPC core and custom status worker now correctly detect native Discord clients on Windows, macOS, and Linux, eliminating the infinite "SEARCHING DISCORD PROCESS" state for non-Windows setups.

Improved

• Strict storage correction — rebuilt setupIntervalControl to eliminate silent failures. The logic now directly overwrites corrupted or non-numeric localStorage entries with valid parameters.
• Synchronized backend state — the runtime interval now triggers an immediate window.electronAPI.setActivityInterval broadcast during initialization, completely removing timing gaps between UI states and the background process.
• Custom status stability — the status worker now shares the same resilient Discord presence detection and interval handling, making token-based custom statuses more reliable across all platforms.

Fixed

• Window restoration on macOS & Linux — fixed a critical Electron lifecycle issue where the application window could not be reopened after being closed or hidden. The application now correctly restores and focuses the UI when clicking the Dock icon on macOS or launching a second instance on Linux.
• Native module resolution (.asar bypass) — resolved a fatal startup error (ERR_DLOPEN_FAILED / Could not load the "sharp" module) on Apple Silicon Mac devices by correcting how native C++ binary dependencies (libvips) are handled and read by the OS.

Cross-Platform Support

New

• macOS support — Void Presence now builds and runs natively on macOS. A .dmg installer and a portable .zip are published with every release.
• Linux support — Void Presence now builds and runs on Linux. A .deb, .rpm, and a portable .zip are published with every release.

Improved

• Platform-aware hardware monitor — the hardware worker now detects CPU name, CPU temperature, and GPU stats on macOS (sysctl, system_profiler) and Linux (/proc/cpuinfo, /sys/class/thermal, sensors, /sys/class/drm) in addition to Windows.
• Platform-aware updater — updates.ts picks the correct installer extension (.exe / .dmg / .deb) and launch method per platform. The self-update flow opens the DMG on macOS and runs pkexec dpkg -i on Linux.
• SMTC plugin guarded — the Windows Media Session (SMTC) plugin and its worker now exit gracefully on macOS and Linux instead of crashing on the missing native module.
• GitHub Actions matrix build — the release workflow now builds all three platform bundles in parallel and publishes them in a single GitHub Release.

Security Hardening & View Routing Improvements

Improved

• Localized plugin install toasts — plugin installation results now use localized toast messages (pluginInstallFromUrlSuccess / pluginInstallFromUrlFailed), with translations available in English, Russian, and Turkish for consistent feedback across languages.
• Folder-only hot-load for plugins — updated the plugins:install-from-url handler so hot reloading is applied only to folder-based plugins (GitHub tree/zip installs), while single-file .js plugins are downloaded and stored without immediate hot-load, reducing unnecessary runtime surface.

Security

• Reduced renderer attack surface for plugin installs — the onInstallPluginFromUrl handler now accepts a single structured payload and routes it into a typed IPC call, preventing accidental extension of the deep link surface with unvalidated flags.

Refactored

• Unified view activation routing — replaced ad-hoc DOM rewrites with unified view switching through the setActiveView shell controller, making all navigation state changes flow through a single, predictable code path.

Bug Fixes & Plugin System Improvements

Fixed

• Double SET_ACTIVITY push — all plugin update callbacks now go through a single 50ms global debounce in plugin-manager, collapsing simultaneous updates from default + hardware plugins into one push.
• Payload signature check — rpc.ts now skips redundant pushes when the active payload has not changed between ticks.
• Button/image index overflow — indices are clamped to array bounds after every config read; deleting an element no longer causes skips or out-of-range access.
• Double index increment — getNextImageCycle and getNextButtons in hardware-plugin no longer advance indices on read; indices advance only in the rotate timer tick via dedicated dvanceImageCycle / dvanceButtons helpers.

Added

• onConfigChanged(key) hook — plugins can implement this optional method to react when buttons, imageCycles, cycles or party config changes. Default and hardware plugins reset their indices and re-render payload immediately on change.
• notifyConfigChanged(key) — plugin-manager broadcasts config changes to all active plugins when set-buttons, set-image-cycles or set-cycles IPC handlers fire.
• exclusive plugin flag — a plugin with exclusive: true takes full control when it has a payload; all other plugins are bypassed in getActivePayload regardless of priority.
• dirtyWhilePushing flag in rpc.ts — if a new update arrives while a push is in flight, a single follow-up push is queued after the current one completes instead of being silently dropped.

Media Settings Fixes

Fixed

• IPC video-filter toggle — fixed a broken renderer-to-main IPC call for toggling the video filter (settings:set-video-filter). The renderer now passes the boolean state correctly, and the main-process handler applies the change reliably, so the filter switches as expected.

Security Hardening

Improved

• Serverless SSE stability — locked down persistent update listeners (.on('value')) to look up strictly targeted author resources instead of listening to the global database root, completely forgetting cascade server crashes under traffic spikes.

Security

• Removed executeJavaScript Deep Link vulnerability — eliminated a critical Remote Code Execution (RCE) and XSS vulnerability by removing risky executeJavaScript string evaluations of untrusted external protocol variables, routing incoming payload structures natively over isolated IPC channels (webContents.send).
• Enforced server-side data authority — stripped out client-controlled author profile strings from the config creation payload, ensuring user identity fields are built securely on the server from verified session states rather than trusting raw JSON body inputs.
• Secured analytic mutations against spoofing — re-engineered telemetry and download increment handlers to securely check document existence before execution, preventing malicious fake ID injections from spawning rogue orphan data structures inside database trees.
• Hardened download metric protections — restricted clients from spoofing initial document engagement metrics by forcing all new configuration structures to securely initialize at zero downloads explicitly on the backend layer.

Structural Architecture Shift & Client Optimization

Added

• Relational database restructuring — migrated the entire database architecture away from redundant data duplication. Presence and status configurations now store only a strict authorId foreign key instead of baking mutable author names and avatars directly into configurations.
• On-the-fly metadata joining — implemented an efficient server-side batch collection pattern (uniqueAuthorIds) in global queries and Server-Sent Events (SSE) streams, fetching and combining real-time profile data dynamically instead of downloading entire raw collection snapshots.

Improved

• Zero-overhead client synchronization — eliminated the complex, recursive multi-path background updates across config trees upon user profile synchronization. Modifying user avatars or Discord tags now updates only a single atomic database leaf in the users branch.
• Linear complexity queries (O(1)) — removed heavy recursive user-to-configuration scanners (buildConfigToOwnerMap/findUserByConfig) in individual fetch, delete, and streaming endpoints, replacing whole-table memory processing with direct key-based lookups.
• Serverless SSE stability — locked down persistent update listeners (.on('value')) to look up strictly targeted author resources instead of listening to the global database root, completely preventing cascade server crashes under traffic spikes.

Fixed

• Ghost config creation — fixed an issue where updating user info while handling deleted configurations could accidentally recreate partial ghost config documents in the configurations branch due to Firebase .update() properties.

Backend Image Color Extraction & Stability

Dependencies

• Removed electron-squirrel-startup — completely dropped the redundant windows startup package from dependencies, as the application setup and distribution are now fully managed by the custom Go-based installer.
• Removed Squirrel installer maker — uninstalled @electron-forge/maker-squirrel, removing legacy installation pipeline configs and preventing unneeded NuGet tools overhead during project setup.
• Cleaned up devDependencies — removed unused native rebuild utilities (@electron/rebuild), hot-reloaders (electron-reloader), cross-platform environment helpers (cross-env), and unnecessary Linux distribution makers (maker-deb, maker-rpm) to minimize the project setup size and drastically speed up npm install execution times.
• Streamlined linting ecosystem — optimized configuration by dropping @typescript-eslint/eslint-plugin, @typescript-eslint/parser, and eslint-plugin-import, leaving only the core eslint setup for simplified code quality maintenance.

Syntax Fix

Fixed

• Protocol script closing brace — removed an extra } at the end of the executeJavaScript template string, which was breaking the injected IIFE and causing an Unexpected token '}' during URL import.

Author Field & Fallback Fix

Added

• Author field persistence — new configs now store the author nickname in Realtime Database alongside authorTag, so streams and listings can always show the creator name.
• Client‑side author name injection — status and presence uploads now read the author name from local state/localStorage instead of sending an empty string, ensuring the payload carries a valid authorName.
• Author avatar storage — configs now save an authorAvatar URL resolved from the author profile, so the site and stream UI can display the creator’s avatar without extra lookups.

Fixed

• Server write logic — the add‑config route no longer drops the author field when writing configs; it keeps all payload fields except kind, including the author nickname.
• API fallback lookup — if the client upload payload arrives without a usable authorName, the uploader calls /v1/authors/{authorId}/configs to fetch user.name and user.avatar, and uses them as author and authorAvatar for the new config.

New REST API Backend Endpoint

Rationale

The main reason for introducing the internal REST API endpoint is to move all sensitive update and upload logic off the client and into the backend. By doing this, the Electron app no longer needs to know about internal author identifiers or touch the database layer directly. Instead, it only talks to a stable HTTP surface, and the server is responsible for resolving author IDs, enforcing permissions, and shaping responses.

From a security perspective, this effectively closes off direct database exposure and reduces the blast radius of any client-side issue. The client sees opaque IDs and sanitized payloads, while the backend can evolve its schema, validation and authorization rules without leaking internals to the outside world. This also makes it easier to apply API security best practices such as “do not expose more data than necessary”, strict rate limiting and centralized error handling in one place.

This also opens the door to working with sensitive integrations entirely on the API side, including Discord tokens and other secret-bound flows. With that logic moved out of the Electron client, it becomes possible to reuse the same backend for future web or bot versions of Presence without exposing secrets in the desktop app.

The new version was already ready to ship, but 3.0.1 kept it blocked because of the weekly contract requirement. This delayed the release even though the update itself was prepared and fully functional.

This issue has worried me for a long time, because with only the database address it would be possible to expose or extract a lot of sensitive information. By sensitive data here, I also mean abuse risks such as artificially inflating activity, stats, or presence counts through author IDs and related internal fields. Again, we are not storing tokens or client IDs, but fake engagement, spammed presences, and manipulated statistics are still a real problem and something I want to prevent.

Added

• Internal update metadata endpoint — introduced a new backend endpoint at https://api.voidpresence.site/v1/github/application that proxies the latest GitHub release for the main app, returning the tag, installer asset name, download URL, and release notes body as JSON.
• GitHub access moved to server — all calls to the GitHub Releases API for update checks are now performed on the server, keeping tokens and rate limits on the backend instead of the Electron client.
• Changelog delivery via API — the Electron app now receives the Markdown changelog directly from the internal endpoint and displays it in the update overlay without talking to GitHub.
• Public API reference page — added a structured API endpoints page on the website that documents authors, configs, analytics, auth and GitHub helper routes in a single, grouped view, with sample JSON payloads and fetch examples.
• Cloud upload flow moved to the API — presence and status uploads now go through the backend API path instead of relying on the legacy direct storage flow, with sanitized payloads and server-side author resolution.
• Upload rate limiting added — repeated cloud upload requests are now throttled per upload type to prevent duplicate submissions and reduce accidental spam.
• Support and logs actions buttons — added four new buttons in the logs/support section for opening the support site, opening Discord, clearing the console, and downloading logs as a .txt file.

Changed

• Update source switched to internal API — the app’s update check logic now fetches release metadata from api.voidpresence.site instead of calling GitHub directly from the client.
• Simplified client update logic — the Electron updater now relies on a stable JSON contract from the website API and no longer parses GitHub release structures or selects assets itself.
• Improved backend control — update behavior can now be adjusted server-side by shaping the API response, filtering assets, or handling GitHub errors without shipping a new desktop client.
• Unified API grouping — HTTP endpoints are now organized by domain in the site docs, matching the backend structure and making the route layout easier to navigate.

Bug Fixes

• Status upload overlay dismissal fixed — the status upload confirmation overlay now closes correctly when pressing Escape and no longer leaves stale UI state or event listeners behind.

Update Overlay Close Text Fix

IMPORTANT: THIS RELEASE INTRODUCES A NEW VOID PRESENCE INSTALLER. LEGACY UPDATES WILL CONTINUE TO WORK FOR 1 WEEK FROM THE RELEASE DATE (28/06/2026). AFTER THAT, ONLY THE NEW INSTALLER‑BASED UPDATE FLOW WILL BE SUPPORTED. IF AUTO‑UPDATE DOES NOT WORK, YOU SEE ERRORS, OR VOID PRESENCE DOES NOT START AFTER UPDATE, YOU MUST OPEN THE RELEASE PAGE AND UPDATE MANUALLY USING THE INSTALLER FROM THIS RELEASE.

Fixed

• Localized close button text — the update overlay close button now uses the translated updateOverlay.close value instead of a hardcoded label, so the text matches the active language.
• Prevented text override — removed the behavior that overwrote the button text with the wrong value during overlay setup.
• Preserved close action — the button still hides the update overlay when clicked, with no changes to the existing behavior.

New Installer & Update Flow

IMPORTANT: THIS RELEASE INTRODUCES A NEW VOID PRESENCE INSTALLER. LEGACY UPDATES WILL CONTINUE TO WORK FOR 1 WEEK FROM THE RELEASE DATE (28/06/2026). AFTER THAT, ONLY THE NEW INSTALLER‑BASED UPDATE FLOW WILL BE SUPPORTED. IF AUTO‑UPDATE DOES NOT WORK, YOU SEE ERRORS, OR VOID PRESENCE DOES NOT START AFTER UPDATE, YOU MUST OPEN THE RELEASE PAGE AND UPDATE MANUALLY USING THE INSTALLER FROM THIS RELEASE.

New Installer

• Installer stored in app folder — the update flow now downloads Void.Presence.Setup.<version>.exe directly into the app directory instead of a temporary location, so the installer always runs next to the current executable.
• Single installer per release — the void-updates → void-presence pipeline ensures that each release exposes one up‑to‑date installer asset that the client can safely use for upgrades.

Manual Update Notice

• Manual update required on update failure — if auto‑update does not complete, the installer reports corruption, or Void Presence fails to start after updating, you need to perform a manual update using this release’s installer.
• Direct installer download from Releases — open the Releases page, download the latest Void.Presence.Setup.<version>.exe from Assets, and run it manually to migrate your installation to the new installer flow.

Compatibility with Older Versions

• Older clients may not support the new flow — previous versions of Void Presence use the legacy updater and may not correctly handle the new installer behavior.
• One‑time manual upgrade path — if auto‑update fails on an older version, perform a single manual update with this release’s installer; future updates will then use the new installer‑based flow correctly.

Config & Status Import Improvements, Presence Controls Refactor

New Features

• Import both configs and statuses — added a unified import flow that handles JSON files as both Rich Presence configs and text-based status presets, so users no longer have to split imports across different screens.
• Unified profile import flow — imported configs and statuses now land in a single profile panel where they can be viewed, edited, and deleted regardless of type.
• Consistent JSON format across types — the JSON structure for configs and statuses has been aligned, simplifying export/import between the desktop app and the web catalog.

Refactoring

• Shared presence control helper — restart and stop logic for Discord Rich Presence has been refactored into a single setupPresenceControls helper so one place manages both Restart and Stop actions.
• Restart/stop actions wired to Electron API — button handlers use a unified Electron API layer; restartDiscordRich and stopDiscordRich are called from setupPresenceControls() and update RPC state (RPC_RESTARTING, RPC_DISABLED) as well as the current presence info.

Improvements

• Extended Toast helpers for presence actions — setupToasts() now exposes additional helpers for presence-related events, including restart and stop, so users always get immediate visual feedback after clicking Restart or Stop.
• Context-aware RPC state messages — toast messages are tailored to the current RPC state (restarting, disabled), making it clear what exactly happened to Discord Rich Presence after each action.

Config Profile Export Scope Fix & Stability

Bug Fixes

• Export current config instead of all profiles — the global config export button now serializes only the currently active config data, rather than the entire vpConfigs array from local storage.
• Prevent multi-profile exports for single-config actions — exporting a config no longer produces a JSON file containing every saved profile; a file now represents exactly one config for import.
• Align global export with per-card behavior — the page-level export now mirrors the intended “export current config” semantics, while per-profile card exports continue to work on their specific saved profile state.

Stability

• Isolated config export payloads — each export file now contains data for a single working config, reducing the risk of overwriting multiple profiles when importing.
• Improved import predictability — the new export format is tailored for single-profile import, so importing an exported config no longer replaces or conflicts with unrelated profiles.
• Consistent export scope with user intent — global config export behaviour now matches what users expect when exporting “this” config, instead of silently including the whole stored array.

Dependencies

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

Config Profiles: Immutable Load Fix

Bug Fixes

• Fixed config profiles mutating after load — applying a saved config now uses a cloned state (deepCloneState) instead of a direct reference from vpConfigs, so changes in the UI no longer corrupt the original profile.
• Fixed cycles and fields drifting from saved state — after applying a config, cycles, timestamps and related fields are no longer written back into the stored profile, so the configs list always reflects exactly what was originally saved.
• Fixed inconsistent base state restore — the base state when loading a config is now built via buildBaseStateFromConfig, ensuring correct clientId, intervals, time modes and activity type even for partial configs.

Stability

• Aligned config behavior with status profiles — config logic is now aligned with status profiles: data is always cloned before being mapped into the working FullState.
• Safer state application pipeline — rendering and applying configs now always start from a clean clone of the stored state, reducing side effects from drag‑and‑drop and live updates in the main context.

Translation Updates & Text Fixes

Improvements

• Translation updates — corrected several text strings.

Cloud Status Profiles, Author Linking & Protocol Auth

New

• Cloud upload for status profiles — you can now upload your custom status profiles to the cloud separately from main RPC configs.
• Dedicated status-configs cloud branch — status presets are stored in their own collection, keeping them isolated from activity configs.
• Deep link from website to app — added voidpresence://auth?... protocol to instantly link your web profile with the desktop app.
• Author metadata in app UI — the config screen now shows your linked profile instead of a generic “None” label.

Improvements

• Author ID sync from web profile — clicking “Use this author ID in app” on the website opens the app and fills in the author ID automatically.
• Name & provider displayed in client — the app now reads name and provider from the protocol URL and shows them next to your author ID.
• Cloud upload UX for statuses — status profiles use the same confirmation modal pattern as configs, with a dedicated “Upload status profile” dialog.
• Persistent author metadata — author ID, name, and provider are stored in local settings and restored on app launch and config screen open.

Bug Fixes

• Fixed status upload modal not appearing — corrected markup, imports, and CSS selectors so the status upload confirmation modal opens reliably.
• Fixed cloud upload endpoint for statuses — status uploads now use a separate /status-configs path and respect Firebase rules for this branch.
• Fixed Cyrillic path typo — replaced accidental Cyrillic characters in the status configs URL to avoid invalid Firebase paths and 401 errors.
• Fixed type warnings in preload — added proper TypeScript types for uploadConfig and uploadStatusConfig parameters to remove implicit any diagnostics.

Stability

• Safer payload filtering before upload — only allowed keys (buttonPairs, cycles, imageCycles, party for configs; statusCycles for statuses) are sent to the cloud.
• Single‑instance protocol handling — improved handling of voidpresence:// URLs when the app is already running, including focus/restore logic and pending URL queue.

Placeholder Translation Fix & Immediate Language Update & Stability

Improvements

• Added translation support for all input placeholders — all input fields now use translation keys instead of hardcoded English text, covering Config, Status, and Activity pages.
• Added new translation keys — introduced 12+ new keys including config.searchConfigsPlaceholder, status.discordTokenPlaceholder, activity.clientIdPlaceholder, recent.appNotFound, and recent.fetchFailed.
• Placeholders update immediately on language change — no app restart required; placeholders refresh instantly when you switch language in settings or via timestamp mode buttons.

Bug Fixes

• Fixed placeholders not updating after language change — previously placeholders required a full app restart to reflect the new language; now they update via updatePlaceholders() called in language change handlers.
• Fixed button translation keys showing as raw text — details.add and buttons.add now display their translated text normally instead of showing the key itself.

Stability

• Centralized placeholder management — all placeholder logic is now in updatePlaceholders(), making it easier to maintain and extend.
• Language handlers now refresh placeholders — timestamp-mode-btn and settings-language-selector both call updatePlaceholders() after setting language.

Dependencies

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

Cloud Color Fix & Average Color Reveal Update

Improvements

• Added image-based average color extraction — configs now compute averageColor from the first imageCycles[0].largeImage using sharp, so each card gets a color derived from its preview image.
• Improved card color reveal — cards now start with the neutral base color and then reveal the extracted averageColor smoothly after a short delay, which makes the UI feel softer and more polished.

Stability

• Hardened the image fetch path — the code checks fetch success and image MIME type before processing, which reduces failures on bad remote URLs.
• Preserved upload reliability — the upload still posts the full config payload to Firebase, while also storing averageColor alongside the other fields.

Dependencies

• Uses sharp for color extraction — the image is resized and sampled efficiently before calculating the average hex color.

Cloud Config Fix & CPU Temperature Update & Layout Markup & Stability

Improvements

• Removed statusCycles from cloud upload — the statusCycles field is now deleted before uploading config to cloud to prevent unnecessary data storage in cloud:uploadConfig IPC handler.
• Fixed page layout markup — adjusted <div data-i18n="config.uploadCurrent">Upload Current</div> to match the overall page styling.
• Added second CPU temperature fallback — added alternative PowerShell WMI method (Get-WmiObject MSAcpi_ThermalZoneTemperature) in getCpuTemperature() to improve CPU temp reading reliability on Windows when the first CimInstance method fails.

Worker Session Hold Fix & Settings Page Update

Improvements

• Removed repeated payload fields — the current payload no longer repeats Buttons and DETAILS, keeping rich presence output cleaner.
• Moved startup options to Settings — Auto Start was moved to the Settings page for easier access.
• Relocated window behavior controls — Auto Hide was moved to the Settings page alongside the other startup options.
• Improved CPU sampling stability — the worker CPU logic was adjusted to produce more stable readings and more accurate timing.

Updated hardware activity formatting

Improvements

• Updated hardware activity formatting — details now shows only the load bar, while state includes the label, temperature, and load percentage for a cleaner RPC layout.
• Kept hardware rotation intact — entries still cycle normally through available hardware stats.

Language

Improvements

• Expanded multi-language interface support - improved Russian (ru), English (en), and Turkish (tr) coverage across the UI and logs

Update RPC

Improvements

• Improved SMTC playback tracking — media progress now stays accurate even when the worker reports a static position.
• Media now takes priority — when music or video is playing, Discord RPC shows media activity before hardware stats.
• Safer cover lookup — resolveCoverUrlFromITunes now handles failures more cleanly and avoids unnecessary extra work.
• Cleaner RPC lifecycle — stale clearActivity() behavior was removed from places where it could wipe active presence too aggressively.
• More stable refresh flow — timestamp and presence updates now follow the latest playback state more reliably.

Update: RPC & SMTC Worker

Improvements

• Removed SMTC session cache — eliminated caching in the Windows SMTC worker to get fresh media position on every poll.
• Fixed local progress calculation — position now increases over time even when SMTC returns static values, ensuring accurate playback progress in Discord RPC.
• Media now overrides hardware — when music or video is playing, it takes priority and shows in Discord RPC instead of hardware stats.

Tray Click Update

Improvements

• Updated tray click behavior — clicking the tray now shows or creates the main window and immediately checks for updates in the background.
• Preserved window recovery — if the main window does not exist, it is created first and then brought to the foreground.

Worker Session Hold Fix

Improvements

• Added last valid session retention — the worker now keeps the previous valid SMTC session when the current one is temporarily unavailable.
• Reduced status dropouts — short media-session gaps no longer clear the now playing state immediately.
• Improved playback stability — cached session data is reused briefly to prevent flickering or missing activity during long playback.

Status Text Mapping Fix

Improvements

• Fixed status text mapping - status labels are now resolved at display time, preventing undefined values on first render
• Improved dynamic translation handling - text mapping now updates correctly when language changes

Language & Display Fix

Improvements

• Fixed language selection - app now correctly detects and applies the selected language (ru/en/tr) on first startup and subsequent launches
• Expanded multi-language interface support - improved Russian (ru), English (en), and Turkish (tr) coverage across the UI and logs
• Fixed placeholder text - all input fields now show correct translations for their placeholders

First Launch Language Fix

Version 2.13.13 is UNSTABLE To update, download and reinstall Void Presence again from the latest release manually.

Improvements

• Fixed first launch language display - now app correctly shows the selected language (ru/en/tr) on first startup

Bug Fixes

• Fixed language not applying correctly on first app launch

Multi-Language interface support

Version 2.13.13 is UNSTABLE To update, download and reinstall Void Presence again from the latest release manually.

Improvements

• Expanded existing multi-language support - improved the current Russian (ru), English (en), and Turkish (tr) interface coverage across the UI and logs

Config Labels Overflow & RU Translation Fix

Version 2.13.13 is UNSTABLE To update, download and reinstall Void Presence again from the latest release.

Improvements

• Fixed text overflow in config labels - adjusted .client-row span width to 85px with word-break to prevent long text cutoff
• Fixed Russian translations - corrected wording for Russian locale

Custom Status: Worker Optimization & Rate Limit Fix & Multi-language support (Test)

Version 2.13.13 is UNSTABLE To update, download and reinstall Void Presence again from the latest release.

Improvements

• Hard stop worker on disable - when feature is turned off, worker now completely stops instead of running empty cycles with timers
• Retry buffer +500ms - added 500ms buffer to retry_after to prevent repeated 429 errors due to network ping/timezone differences
• Session-based race condition protection - existing sessionId check prevents concurrent worker executions
• Isolated worker architecture - custom status runs independently from main RPC loop, protecting presence updates from status errors
• Multi-language support (i18n) - UI and logs now support Russian (ru), English (en), and Turkish (tr) languages. Language is stored in language.json and can be changed in settings. Translations are loaded via IPC from main process to renderer.

Error Logging Fix

Improvements

• Fixed log spam for Custom Status errors - errors now update in place instead of creating new log entries
• Added updateExistingLogItem helper function - extracts common log update logic for reuse
• Improved log readability - same behavior as download progress updates

Bug Fixed

Issue: Log spam with repeated Custom status apply error: fetch failed messages every few seconds Fix: Errors now consolidate into a single line that updates with the latest error message using the new helper function

RPC Auto-Start Fix for Hardware/SMTC Workers

Improvements

• Fixed RPC auto-start issue - RPC no longer immediately re-enables after being manually toggled on
• Added rpcEnabled check in SMTC worker - worker now verifies RPC is enabled before auto-starting
• Added rpcEnabled check in Hardware worker - worker now verifies RPC is enabled before auto-starting
• Added rpcStarted = false reset - flag reset when toggling RPC on to prevent duplicate starts

Bug Fixed

Issue: RPC would immediately turn back on after being toggled off due to hardware/SMTC workers auto-starting it Fix: Workers now respect rpcEnabled setting and won't start RPC if it's disabled

Custom Status Controls Relocation & Stability

Improvements

• Moved Custom Status Restart and Stop buttons - relocated above the Status Cycles block for better UX

Dependencies

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

Custom Status Token Validation Fix & Added Browser Mode Toggle

New Feature

• Added statusEnabledBrowser toggle - new setting to enable Custom Status in browser mode
• When enabled, completely skips Discord.exe process check - Custom Status runs without verifying Discord is running
• Added setStatusEnabledBrowser() IPC method - new Electron API method for browser mode toggle
• Added statusEnabledBrowser to settings - stored in localStorage and persisted across restarts

Improvements

• Removed Discord token validation check - token is no longer validated on each cycle, preventing premature worker stoppage
• Removed isDiscordTokenValid() function - eliminated unnecessary API call that caused "token invalid" errors after ~1 minute
• Custom status now runs continuously - loop doesn't stop due to false "logged out" detections

Custom Status Rate Limit Fix

Improvements

• Added comprehensive JSDoc documentation to all functions and file header
• Added Discord User-Agent header to API requests for better spoofing:
• Improved rate limit handling with proper retry_after respect
• Maintains signature-based change detection (skips if status unchanged)
• Token validation on each cycle (stops if logged out)
• Smart Discord process detection (checks Discord.exe before starting)

Rate Limits:

• Minimum interval: 5 seconds (5000ms)
• Recommended interval: 60-90 seconds for smooth animation
• On 429: waits retry_after seconds before next attempt
• Global rate limit bucket: ~60 seconds for /users/@me/settings

Rate Limit Retry-After Fix

Bug fixes

• Fixed custom status rate limit spam: worker now respects retry_after from Discord's 429 response and waits the exact amount of seconds before retrying.
• Previous behavior: worker continued with normal interval after 429, causing repeated rate limits.
• New behavior: worker pauses for retry_after seconds (e.g. 9.6s) before next custom status attempt.

Cloud Configs: Discord Token Excluded from Cloud Uploads

Security fix

• Discord token is now automatically excluded when uploading configurations to the cloud. The token never leaves your local machine and is never stored in Firebase.
• When you upload a config to share with others, the discordToken field is automatically removed from configData before uploading.
• This prevents accidental token leaks when sharing presets, status cycles, or RPC configurations with other users.

What changes

• Config uploads now strip the Discord token automatically in the main process.
• Users can safely share configs without worrying about exposing their account token.
• The token remains stored locally only at \AppData\Roaming\Void Presence\discord-token-config.

What stays the same

• All other config data (title, description, cycles, intervals, RPC settings, etc.) uploads normally.
• Downloaded configs will apply all settings except the token — users must set their own token separately.
• Your local token storage is unchanged.

Why this matters

Your Discord token gives full access to your account. This fix ensures that even if you share a config publicly, your token stays private and local.

Discord RPC Now Starts After Workers Initialize

Added

• Worker-first RPC initialization: Discord Rich Presence now starts only after SMTC or hardware worker sends its first message, ensuring workers are fully initialized before RPC begins.

Improvements

• Deterministic startup order: RPC no longer starts in parallel with workers — it waits for nowPlaying (SMTC) or hardwareStats (hardware) message first.
• Duplicate RPC prevention: Added rpcStarted flag to guarantee RPC initializes exactly once, even if multiple worker messages arrive.

New Hardware Temperature & Logging Improvements

Added

• CPU/GPU temperature support: Implemented hardware temperature display via RPC — CPU and GPU temps are now shown in the status when hardwareMonitorEnabled is enabled, using the same style as other stats.

Improvements

• Minor log improvements: Refined logging in the RPC and hardware modules to make errors and status changes clearer and more consistent.

RPC Payload Priority & Bar Style

Improvements

• Explicit media/hardware priority: Introduced PresencePayload with priority and split state into activePayload (media) and fallbackPayload (hardware) — the visible payload is now always active ?? fallback, без смешивания.
• Cleaner timestamp handling: Unified timestamp calculation for media, range, persist, and cycle modes so Rich Presence always receives a consistent and sane start/end pair.
• Adaptive bar style visibility: The bar style row now reacts to RPC-related toggles (filters, hardware monitor, automatic activity) and only appears when one of these features is actually enabled.

Fixed

• Media/hardware merge bug: Fixed a conflict where media updates could be partially merged with hardware data, causing mixed details/state in Discord; media presence now fully overrides hardware while playback is active.
• TypeScript excess property error: Resolved PresencePayload typing by adding the priority field to the shared type, so internal priority logic no longer triggers “object literal may only specify known properties” during build.
• Bar style UI desync: Fixed cases where the bar style section stayed visible or hidden incorrectly by wiring all relevant toggles through localStorage and refreshBarStyleVisibility().

Persistent Timestamps

Improvements

• Guaranteed offset save on shutdown: stopDiscordRich() now awaits savePersistOffsetIfNeeded() — config file always updated before exit.
• Synchronous crash protection: File write completes before process termination — no more lost offsets on kill/crash.

Fixed

• Async race condition: updatePersistOffsetIfNeeded() fire-and-forget → awaited in stopDiscordRich() — Promise always resolves before shutdown.
• Lost writes on crash: Background setTimestampConfig() Promise hangs → Emergency save on stop with await guarantee.

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.