eMuleBB Help¶
This is the shortest path into the eMuleBB manuals. It is written for users who already understand eMule-style clients and want exact operating guidance.
I Want To...¶
| Task | Start Here |
|---|---|
| Understand what eMuleBB is and why it exists | Product Guide |
| Learn eMule from zero before tuning a serious profile | Power User Manual |
| Set up a fresh profile | Setup Guide |
| Use an existing eMule profile | Setup Guide |
Launch with an isolated -c profile |
Setup Guide |
| Fix Low ID, Kad firewalled, or bind problems | Network Guide |
| Improve search and download workflow | Downloads And Search |
| Share a large library deliberately | Sharing Guide |
| Wire eMuleBB into aMuTorrent or Arr apps | Stack Integration Guide |
| Make the first REST API call | REST Quickstart |
| Diagnose a crash, hang, slow startup, or REST failure | Troubleshooting Guide and Diagnostics Guide |
| Translate user-facing docs or homepage text | Translations And Localization |
Safe First Steps¶
- Keep the application directory separate from the profile directory.
- Back up an existing profile before first launch.
- Use
emulebb.exe -c <profile-dir>when testing a package or copied profile. - Confirm temp, incoming, and shared directories before starting downloads.
- Verify the desktop app before enabling REST, aMuTorrent, Radarr, or Sonarr.
Power User Notes¶
eMuleBB keeps the classic eMule desktop workflow while adding maintained broadband defaults, diagnostics, large-library handling, and trusted local controller surfaces.
The desktop app owns live state. Controllers and adapters should read or mutate that state through documented APIs; they do not replace the native client.