What is the NoMercy Player Core

The video player and the music player are mostly the same machine underneath. A queue is a queue, auth is auth, and a plugin system does not care whether it is driving a film or an album. nomercy-player-core is that shared machine pulled into one package, so the two players do not each carry their own copy. It is headless and you never run it on its own; the library packages bring it along as a dependency.

What’s in it

• Transport and a queue engine (play, pause, seek, next, shuffle, backlog)
• The auth pipeline (bearer tokens, 401 refresh, 403 propagation)
• The plugin system and a typed event bus
• i18n and storage
• An adapter port for every cross-cutting concern, swappable without subclassing the player

A fix in any of these lands in both players at once.

Where it sits

The core knows nothing about NoMercy server APIs or your app; that lives in the layers above it.

Next steps

• Quick Start: the smallest working setup
• Architecture: the full five-layer model and how the player is composed
• Adapter Ports: every port and its default
• Plugins: the built-in plugins shipped with the core