SeedCracker VS LuckPerms

If you don't respect this, you can use https://github.com/KaptainWutax/SeedCracker

Custom code, usually. KaptainWutax made a program a few years ago which can crack seeds just by scanning the world. When seed cracking, though, you are looking for certain features which can rule out many many seeds very easily. For example, finding specific dungeon coordinates and mossy cobble patterns can narrow it down dramatically. For this process, you need not scan that much since it's some simple maths applied to not that many blocks and not checking very many times.

Im not an expert but cords are needed or at least if you want to solve it in any time. you say you play on that SMP so maybe use seedcrackermod but KaptainWutax. It is a fabric mod that searches the world for structures like shipwrecks and once you find 5 of them it can crack the seed within minutes or even less (depends on your gpu)

Otherwise, I found a mod that will calculate a server's seed but you have to actually be on the server; most of the actual tools seem to be private, most likely due to security concerns as stated above.

But if you just need to provide permissions, you need an additional plugin like LuckPerms. And with its help, give the players the necessary permissions. How to use this plugin you can find on YouTube. What rights are available in the Chest Commands plugin you can find in the plugin documentation.

You need to install and configure a permission mod/plugin like LuckPerms.

This subreddit is for vanilla commands. I think you should ask on the r/admincraft subreddit for plugins. I can only recommend the LuckPerms plugin. You can find more video tutorials on YouTube for this plugin.

LuckPerms.

Get luckperms (plugin) which is a permission platform which will allow you to control who is allowed to do what i.e. allowing you to do server admin stuff while denying some of the more destructive commands to your kids

LuckPerms is a good permissions plugin if it's needed. I don't know why you would, but maybe.

In that case, there‘s no easy fix. This seems to be a bug, as this should work already. At least according to this issue.

I have encountered the same problem due to missing permissions in LuckPerms. If you are using LuckPerms, try the /lp verbose command to find the missing permission. You can find how to use it here.