eMule Fans 電騾愛好者

電騾愛好者們最常用的eMule mods之一，「刀疤天使騾」 – eMule ScarAngel Mod的新版v4.2由作者Stulle在eMule（電騾）官方論壇發布了。它基於eMule v0.50a Xtreme 8.1製作。除了繼承了Xtreme的特性，天使騾更關注於功能的強大，例如：增加了多種積分系統，老闆鍵（一鍵隱藏），系統後台服務運行（無界面），多賬號網頁遠程管理支持，TBH迷你騾（minimule），自動備份配置文件，增強的下載分類管理，稀有文件推送，更多高級功能設置等等。

下載ScarAngel v4.2：
eMule 0.50a ScarAngel v4.2 壓縮檔
（推薦老手使用的「綠色」壓縮包，解壓後直接使用。Sourceforge鏡像。伺服器列表、IPFilter、IP2C等組件需自己手動添加更新。如果在舊版上更新，一般情況下只需覆蓋eMule.exe即可）
eMule 0.50a ScarAngel v4.2 安裝包
（推薦新手使用的安裝嚮導包，安裝後使用。Sourceforge鏡像。各組件也需自己手動添加更新）
eMule 0.50a ScarAngel v4.2 源代碼
（程序員用。Sourceforge鏡像）
eMule 0.50a ScarAngel v4.2 開發者debug包
（程序員用）

另參見：

• eMule ScarAngel Mod在eMule官方論壇的發布貼
• eMule ScarAngel Mod官方主頁
• SourceForge上舊版ScarAngel下載

從舊版ScarAngel更新到新版，可以直接用新版的emule.exe覆蓋原來的。如果想更徹底地更新，或者需要從其他eMule換用到ScarAngel，請參考《如何安全、徹底、有效地更換eMule Mod》。

電驢（eD2k）鏈接下載

詳細更新日誌

關於此次更新，作者在論壇上的說明：

Dear customers,

I am happy to bring you a new and improved version of ScarAngel. It seems our hard working developers were having too much fun on the last release. But don’t fear, those days are over! No more fun within the realm of ScarAngel Industries Ltd. from hear on out!
This release will do a couple of things differently in order to avoid different threads changing the upload list. We hope this will improve stability for you, our dear customers. Additionally, we also added two minor GUI goodies. As usual, check the changelog for more.

Yours dearly, Stulle 🙂

更新日誌：

eMule v0.50a ScarAngel v4.2:
————————
– 22.06.2011 –
——————————————————————————-
based on eMule 0.50a Xtreme 8.1 compiled with vs2010 SP1

Changed: Pause UBT when moving down slots in upload [Stulle] – Stulle
Changed: Schedule blocking clients for removal [Stulle] – Stulle
Changed: Schedule clients for moving down [Stulle] – Stulle
Changed: Show ModID in systray dialog sidebar [Stulle] – Stulle
Changed: Display ratio activation in WebInterface [Stulle] – Stulle

Fixed: Potential NULL-pointer bugs in Upload Bandwidth Throttler [Stulle] – Stulle

Note: The schedule changes will delay removal of blocking or moving down clients so the action will
be done when going through the uploading sockets the next time to avoid exceptions due to
changes in the upload list done by another thread while going through the sockets.