FAQ
Short answers for users who want the classic eMule workflow with better broadband control, safer networking, and clearer release proof.
eMuleBB can bind P2P traffic to a named interface or local address, and it can block startup when the target is missing. Keep your VPN kill switch, firewall, and WebServer/REST bind policy separate.
Read more: Network guideeMuleBB keeps the familiar Shared Files model: add curated roots, keep Temp out of shares, use stable paths, and let hashing finish before scaling up.
Read more: Sharing guideeMuleBB adds a finite broadband upload-slot target, weak-slot recycling, and practical diagnostics so fast lines stay useful without flooding the queue.
Read more: Downloads and search guideNo. eMuleBB keeps stock-compatible eD2K and Kad behavior as the default, then improves local limits, automation, diagnostics, and release discipline around it.
Read more: Product guideUse eMuleBB nightlies for public testing now. The first public release candidate is planned as 0.7.3-rc.1, with 0.7.3 as the stable target after the gates pass.
Read more: 0.7.3 release dashboardeMuleBB treats WebServer and REST as trusted-controller surfaces. Enable them only when needed, bind deliberately, use an API key, and avoid broad exposure.
Read more: Controllers and REST guideeMuleBB keeps classic server, global, and Kad search workflows. Start with trusted server lists, bootstrap Kad deliberately, and diagnose Low ID or firewalled Kad before changing many settings.
Read more: Network guideeMuleBB is built for large libraries: add roots gradually, use long-path capable Windows setups, review share-ignore rules, and let startup cache work settle.
Read more: Sharing guideYes. eMuleBB exposes an authenticated JSON REST API for trusted local controllers while keeping native transfer and sharing semantics in the desktop app.
Read more: Controllers and REST guide