NoTick
NoTick 是一个专为大型模组化 Minecraft 服务器构建的服务端实体刻优化器。
大型整合包会浪费大量 CPU 时间来刷新(tick)那些玩家无法看到、到达、战斗、收集或交互的怪物、物品和其他实体。NoTick 通过跳过符合条件的远距离实体刻,同时保护重要的游戏玩法,从而减少这些后台工作。
目标很简单:减少无效的模拟运算,为服务器实际正在使用的部分腾出更多刻预算。
服务器影响仪表板
| NoTick 统计 | 数值 |
|---|---|
| 必需依赖项 | Fabric 版本需要 Fabric API |
| 支持的构建目标 | 6 |
| 可选领地集成 | FTB Chunks + Open Parties and Claims |
| 管理员命令 | 5 |
| 主要优化目标 | 远处未使用实体的刷新 |
| 安全控制 | 白名单、维度、突袭、领地、活跃区块 |
刻节省示例
NoTick 的节省效果与符合条件的远处实体数量成正比。如果一个实体在玩家范围之外,且不受白名单、领地、突袭规则或活跃区块保护的约束,其正常的实体刻可以被跳过。
| 符合条件的远处实体 | 每服务器刻跳过的刻调用次数 | 每秒 20 TPS 下跳过的刻调用次数 |
|---|---|---|
| 100 | 最多 100 | 最多 2,000 |
| 500 | 最多 500 | 最多 10,000 |
| 1,000 | 最多 1,000 | 最多 20,000 |
| 2,500 | 最多 2,500 | 最多 50,000 |
这些并非虚假的基准测试声明。它们展示了优化的数学原理:较少的符合条件远处实体被刷新,意味着服务器所需的后台实体工作量更少。
保持活跃的实体
玩家及附近的游戏玩法 [ACTIVE] 始终正常刷新
白名单实体/模组 [ACTIVE] 受配置保护
已领地的基地和农场 [ACTIVE] 受 FTB Chunks 或 OPAC 保护
受突袭影响的实体 [ACTIVE] 受突袭规则保护
远处未使用的怪物/实体 [OPTIMIZE] 当安全处于范围外时跳过刷新
远处掉落的物品 [OPTIONAL] 可配置的基于概率的刷新
决策流程
实体刻开始
-> 是玩家吗? 正常刷新
-> 被配置禁用? 正常刷新
-> 是白名单实体或模组? 正常刷新
-> 靠近玩家? 正常刷新
-> 位于活跃或已领地的区块中? 正常刷新
-> 受突袭保护? 正常刷新
-> 是符合条件的远处实体? 跳过刷新
为什么服务器使用 NoTick
- 在高实体数量的世界中降低后台实体刷新的成本
- 帮助稳定大型整合包和繁忙 SMP 服务器的 TPS
- 通过注册表 ID 支持模组化的怪物和实体
- 通过白名单和安全机制保护重要 gameplay
- 支持基于领地的刷新,适用于基地、农场和自动化区域
- 为管理员提供游戏内的诊断工具和配置重载功能
- 仅在 Fabric 上需要 Fabric API;Forge 和 NeoForge 版本无需额外依赖模组
核心功能
- 基于距离的实体刻优化
- 可配置的水平与垂直刷新范围
- 可选的掉落物品优化,支持可配置的远处刷新概率
- 实体白名单及完整模组 ID 白名单支持
- 针对突袭的特定刷新控制
- 维度白名单支持
- 对最近使用过或类似基地区块的活跃区块保护
- 可选的 FTB Chunks 集成
- 可选的 Open Parties and Claims 集成
/notick诊断命令套件/notick reload用于在不重启的情况下重载配置
管理员命令
所有命令都需要操作员/管理员权限。
| 命令 | 用途 |
|---|---|
/notick |
显示当前优化状态 |
/notick status |
显示详细设置和集成状态 |
/notick here |
显示您当前所在区块的诊断信息 |
/notick reload |
从磁盘重载配置 |
/notick help |
列出可用命令 |
兼容性
NoTick 专为模组化服务器设计,并通过标准注册表 ID 支持模组化实体。
当前构建版本:
- Fabric 1.20.1 和 1.21.1
- Forge 1.20.1
- NeoForge 1.21.1, 26.1.2, 和 26.2
请使用配置白名单来保护以下情况:
- Boss 和多部件怪物
- 脚本化或事件驱动的实体
- 仿玩家风格的自动化
- 来自大型内容模组的投射物或特殊实体
- 任何必须让远处实体保持正常刷新的模组
如果安装了 FTB Chunks 或 Open Parties and Claims,已领地的区块可以被视为受保护区域。这对于在玩家离开时仍需保持正常行为的农场、自动化区域和基地非常有用。
最佳适用场景
NoTick 在以下场景中效果最强:
- 大型模组化生存服务器
- 具有大量被动实体负载的 kitchensink 整合包
- 拥有众多基地、农场和维度的 SMP 服务器
- 远处怪物和物品造成持续刻成本的服务器
- 需要管理员控制的性能安全措施的整合包
重要提示
NoTick 专注于性能优化,可能会改变远离玩家且未受保护的实体的行为。
如果某个农场或装置必须在没有人在附近时运行,请通过区块领地、活跃区块保护措施、实体白名单、模组 ID 白名单或维度规则对其进行保护。
致谢
最初基于 Txni 开发的 DoesItTick。
由 Rique 维护的分叉版本。
NoTick
NoTick is a server-side entity tick optimizer built for large modded Minecraft servers.
Large packs can waste a lot of CPU time ticking mobs, items, and other entities that no player can see, reach, fight, collect, or interact with. NoTick cuts that background work by skipping eligible far-away entity ticks while keeping important gameplay protected.
The goal is simple: less wasted simulation, more tick budget for the parts of the server players are actually using.
Server Impact Dashboard
| NoTick Stat | Value |
|---|---|
| Required dependencies | Fabric API on Fabric builds |
| Supported build targets | 6 |
| Optional claim integrations | FTB Chunks + Open Parties and Claims |
| Admin commands | 5 |
| Main optimization target | Distant unused entity ticking |
| Safety controls | Whitelists, dimensions, raids, claims, active chunks |
Tick Savings Example
NoTick's savings scale with the number of eligible distant entities. If an entity is outside player range and is not protected by a whitelist, claim, raid rule, or active chunk safeguard, its normal entity tick can be skipped.
| Eligible distant entities | Tick calls skipped per server tick | Tick calls skipped per second at 20 TPS |
|---|---|---|
| 100 | up to 100 | up to 2,000 |
| 500 | up to 500 | up to 10,000 |
| 1,000 | up to 1,000 | up to 20,000 |
| 2,500 | up to 2,500 | up to 50,000 |
These are not fake benchmark claims. They show the math behind the optimization: fewer eligible distant entities ticking means less background entity work for the server.
What Stays Active
Players and nearby gameplay [ACTIVE] always ticks normally
Whitelisted entities/mods [ACTIVE] protected by config
Claimed bases and farms [ACTIVE] protected with FTB Chunks or OPAC
Raid-sensitive entities [ACTIVE] protected by raid rules
Distant unused mobs/entities [OPTIMIZE] skipped when safely outside range
Distant dropped items [OPTIONAL] configurable chance-based ticking
Decision Flow
Entity tick starts
-> Player? Tick normally
-> Disabled by config? Tick normally
-> Whitelisted entity or mod? Tick normally
-> Near a player? Tick normally
-> In active or claimed chunk? Tick normally
-> Raid-protected? Tick normally
-> Eligible distant entity? Skip tick
Why Servers Use NoTick
- Reduces background entity ticking cost in high-entity worlds
- Helps stabilize TPS in large modpacks and busy SMPs
- Works with modded mobs and entities through registry IDs
- Protects important gameplay through whitelists and safeguards
- Supports claim-aware ticking for bases, farms, and automation zones
- Gives admins diagnostics and config reload tools in-game
- Requires only Fabric API on Fabric; Forge and NeoForge builds need no extra dependency mod
Core Features
- Distance-based entity tick optimization
- Configurable horizontal and vertical tick ranges
- Optional dropped-item optimization with configurable distant tick chance
- Entity whitelist and full mod ID whitelist support
- Raid-specific ticking controls
- Dimension whitelist support
- Active chunk protection for recently used or base-like chunks
- Optional FTB Chunks integration
- Optional Open Parties and Claims integration
/notickdiagnostics command suite/notick reloadfor config reloads without restarting
Admin Commands
All commands require operator/admin permissions.
| Command | Purpose |
|---|---|
/notick |
Shows current optimization status |
/notick status |
Shows detailed settings and integration status |
/notick here |
Shows diagnostics for your current chunk |
/notick reload |
Reloads the config from disk |
/notick help |
Lists available commands |
Compatibility
NoTick is designed for modded servers and supports modded entities through normal registry IDs.
Current builds:
- Fabric 1.20.1 and 1.21.1
- Forge 1.20.1
- NeoForge 1.21.1, 26.1.2, and 26.2
Use config whitelists for:
- bosses and multipart mobs
- scripted or event entities
- fake-player-style automation
- projectiles or special entities from large content mods
- any mod where distant entities must keep ticking normally
If FTB Chunks or Open Parties and Claims is installed, claimed chunks can be treated as protected areas. This is useful for farms, automation zones, and bases that should keep normal behavior while players are away.
Best Fit
NoTick is strongest on:
- large modded survival servers
- kitchensink packs with heavy passive entity load
- SMPs with many bases, farms, and dimensions
- servers where distant mobs and items create constant tick cost
- packs that need admin-controlled performance safeguards
Important Note
NoTick is intentionally performance-focused and can change behavior for far-away, unprotected entities.
If a farm or contraption must run while nobody is nearby, protect it with chunk claims, active chunk safeguards, entity whitelists, mod ID whitelists, or dimension rules.
Credits
Originally based on DoesItTick by Txni.
Maintained fork by Rique.
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
下载 NoTick
修复了 FTB Chunks 在客户端世界中执行领地查询的问题,将许可证重新授权为 LGPL-3.0-or-later,更新了打包的徽标以匹配最新的 NoTick 图标,并添加了自动化测试套件。
关于这个资源的讨论、问题反馈与使用心得
还没有讨论,来发第一帖吧
你是这个资源的作者?登录后可认领此资源。
评论 0
登录后参与评分
还没有评论,来抢沙发吧