Got this error back when we moved from 1.16 to 1.17, a later version of Paper fixed it but now it's back again as we've just moved to 1.18.
Updated to the latest paper version seems to have fixed the issue for us.
Also having the same issue, interested in any work-arounds folks know about. Thanks!
Jeff Ginger
Got this error back when we moved from 1.16 to 1.17, a later version of Paper fixed it but now it's back again as we've just moved to 1.18.