This plugin provides TheIntroDB API configuration and a client for TheIntroDB (intro/recap/credits/preview timestamps by TMDB ID). Emby does not have a built-in Media Segments API like Jellyfin, so this plugin does not add skip buttons by itself; it stores settings and exposes an API client for custom integrations or future Emby features.
Minimal Emby Server plugin skeleton. Built with .NET Standard 2.0 and MediaBrowser.Server.Core.
- .NET SDK (6.0+ for building; plugin targets netstandard2.0)
- Emby Server for testing
- Customize
TheIntroDB/Plugin.cs: setNameand a uniqueId(GUID). - Build:
dotnet build TheIntroDB.sln - Copy the built DLL (and PDB if debugging) to your Emby plugin folder (e.g.
%AppData%\Emby-Server\programdata\plugins\on Windows, or thepluginsdirectory under your Emby data path).
From this repo (or after cloning it):
# Install the dotnet template (path to the content folder)
dotnet new -i ./dotnet-template/content
# Create a new plugin (e.g. in a sibling directory or new folder)
dotnet new Emby-plugin -n MyPlugin -o ../MyEmbyPluginThen open the new project, set Name and Id in the Plugin class, and build.
TheIntroDB/– Plugin projectPlugin.cs– Main plugin class (Name, Id, config page registration)Configuration/PluginConfiguration.cs– Config modelConfiguration/configPage.html– Dashboard config page (embedded)
TheIntroDB.sln– Solution fileDirectory.Build.props– Shared version and MSBuild settings.editorconfig– Coding style and formatting.vscode/– VS Code launch (run Emby with plugin), tasks (build-and-copy), settings (paths).github/workflows/– CI: build and test on push/PRdotnet-template/–dotnet new Emby-plugintemplate
- Set paths in
.vscode/settings.json:embyDir(server install, e.g..../Emby-Server/system),embyWindowsDataDir/embyLinuxDataDir/embyOsxDataDir(Emby data directory). - Use the Launch Emby Server configuration; it runs the build-and-copy task then starts Emby so you can attach breakpoints.