Maybe we need to check if the player is in dreamworld before even calling that function.
Because now it causes to much CPU because It's getting triggered all the time.

sure, 1.9 we can add nightmare and optimizations

I hit the wrong button :P

again

Could be closed ;D

I added it to the milestone so it must go open again :P

Fixed major issue, it was loading the world of the player from file every time it was triggered

trying to load player from dictionary (maybe)

I am doing a rework of player loading using hashmaps working with files

Cool, I have some stuff to do on my Mac first before I can get programming again (things like the up coming Lion update (currently running Lion Preview, so can't program Java on that one now)). Also I wan't to say that I can't figure out the github application on Windows. So Windows is a no no for me on github form now on :P

I had a slow day at work and am doing some programming tonight on my ubuntu dev machine

Fixed using hash maps to cache variables for players (If there are players with the same name, we will run into trouble)