Shift+click is one of the more useful features in vanilla MC, we definitely need to do that. Create a ticket in the support system, so that it doesn't rot in the middle of a forum thread only.
STR_Warrior, you're in for some heavyweight testing
First of all, download and install MS Standalone Profiler (a tool that records program's execution and generates a detailed report on where the program is spending its time) from here:
http://www.microsoft.com/en-us/download/...x?id=18277
Then, from the nightbuild server, download the _profiled package ( http://mc-server.xoft.cz/mcserver_win_593_profiled.7z ) and extract it to a copy of your MCServer installation (you don't want to ruin your normal MCServer, do you?) Note that I've packed only the files essential for profiling, there's no configuration etc., you need to provide those from your normal MCServer folder.
Don't run the MCServer program there directly, but instead, run the "profile_run.cmd".
If all went well, this will run MCServer. Go ahead and reproduce the CPU usage for some time (at least a minute). When done, shut down MCServer normally by typing stop into the server console.
This process should create a file, "MCServer_profiledata.vsp" next to the server executable. That's the detailed report file. Post it here.
If the server didn't get launched or the file wasn't created, post the errors that you see.
Just to give you an idea of what info you'll be providing me with, this is what the report looks like when processed:
![[Image: profiler_gen.png]](http://xoft.cz/img/mcs/profiler_gen.png)
STR_Warrior, you're in for some heavyweight testing
First of all, download and install MS Standalone Profiler (a tool that records program's execution and generates a detailed report on where the program is spending its time) from here:
http://www.microsoft.com/en-us/download/...x?id=18277
Then, from the nightbuild server, download the _profiled package ( http://mc-server.xoft.cz/mcserver_win_593_profiled.7z ) and extract it to a copy of your MCServer installation (you don't want to ruin your normal MCServer, do you?) Note that I've packed only the files essential for profiling, there's no configuration etc., you need to provide those from your normal MCServer folder.
Don't run the MCServer program there directly, but instead, run the "profile_run.cmd".
If all went well, this will run MCServer. Go ahead and reproduce the CPU usage for some time (at least a minute). When done, shut down MCServer normally by typing stop into the server console.
This process should create a file, "MCServer_profiledata.vsp" next to the server executable. That's the detailed report file. Post it here.
If the server didn't get launched or the file wasn't created, post the errors that you see.
Just to give you an idea of what info you'll be providing me with, this is what the report looks like when processed: