The ArcEmu Test Realm used to run on a server own but someone not affiliated at all with ArcEmu but who let me use it. It's primarly used to run other applications with higher priority but for few months they ran together all happy. As a Test Realm, its purpose was to help developers track down issues, especially memory leaks since we were using a memory profile, and to give users an ArcEmu Certified realm where to test if bugs happening on local servers happened on our realm, too. When an issue was reported it usually took less than 24 hours for us to find the reason, write a patch, apply it to the Test Realm and commit it but around April this way to work got slowed down by a rate that I thought inacceptable: it was reporting a lot of memory leaks caused by a recent commit but who added them didn't do anything to fix them, nor he looked interested doing that anytime soon. This is the main reason it was shut down: its reports were ignored.
As often happens, time passes and things change: we decided to revocate the status of Developer from that guy, fixed the issues that he caused (it's still an ongoing process actually), so the next step would be to put the Test Realm back.
There's a little problem right now: there are more applications with higher priority now and the limited amount of RAM (4 GB with a 64 bits OS) doesn't allow an instance of ArcEmu running with the memory profiler attached. Maybe we'll come up with a trade-off, like running the Test Realm with limited features (loot tables, waypoints, maps, vmaps, all these use SOO much memory), that will give our users a basic overview of what ArcEmu can be.
This should be a pretty good explaination

The ArcEmu Test Realm used to run on a server own but someone not affiliated at all with ArcEmu but who let me use it. It's primarly used to run other applications with higher priority but for few months they ran together all happy. As a Test Realm, its purpose was to help developers track down issues, especially memory leaks since we were using a memory profile, and to give users an ArcEmu Certified realm where to test if bugs happening on local servers happened on our realm, too. When an issue was reported it usually took less than 24 hours for us to find the reason, write a patch, apply it to the Test Realm and commit it but around April this way to work got slowed down by a rate that I thought inacceptable: it was reporting a lot of memory leaks caused by a recent commit but who added them didn't do anything to fix them, nor he looked interested doing that anytime soon. This is the main reason it was shut down: its reports were ignored.
As often happens, time passes and things change: we decided to revocate the status of Developer from that guy, fixed the issues that he caused (it's still an ongoing process actually), so the next step would be to put the Test Realm back.
There's a little problem right now: there are more applications with higher priority now and the limited amount of RAM (4 GB with a 64 bits OS) doesn't allow an instance of ArcEmu running with the memory profiler attached. Maybe we'll come up with a trade-off, like running the Test Realm with limited features (loot tables, waypoints, maps, vmaps, all these use SOO much memory), that will give our users a basic overview of what ArcEmu can be.
This should be a pretty good explaination