I have received a few good suggestions to how I can improve the speed of Mediocre. I have also learned a lot about optimizing Java while researching myself.
Many of the things I have changed are very program specific. I do not know how much use it can be for other programmers other then the general things like not allocate too many objects etc. I might try to put together a short list of suggestions what to look for in the code, but generally it is up to every programmer to find these things in his own code.
A thing like the isAttacked()-method not checking for color of the piece before doing the calculations, is more of a bug than an actual general improvement.
Anyway I am going to finish up with the improvements (right now quiescent search and move sorting are broken due to the new move representation) and then release a (hopefully) much faster version of Mediocre.
On another note I have been receiving many very good suggestions through e-mail, along with unwanted spam that is starting to add up. So I for now use a thing called 'spambutcher' instead of printing my e-mail address in clear text. Just follow the link and enter the phrase and you get my e-mail address. This is to prevent automatic gathering of e-mail addresses.
Hope it is not too much of a hassle. :)