This appears to be a bug that snuck in with the 1.1.1 update. If we release another patch, it'll be fixed. The full credits are linked on this page as well.
