For PermissionsEx 2.0, there are a significant number of API breaks, meaning that users running that version of PEX will not be able to use EssX as it is currently. This line should be adjusted to check an option through the Vault chat service rather than directly hooking into PEX.

This will reduce breaks as more users switch to PEX2.

I'm confused, that method does nothing with the chat service? It checks for build permissions.

That line gets the PEX user, and the next line gets an option from the PEX user (using PEX's own API). Vault's chat service provides an implementation-abstract way of fetching the same data (the build option).

Ah, I wasn't aware that Vault's chat service provided metadata capabilities. I'll take a look.

Would this work? 7d33814

Looks like that fixes it! Thanks a ton.

Thanks for reporting :)