BASpark: Blue Archive mouse effects rendered on the Windows desktop

BASpark puts Blue Archive mouse effects on the Windows desktop

BASpark is a Windows desktop utility for interactive visual effects, built to reproduce the click and particle dynamics seen in the game Blue Archive. The effect follows the cursor: click, and the desktop throws off the kind of particle response the game is known for. The repository description calls it a Windows mouse effect tool reconstructing Blue Archive UI style using HTML5/Canvas, and the README calls it lightweight and versatile, dedicated to precisely reproducing those clicking and particle fluid dynamics. The audience is narrow and self-evident: people running Windows who want an animated desktop flourish in that specific visual style, not a general purpose window manager or a theming tool. It ships with an English README and a Simplified Chinese one under docs/README_zh.md, and the project page is basp.vcbs.top.

A WPF host wrapping a WebView2 canvas

The rendering architecture is hybrid, and the README is explicit about the split. BASpark runs on a WPF host infrastructure powered by localized WebView2 rendering runtimes. In practice that means the desktop application layer is C# and WPF, while the actual drawing of particles, easing and textures happens in an HTML5 canvas surface embedded through WebView2. The repository topics name both technologies, webview2 and wpf, and the source tree follows the split: src/ holds the application, and the web assets live inside it. The reason for this arrangement is visible in the layout rather than documented as a design essay, but it is a familiar trade-off. Canvas gives easy particle drawing and easing curves, and WebView2 lets that code be written in a language a web developer already knows, at the cost of embedding a browser runtime in a background utility.

The renderer wakes on input and hibernates when idle

The README claims aggressive resource optimization through WebView2 lifecycle management, and describes a specific behaviour: rendering procedures are invoked strictly upon input triggers, and the graphics context completely hibernates when idle, causing zero overhead to active background processes or system resources. That is the design that makes a full-screen, always-present overlay tolerable. The same section claims system-wide environment perception, full compatibility with full-screen entertainment and production environments, and real-time hook intercepting that routes input feedback without interrupting the target processes. Treat the wording carefully: it is the project's own description, and the README does not publish measurements, frame timings or memory figures to back it up. What can be checked is the behaviour it implies, since a background overlay that renders continuously would show up as CPU time in a task manager.

Downloading BASpark_Installer_vX.X.X_x64.exe for Windows 10 or 11

Installation is a Windows installer rather than a package manager entry, and the README sets out the requirements first. The tool needs a 64-bit processor and a native OS environment, Windows 10 or Windows 11 on X64 architectures, a minimum 200 MB RAM allocation, a discrete or integrated GPU supporting DirectX 11 or OpenGL, and a minimum 200 MB of physical storage. To install, the README says to open the official Releases Hub on GitHub, download the latest setup binary named BASpark_Installer_vX.X.X_x64.exe, execute it, and follow the deployment wizard to initialize the localized directory. The repository holds setup.iss, which is the Inno Setup script an installer of this kind is built from, plus ChineseSimplified.isl and Japanese.isl for installer languages. Launch the main execution routine afterwards and the effects appear.

src/Web/ holds the animation, so the canvas can be edited without rebuilding

For contributors, the interesting part of the layout is that the central animation loops and visual textures are compiled inside HTML5/Canvas components rather than inside the C# runtime wrapper. The README says this means you can view and troubleshoot elements in src/Web/ in real time in VS Code without rebuilding the whole C# runtime wrapper structure. The setup steps are short: clone the repository, open it in Visual Studio Code with the C# Dev Kit extension installed, and edit the web assets directly.

git clone https://github.com/DoomVoss/BASpark.git
cd BASpark

code .

The project solution is BASpark.sln, and the repository also carries assets/, docs/, pages/, tests/ and a SECURITY.md. A contributor submits changes as a pull request and is asked to follow the project's established formatting and code quality rules.

The MIT licence and the non-commercial clause contradict each other

Here is the part to read before you adopt the code rather than the effect. The README states the project is distributed globally under the MIT License, and the licence file names MIT with a 2026 copyright line. The same README also states the utility is published strictly as a non-commercial, fan-made interactive tribute project, and that commercial distribution or unauthorized reselling of the code or asset package is strictly prohibited. Those two statements are in tension, and an MIT grant does not normally carry a non-commercial restriction. The README further notes that the design language, trademark graphics and creative aesthetics draw artistic inspiration from the intellectual property of Nexon and Yostar, the owners of Blue Archive. No legal advice is offered here, but the practical consequence is clear: MIT is a convenient licence to read, and the non-commercial and trademark paragraphs are the ones that determine what you may actually ship.

Where BASpark is the wrong tool

Several ordinary situations rule this project out. Any desktop that is not Windows 10 or 11 on x64 is unsupported, and the README lists no macOS or Linux path, so a cross-platform team cannot standardise on it. A machine without the WebView2 runtime, or without a DirectX 11 or OpenGL capable GPU, fails the stated hardware requirements. The tool is also not a cursor theme manager and not a desktop pet framework: it is a single visual effect with a specific game as its reference, and the repository topics list cursors, cursor-theme, desktop-pet and desktop-animation alongside each other, which describes a family of small utilities rather than a configurable system. Finally, if you want to ship anything commercial with this code or these assets, the non-commercial disclaimer and the Nexon / Yostar intellectual property note both push back.

A v2.0.0 pre-release sits ahead of the stable tags

The release record matters here because the project moved to a new major version shortly before its last push. The last push was on 2026-08-20. Around it sit three tagged releases: BASpark Release v1.6.1 on 2026-06-30, BASpark Release v1.6.2 on 2026-07-31, and BASpark Pre-release v2.0.0 on 2026-08-18. The naming is itself the signal, since v2.0.0 is labelled a pre-release while v1.6.1 and v1.6.2 are labelled releases. Anyone installing from the Releases Hub should therefore check which artefact they are taking rather than assuming the highest version number is the stable one. The README carries no changelog section, so those tagged names are the most concrete maintenance signal available for a user deciding whether to run this on a daily machine.

Editorial conclusion

BASpark makes sense for a Windows 10 or 11 desktop that wants animated cursor feedback in the Blue Archive style, and for developers who want to edit canvas animations directly in src/Web/. It does not make sense for cross-platform teams, for machines without WebView2, or for any commercial product, because the README states the project is a non-commercial fan tribute while the repository carries an MIT licence. Before installing BASpark_Installer_vX.X.X_x64.exe, check that the release you pick is a stable tag rather than the v2.0.0 pre-release, and read the MIT text in LICENSE next to the non-commercial disclaimer in the README.

Frequently asked questions

Official sources

1. DoomVoss/BASpark on GitHub
2. License: MIT
3. Project website
4. README
5. Releases