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.