Interesting, that was something I thought I had fixed in the previous update, it was caused by something in the monster frequency data being null, there must be something else in the data structure that is null but it isn't coming from the monster frequency, I'll have a look