The importance of move ordering made obvious

[JVMerlino]

So I (very briefly) had a bug in which all captures were moved to the end of the move order and left unsorted (IOW, left in the order that they were generated).

Try to guess how much elo this lost. I'll post the answer in 24 hours.

[JVMerlino]

The answer is that this bug caused a loss of 325 elo (+/- 22). So the one person who guessed 301-400 was correct.

I'd be interested to see what the results would be if anybody else gave this a quick test with their engine.

Thanks for voting!
jm

[jswaff]

Are you saying your next release will be 2900+ ?

[JVMerlino]

Are you saying your next release will be 2900+ ?

God no! I was saying that I temporarily created a bug which was then tested to show a loss of 325 elo. That bug is not in any released version.

[jswaff]

Are you saying your next release will be 2900+ ?

God no! I was saying that I temporarily created a bug which was then tested to show a loss of 325 elo. That bug is not in any released version.

lol, I read your post too fast and nearly fell out of my seat. Sorry, you did say "very briefly". For a while I thought you meant you had an existing bug that you only just now found and leapt 300+ points.

[JVMerlino]

Are you saying your next release will be 2900+ ?

God no! I was saying that I temporarily created a bug which was then tested to show a loss of 325 elo. That bug is not in any released version.

lol, I read your post too fast and nearly fell out of my seat. Sorry, you did say "very briefly". For a while I thought you meant you had an existing bug that you only just now found and leapt 300+ points.

Heh, yeah. The day Myrddin reaches 2900 is the day somebody (other than me) decides to add NNUE and a real tuning framework....and maybe not even then....