EZTP
轻量级、对服务器友好的 Minecraft 1.12.2 传送模组
EZTP 是一款适用于 Minecraft 1.12.2 的轻量级 Forge 传送模组。它提供返回上一位置、设置家、全球出生点、安全随机传送、玩家间传送请求、冷却时间以及权限控制等功能。
亮点
- 功能齐全:
/back(返回)、家、全球出生点、安全 RTP(随机传送)以及可点击的 TPA(传送申请)请求。
- 对多人服务器友好: 仅需在专用服务器上安装该模组;玩家无需安装 EZTP 即可加入游戏。
- 生存向默认设置: 包含引导延迟、移动与伤害取消机制、独立的冷却时间以及保守的 RTP 生成策略。
- 管理简便: 支持热重载的游戏设置、Forge PermissionAPI 权限支持,以及服务器端的英文/中文本地化。
- 兼容性优先: 不使用 CoreMod、ASM、替换原版类、自定义传送门生成或需要客户端数据包。
快速开始
- 为 Minecraft
1.12.2 安装 Forge 14.23.5.2860 并使用 Java 8。
- 将 EZTP Universal JAR 文件复制到
mods 目录中。
- 启动一次游戏或服务器以生成
config/eztp.cfg 配置文件。
- 根据需要调整文档中的设置,然后运行
/eztp reload 以实现运行时安全的更改。
多人游戏: 仅在专用服务器上安装 EZTP。原版客户端和未安装 EZTP 的 Forge 客户端均可正常连接。
替换 EZTP JAR 文件前请停止游戏或服务器。在单人游戏中,JAR 文件应放在客户端的 mods 目录中,以便集成服务器能够加载它。
命令
| 命令 |
默认访问权限 |
描述 |
/back |
所有人 |
返回上次传送前的位置,或返回最后死亡的位置 |
/sethome [name] |
所有人 |
保存当前位置;若名称已存在则覆盖 |
/home [name] |
所有人 |
传送回家;如果只有一个家,可省略名称 |
/homes [page] |
所有人 |
显示可点击的分页家列表 |
/delhome [name] |
所有人 |
删除一个家;如果只有一个家,可省略名称 |
/setspawn |
管理员 |
将当前位置和朝向设置为全球出生点 |
/spawn |
所有人 |
传送到全球出生点 |
/rtp |
所有人 |
在当前维度中寻找一个安全的随机目的地 |
/tp <player> |
管理员 |
立即传送到某玩家身上;其他 /tp 形式保持原版行为 |
/tpa <player> |
所有人 |
申请传送到另一位玩家处 |
/tpahere <player> |
所有人 |
请求另一位玩家传送到你这里 |
/tpaccept [player] |
所有人 |
接受请求;别名 /tpyes |
/tpdeny [player] |
所有人 |
拒绝请求;别名 /tpno |
/tpacancel |
所有人 |
撤回当前的外出传送请求 |
/eztp reload |
管理员 |
重新加载运行时安全的配置 |
家的名称不区分大小写,并以小写形式保存。名称可包含 1–16 个 ASCII 字母、数字或下划线。
当玩家骑乘实体时,EZTP 会让玩家下马,并在下一个服务器刻仅传送玩家本体。坐骑会留在原地。遵循 Minecraft 标准骑乘关系的模组坐骑通常无需特殊处理。
传送行为
/back、/home、/spawn、/rtp、/tpa 和 /tpahere 默认拥有独立的冷却时间。设置 shareTeleportCooldowns=true 可使它们共享一个玩家全局冷却池。
- 普通玩家默认最多可以保存五个家。
- 默认延迟为 3 秒。移动或受到实际伤害会取消传送,成功传送后默认进入 30 秒冷却时间。
- 管理员默认绕过延迟、冷却时间和家的数量限制,但移动仍会取消他们的传送。
- 可选音效会在最后三秒倒计时期间播放,并在成功抵达后播放。
- 死亡、登出或维度变化会取消待处理的传送。
成功的 EZTP 玩家传送会记录其起点,而死亡则会记录死亡位置。成功的 /back 会将其自身的起点保存为下一次的上一个位置,从而可以在两个地点之间切换。该位置记录在重连和服务器重启后依然保留。自动的首次出生点和重生放置不会覆盖死亡位置。当 EZTP 的 /tp 扩展功能激活时,由原版 /tp 移动的玩家也会记录其起点。
当 back.deathOnlyOnce 设为 true 时,普通传送不再创建返回点,且每次死亡仅提供一次成功的 /back 使用机会。移动、受到伤害或另一次传送失败都不会消耗此次机会。此选项默认关闭。
全球出生点
在使用 /setspawn 之后:
- 首次登录的玩家将在自定义的全球出生点生成。
- 没有床或其他个人重生点的玩家将在此处重生。
- 由其他模组提供的床和重生点始终拥有更高优先级。
在设置自定义出生点之前,初始生成和重生放置保持原版行为。在此状态下,/spawn 使用原版主世界出生点。如果目的地后续被阻挡,EZTP 会向上搜索适合玩家的空间。
随机传送
/rtp 默认仅在主世界允许,并搜索距离世界出生点 1,000–5,000 块的范围。默认情况下,它最多尝试三个不同的区块,并在每个区块中检查多达 64 个地表位置。
搜索工作分布在服务器的多个刻(tick)中执行,因此一条命令不会连续生成大量区块。randomTeleport 类别控制维度、原点、半径、Y 轴范围、重试次数、每刻预算以及不安全方块。较高的重试次数或每刻预算可能会增加地形生成量并导致卡顿。
传送请求
- 请求默认在 60 秒后过期。
- 玩家默认最多可接收 10 个待处理的请求。
- 每位玩家仅保留其最新的发出请求。
- 当存在多个传入请求时,使用
/tpaccept <player> 或 /tpdeny <player> 来选择发起者。
- 接受、拒绝和撤回操作可通过聊天中的可点击按钮完成。
配置
主配置文件类别:
| 分类 |
用途 |
general |
默认家园名称、家园数量上限、传送延迟、伤害取消、可选共享冷却时间、备用冷却时间以及 /tp 扩展功能 |
commandCooldowns |
六种传送来源的独立冷却时间;设为 -1 则继承备用冷却时间 |
back |
/back 命令的可选单次使用行为,仅限死亡后触发 |
effects |
倒计时和到达时的音效及其音量 |
spawn |
首次加入游戏及未绑定重生点时的重生行为 |
randomTeleport |
RTP(随机传送)可使用的维度、范围、安全检查及性能预算 |
teleportRequests |
请求频率限制、请求有效期及接收请求的数量上限 |
chatDisplay |
家园列表和请求列表在聊天栏中的显示上限 |
permissions |
固定权限节点的默认权限等级 |
生成的文件记录了每项设置的默认值、有效范围以及极端数值可能带来的风险。
默认配置: 包含五个家园、3秒预热时间、每个传送来源拥有独立的30秒冷却时间,以及在移动或受到伤害时取消传送。共享冷却时间为可选设置。随机传送(RTP)会在距离世界出生点1,000至5,000格范围内搜索,最多尝试三个区块,并且每刻处理一个区块。请求采用3秒的发送节流机制、60秒的生命周期,并限制同时接收的请求数量为10个。这些默认设置旨在保留探索乐趣、战斗压力以及服务器性能。
重载配置
保存 config/eztp.cfg 后,从服务器控制台或以授权玩家身份运行以下命令:
/eztp reload
大多数设置会立即生效,包括 shareTeleportCooldowns、cancelTeleportOnDamage 和 back.deathOnlyOnce。更改共享冷却选项仅会改变现有计时器的显示方式,而不会重置它们:在共享模式下,使用最长活跃来源的计时器。已经启动的 RTP 搜索和传送请求将保留创建时捕获的参数,且活跃的冷却持续时间不会重新计算。
以下设置需要完全重启游戏或服务器:
enableTpExtension
permissions 下的默认访问级别
如果其中任何一项发生更改,重载命令会提示需要重启,并阻止在当前进程中部分应用。不支持在服务器运行时替换或重载模组 JAR 文件。
权限
默认访问级别:
EVERYONE:所有玩家
OPERATORS:仅限服务器管理员
NOBODY:默认无玩家拥有
显示完整的权限矩阵
| 权限节点 |
默认值 |
eztp.command.back |
EVERYONE |
eztp.command.home |
EVERYONE |
eztp.command.sethome |
EVERYONE |
eztp.command.delhome |
EVERYONE |
eztp.command.spawn |
EVERYONE |
eztp.command.setspawn |
OPERATORS |
eztp.command.rtp |
EVERYONE |
eztp.command.reload |
OPERATORS |
eztp.command.tp |
OPERATORS |
eztp.command.tpa |
EVERYONE |
eztp.command.tpahere |
EVERYONE |
eztp.command.tpaccept |
EVERYONE |
eztp.command.tpdeny |
EVERYONE |
eztp.command.tpacancel |
EVERYONE |
eztp.teleport.cross_dimension |
EVERYONE |
eztp.bypass.home_limit |
OPERATORS |
eztp.bypass.teleport_delay |
OPERATORS |
eztp.bypass.teleport_cooldown |
OPERATORS |
eztp.bypass.movement_cancel |
NOBODY |
兼容 Forge PermissionAPI 的权限模组可以覆盖这些默认值。节点名称是稳定的 API,不应被更改。
兼容性
- 多人游戏客户端无需安装 EZTP。
- 单人游戏需要在客户端保留 JAR 文件,以便其内置服务器能够加载 EZTP。
- 消息在服务端进行本地化;包含英文和简体中文,不支持的语言将回退到英文显示。
- EZTP 不会修改原版类、不使用 CoreMod 或 ASM,也不会创建传送门。
EZTP
Lightweight, server-friendly teleportation for Minecraft 1.12.2
EZTP is a lightweight Forge teleportation mod for Minecraft 1.12.2. It provides return-to-previous-location, homes, a global spawn, safe random teleportation, player teleport requests, cooldowns, and permission control.
Highlights
- Complete essentials:
/back, homes, global spawn, safe RTP, and clickable TPA requests.
- Server-friendly multiplayer: only the dedicated server needs the mod; players may join without EZTP.
- Survival-minded defaults: warmups, movement and damage cancellation, independent cooldowns, and conservative RTP generation.
- Easy administration: hot-reloadable gameplay settings, Forge PermissionAPI support, and server-side English/Chinese localization.
- Compatibility first: no CoreMod, ASM, vanilla class replacement, custom portal generation, or required client packets.
Quick start
- Install Forge
14.23.5.2860 for Minecraft 1.12.2 and use Java 8.
- Copy the EZTP Universal JAR into the
mods directory.
- Start the game or server once to generate
config/eztp.cfg.
- Adjust the documented settings as needed, then run
/eztp reload for runtime-safe changes.
Multiplayer: install EZTP only on the dedicated server. Vanilla clients and Forge clients without EZTP can connect normally.
Stop the game or server before replacing the EZTP JAR. In singleplayer, the JAR belongs in the client mods directory so the integrated server can load it.
Commands
| Command |
Default access |
Description |
/back |
Everyone |
Return to the location before the last teleport or to the last death location |
/sethome [name] |
Everyone |
Save the current position; an existing name is replaced |
/home [name] |
Everyone |
Teleport home; the name may be omitted when only one exists |
/homes [page] |
Everyone |
Show a clickable, paginated home list |
/delhome [name] |
Everyone |
Delete a home; the name may be omitted when only one exists |
/setspawn |
Operators |
Set the global spawn to the current position and rotation |
/spawn |
Everyone |
Teleport to the global spawn |
/rtp |
Everyone |
Find a safe random destination in the current dimension |
/tp <player> |
Operators |
Immediately teleport yourself to a player; other /tp forms remain vanilla |
/tpa <player> |
Everyone |
Ask to teleport to another player |
/tpahere <player> |
Everyone |
Ask another player to teleport to you |
/tpaccept [player] |
Everyone |
Accept a request; alias /tpyes |
/tpdeny [player] |
Everyone |
Deny a request; alias /tpno |
/tpacancel |
Everyone |
Withdraw the current outgoing request |
/eztp reload |
Operators |
Reload runtime-safe configuration |
Home names are case-insensitive and saved in lowercase. They may contain 1–16 ASCII letters, digits, or underscores.
When a player is riding an entity, EZTP dismounts the player and teleports only the player on the next server tick. The mount remains behind. Modded mounts that follow Minecraft's standard riding relationship usually need no special handling.
Teleport behavior
/back, /home, /spawn, /rtp, /tpa, and /tpahere have independent cooldowns by default. Set shareTeleportCooldowns=true to make them share one player-wide cooldown pool.
- Regular players may save up to five homes by default.
- The default delay is 3 seconds. Movement or actual damage cancels the teleport, and a successful teleport starts a 30-second cooldown by default.
- Operators bypass the delay, cooldown, and home limit by default, but movement still cancels their teleports.
- Optional sounds play during the final three countdown seconds and after a successful arrival.
- Death, logout, or a dimension change cancels a pending teleport.
Successful EZTP player teleports save their origin, while death saves the death location. A successful /back saves its own origin as the next previous location, so it can toggle between two places. The location persists across reconnects and server restarts. Automatic first-spawn and respawn placement do not overwrite a death location. When EZTP's /tp extension is active, players moved by vanilla /tp also have their origin recorded.
When back.deathOnlyOnce is true, ordinary teleports no longer create return points and each death grants one successful use of /back. Movement, damage, or another teleport failure does not consume the opportunity. This option is disabled by default.
Global spawn
After /setspawn has been used:
- First-time players spawn at the custom global spawn.
- Players without a bed or another personal respawn point respawn there.
- Beds and respawn points supplied by other mods always take priority.
Until a custom spawn is set, initial spawn and respawn placement remain vanilla. /spawn uses the vanilla Overworld spawn in this state. If a destination later becomes obstructed, EZTP searches upward for space that fits the player.
Random teleport
/rtp is allowed only in the Overworld by default and searches 1,000–5,000 blocks from world spawn. It tries at most three different chunks by default and checks up to 64 surface positions in each chunk.
Search work is spread across server ticks so one command does not generate many chunks consecutively. The randomTeleport category controls dimensions, origin, radius, Y range, retries, per-tick budget, and unsafe blocks. Large retry counts or tick budgets can increase terrain generation and lag.
Teleport requests
- Requests expire after 60 seconds by default.
- A player may receive up to 10 pending requests by default.
- Each player keeps only their latest outgoing request.
- With multiple incoming requests, use
/tpaccept <player> or /tpdeny <player> to choose the requester.
- Accept, deny, and withdraw actions are available as clickable chat buttons.
Configuration
Main configuration categories:
| Category |
Purpose |
general |
Default home name, home limit, teleport delay, damage cancellation, optional shared cooldown, fallback cooldown, and /tp extension |
commandCooldowns |
Independent cooldowns for six teleport sources; -1 inherits the fallback |
back |
Optional one-use death-only behavior for /back |
effects |
Countdown and arrival sounds and volume |
spawn |
First-join and unbound-respawn behavior |
randomTeleport |
RTP dimensions, range, safety checks, and performance budget |
teleportRequests |
Request rate limit, lifetime, and incoming limit |
chatDisplay |
Home and request list display limits |
permissions |
Default levels for fixed permission nodes |
The generated file documents each setting's default, valid range, and risks associated with extreme values.
Default profile: five homes, a 3-second warmup, a separate 30-second cooldown per teleport source, and cancellation on movement or damage. Shared cooldowns are opt-in. RTP searches 1,000–5,000 blocks from world spawn, tries at most three chunks, and processes one chunk per tick. Requests use a 3-second send throttle, a 60-second lifetime, and a limit of 10 incoming requests. These defaults preserve exploration, combat pressure, and server performance.
Reloading configuration
After saving config/eztp.cfg, run this from the server console or as an authorized player:
/eztp reload
Most settings apply immediately, including shareTeleportCooldowns, cancelTeleportOnDamage, and back.deathOnlyOnce. Changing the shared-cooldown option changes how existing timers are viewed without resetting them: shared mode uses the longest active source timer. RTP searches and teleport requests that have already started keep the parameters captured at creation, and active cooldown durations are not recalculated.
These settings require a full game or server restart:
enableTpExtension
- default access levels under
permissions
If either changes, the reload command reports that a restart is required and prevents partial application in the current process. Replacing or reloading the mod JAR while the server is running is not supported.
Permissions
Default access levels:
EVERYONE: all players
OPERATORS: server operators only
NOBODY: no players by default
Show the complete permission matrix
| Permission node |
Default |
eztp.command.back |
EVERYONE |
eztp.command.home |
EVERYONE |
eztp.command.sethome |
EVERYONE |
eztp.command.delhome |
EVERYONE |
eztp.command.spawn |
EVERYONE |
eztp.command.setspawn |
OPERATORS |
eztp.command.rtp |
EVERYONE |
eztp.command.reload |
OPERATORS |
eztp.command.tp |
OPERATORS |
eztp.command.tpa |
EVERYONE |
eztp.command.tpahere |
EVERYONE |
eztp.command.tpaccept |
EVERYONE |
eztp.command.tpdeny |
EVERYONE |
eztp.command.tpacancel |
EVERYONE |
eztp.teleport.cross_dimension |
EVERYONE |
eztp.bypass.home_limit |
OPERATORS |
eztp.bypass.teleport_delay |
OPERATORS |
eztp.bypass.teleport_cooldown |
OPERATORS |
eztp.bypass.movement_cancel |
NOBODY |
Permission mods compatible with Forge PermissionAPI may override these defaults. Node names are stable API and should not be changed.
Compatibility
- Multiplayer clients do not need EZTP installed.
- Singleplayer requires the JAR on the client so its integrated server can load EZTP.
- Messages are localized on the server. English and Simplified Chinese are included; unsupported languages fall back to English.
- EZTP does not modify vanilla classes, use a CoreMod or ASM, or create portals.
评论 0
登录后参与评分
还没有评论,来抢沙发吧