❗ Checklist

• I am using the official english version of Slimefun and did not modify the jar.
• I am using an up to date "DEV" (not "RC") version of Slimefun.
• I am aware that issues related to Slimefun addons need to be reported on their bug trackers and not here.
• I searched for similar open issues and could not find an existing bug report on this.

📍 Description

I have more plugins on the server, but gradually removing it failed to detect an error.

(if i have Slimefun plugin on the server, i cant place itemsadders block intro another. The problem is that when I start removing plugins and then I want to add any other (even LuckPerms) there is a problem that I can't lay blocks (if it is on the Slimefun server)

Alternatively, please help which plugins I should remove what may be causing the issues. Honestly? On the server I had:

And after adding the Vault plugin there was a problem (completely nonsensical)

I've been solving this problem for a month now and I haven't been able to fix the error. Please help.

📑 Reproduction Steps

1. Install ItemsAdder and Slimefun (with another 21 plugins) and after place on the itemsadder block vanilla blocks.

💡 Expected Behavior

You cant place vanilla block on the itemsadder blocks

📷 Screenshots / Videos

https://www.youtube.com/watch?v=GoqjhGT1wsU

📜 Server Log

https://pastebin.com/QKpcjFgE

📂 /error-reports/ folder

Nothing

💻 Server Software

Paper

🎮 Minecraft Version

1.17.x

⭐ Slimefun version

🧭 Other plugins

Is this still an issue? I also don't think this is caused by Slimefun if it is but instead by one of the other plugins

Is this still an issue?

Cant test it since I dont have IA license.

Is this still an issue?

Cant test it since I dont have IA license.

I believe there is a free version

Thanks for the info, I'll close this issue as resolved.

Is this still an issue? I also don't think this is caused by Slimefun if it is but instead by one of the other plugins

Nope, its fixed. Before, I was using a custom plugin for this that it created via shrink packets :D It was a strange problem because it happened occasionally. However, in current versions it already works.