Minecraft Version
1.21.1
Mod Loader
NeoForge
Describe the Issue
Hi there,
Messaged you on Discord about this. I'm having a really odd issue with Unbreakables.
I'm trying to configure it so that any waystone, no matter who has placed it or how it is generated, is unbreakable. I've changed the config to accommodate this, see below for the contents of my unbreakables-common.toml config file.
#IDs of inbuilt rulesets to enable. For example, "waystones:generated_waystones" makes all generated waystones breakable.
rulesets = []
#List of custom rules with comma-separated parameters in parentheses. Conditions can be defined as comma-separated list in square brackets. Will be applied in order.
rules = [ "[is_tag(waystones:waystones)] refuse($chat.waystones.cannot_break_waystone)" ]
In Single Player, this works fine. I place down any waystone or go to any generated one and I cannot break it and the message pops up telling me I can't do it.
In multiplayer however this is different. For me, the behaviour is the same - I am unable to break waystones of any kind and the message pops up. For other players though they can break waystones just fine despite the config being the same on the server.
I don't understand why there's a different rule for me and a different one for other players. If I could have some help I would appreciate it!
Logs
latest.log
Minecraft Version
1.21.1
Mod Loader
NeoForge
Describe the Issue
Hi there,
Messaged you on Discord about this. I'm having a really odd issue with Unbreakables.
I'm trying to configure it so that any waystone, no matter who has placed it or how it is generated, is unbreakable. I've changed the config to accommodate this, see below for the contents of my unbreakables-common.toml config file.
#IDs of inbuilt rulesets to enable. For example, "waystones:generated_waystones" makes all generated waystones breakable.
rulesets = []
#List of custom rules with comma-separated parameters in parentheses. Conditions can be defined as comma-separated list in square brackets. Will be applied in order.
rules = [ "[is_tag(waystones:waystones)] refuse($chat.waystones.cannot_break_waystone)" ]
In Single Player, this works fine. I place down any waystone or go to any generated one and I cannot break it and the message pops up telling me I can't do it.
In multiplayer however this is different. For me, the behaviour is the same - I am unable to break waystones of any kind and the message pops up. For other players though they can break waystones just fine despite the config being the same on the server.
I don't understand why there's a different rule for me and a different one for other players. If I could have some help I would appreciate it!
Logs
latest.log