A Watched Pot

Description

A watched pot never boils. A watched furnace never... ticks?

A Watched Pot is a fully configurable mod for both Neoforge/Forge and Fabric/Quilt that either stops blocks from ticking when they're looked at or restricts them to only tick when they *are* looked at, with filtering available via block tags.

Usage

On Forge, A Watched Pot can be configured through Forge's normal server configuration systems. There are currently two configuration options:

• The mod can use either a whitelist or a blacklist, which can be toggled via the use_whitelist option. If the option is enabled, only blocks in the watchedpot:whitelist block tag will be affected. If it's disabled (which it is by default), all blocks will be affected except those in the watchedpot:blacklist tag.
• The mod's behavior can be inverted via the invert_behavior option. If enabled, only blocks that are looked at will tick (of those affected); if disabled, all blocks will tick *unless* they are looked at.

By default, both options are set to false - that is, no block will tick while a player is looking at it.

To recap:

• use_whitelist=true, invert_behavior=false - blocks in the whitelist tag will not tick if they are looked at; all other blocks remain unchanged.
• use_whitelist=false, invert_behavior=false - all blocks will not tick if they are looked at, unless they are in the blacklist tag (in which case they remain unchanged).
• use_whitelist=true, invert_behavior=true - blocks in the whitelist tag will only tick if they are looked at; all other blocks remain unchanged.
• use_whitelist=false, invert_behavior=true - all blocks will only tick if they are looked at, unless they are in the blacklist tag (in which case, again, they remain unchanged).

On Fabric, the same options can be set via gamerules (watchedpot_useWhitelist and watchedpot_invertBehavior) to avoid an extra config dependency. This is unfortunately not quite as robust but it keeps the mod lightweight on both platforms. If you need to set default values (such as for a modpack) you can emulate that behavior with a KubeJS server_script, like so:

// For 1.18.2 change the line below to onEvent('server.load', event => {
ServerEvents.loaded(event => {
  if (event.server.persistentData.gameRules) return
  event.server.gameRules.set("watchedpot_useWhitelist", true)
  event.server.gameRules.set("watchedpot_invertBehavior", false)

  event.server.persistentData.gameRules = true
})

You can also use datapacks to achieve the same effect with a .mcfunction running the /gamerule command. See the Minecraft Wiki for information on that.

Demo

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install