You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as the title says, turning on either the restrictToCreative or generatedWaystonesUnbreakable config options will still allow players to break the waystones in a certain way- be that either with create drills, hexcasting block breaking spells or some other block breaking technique that comes from a mod i didn't test. my theory is that the waystone ignores the config option when something other than a player attempts to break the waystone, be that a 3X3 pickaxe from a random 3X3 pickaxe mod or an entity that can break blocks with or without the player's aid. with that said, maybe
Logs
No response
Do you use any performance-enhancing mods (e.g. OptiFine)?
No response
The text was updated successfully, but these errors were encountered:
All options allowing for unbreakable waystones will be removed in 1.20. Servers and adventure maps should instead make use of the existing tools (either in Vanilla or through claiming/permission mods) for limiting breakability.
Minecraft Version
1.18.x
Mod Loader
Forge
Mod Loader Version
40.1.68
Mod Version
waystones-forge-1.18.2-10.1.0
Describe the Issue
as the title says, turning on either the restrictToCreative or generatedWaystonesUnbreakable config options will still allow players to break the waystones in a certain way- be that either with create drills, hexcasting block breaking spells or some other block breaking technique that comes from a mod i didn't test. my theory is that the waystone ignores the config option when something other than a player attempts to break the waystone, be that a 3X3 pickaxe from a random 3X3 pickaxe mod or an entity that can break blocks with or without the player's aid. with that said, maybe
Logs
No response
Do you use any performance-enhancing mods (e.g. OptiFine)?
No response
The text was updated successfully, but these errors were encountered: