NipaPlay

NipaPlay v1.10.12 Changelog New Features & Experience Improvements Moved bullet screen display settings to the player menu (#702) Frequently used playback controls for bullet screens—including transparency, font size, font files, stroke, shadow, scrolling speed, display area, duplicate merging, and bullet type filtering—can now be adjusted directly in the NipaPlay and Cupertino player menus. The random color entry has also been restored on the Cupertino bullet screen settings page, and the display hierarchy of the filter word input box in NipaPlay has been streamlined for a cleaner interface. Bug Fixes & Optimizations Adapted bullet screen rendering surface for Erika on iOS (#700) On iOS, the Erika platform’s rendering surface defaults to full-screen dimensions, allowing bullet screens to cover letterbox black bars. The original AspectRatio wrapping method can still be enabled as a debug or rollback switch via the environment variable NIPAPLAY_IOS_ERIKA_ASPECT_SURFACE=1. Maintenance & Release Pipeline Switched Erika CI to prebuilt C APIs (#701) Builds for macOS, iOS, and Windows now utilize prebuilt artifacts of Erika v0.1.1. A Windows source code build path is retained as a fallback for mandatory builds or scenarios where prebuilt artifacts are disabled. Fixed fallback download for Windows mdk-sdk (#703) The GitHub fallback download for mdk-sdk in Windows builds now dynamically locates the latest release assets, supporting new naming conventions such as mdk-sdk-windows-x64-vs2026.7z. This prevents build failures caused by accidental 404 errors during fallback downloads. Corrected Android release build paths (#699) Removed redundant duplicate build/symbols-android-*/ symbol paths from the release workflow to resolve packaging errors stemming from bloated Android build output directories. Separate symbol file upload functionality remains intact. Strengthened release permissions (#698) The release workflow prioritizes the dedicated RELEASE_GITHUB_TOKEN, falling back to github.token only if the dedicated token is missing. This mitigates permission issues when querying release notes via the API and uploading build artifacts. Contributors @FurudeRika123, @MCDFsteve, @Shinokawa, @makabaka11