Haha. Sadly, I've fixed this for the expansion coming out next week. :S
Haha. Sadly, I've fixed this for the expansion coming out next week. :S
Can you tell (from a programming standpoint) how this is happening? double species ids or something?
If I recall correctly, it was because a cached job wasn't clearing out its state properly. This had a small loophole where any other entity could bypass a requirement check.