
本项目并未完全弃坑——只是在过去一年中缺乏一些关爱与维护;我计划在新的一年继续开发并修复所有遗留问题。感谢您对 ServerSigns 的持续支持 —— Exloki
ServerSigns (SVS) 允许将玩家发送和服务端发送的命令、消息和操作绑定到 Minecraft 中的告示牌及其他任何方块上。
一旦玩家点击 ServerSign,所配置的操作将按照您指定的顺序和设置依次执行。
源码:
主要功能:
- 无限制:每个 ServerSign 可绑定的命令数量不限
- 多角色:在点击告示牌时分配多种操作(甚至可以为右键/左键定义不同的命令)
- 消息:向玩家发送消息
- 广播:向整个服务器发送消息
- 玩家命令:以玩家自己在聊天栏输入命令的方式执行命令
- 服务端命令:以从服务端控制台执行命令的方式执行命令
- 延迟操作:任何操作均可设置延迟(从几秒到几个月不等)
- 循环操作:任何 ServerSign 均可转换为以指定间隔循环执行服务端命令
- 需要权限:ServerSign 可设置为需要特定权限才能使用
- 授予权限:为玩家授予临时权限以执行相关命令
- 按告示牌计费:可将经验值、货币和物品消耗绑定到 ServerSign 上
- 受保护:自动保护每个 ServerSign 及其附加的方块。
- 基础脚本:在 ServerSign 的命令中实现 if/else 和 return 语句
请注意,版本 2.6 及以上会在有 ServerSigns 开发者加入时通知您,以便我们知道是谁加入了社区,并能尽快协助您解决可能遇到的 ServerSigns 相关问题。版本 4.1 及以上还会向开发者发送一条包含当前插件版本的消息。
本插件使用了自动更新功能,它会检查最新的 ServerSigns 构建版本,并在发现新版本比当前已安装版本更新时自动下载该版本。您可以在 config.yml 中将 'check_for_updates' 设置为 false 来禁用此功能。
本插件使用了 Metrics 来收集基本的非标识性统计数据,例如您使用的 ServerSigns 数量、您的插件版本以及其他 mcstats.org 的标准数据。您可以在 config.yml 中将 'metrics_opt_out' 设置为 true 来选择退出此功能。收集的完整信息列表请参阅此处:
已知问题
- 所有版本:出生点保护会阻止非 OP 玩家使用 ServerSigns 正如 md_5 所述,此问题无法“修复”,已知的解决方案包括将 spawn-protection 设置为 0,或清除 ops.json 文件
报告 Bug / 请求功能
在报告 Bug、请求新功能或提供任何其他需要修改代码的建设性反馈时,您必须提交一个工单,以确保您的声音被听到并采取相应行动(如需要)。此后,评论区中出现的此类话题将一律不予理会。
在您提交工单之前,请确保您所请求的功能尚未实现(阅读显示 SVS 功能的所有帮助页面),或者您希望修复的 Bug 已在最新的开发版中得到解决(开发版页面上保留了滚动更新日志,可作为参考)。
提交工单时,请尽可能详尽地描述并提供相关信息。如果报告错误或缺陷,请提供所有重现问题的步骤,并附上任何相关的截图或其他文件。如果请求新功能,请尽可能详细说明,以便我们清楚了解您的建议——这样如果我们确实采纳了该建议,就能确保其完全符合您的预期。
提交工单后,请放心,我们会进行处理。我们无法保证回复或实际修改的具体时间,但会尽全力尽快解决工单。请勿:顶起已有工单、就同一问题提交多个工单、通过私信联系我们的开发人员,或在评论区内讨论工单内容。不符合上述要求的工单可能会被直接拒绝且不予说明。

This project has not been abandoned completely - it's just been lacking some love & care for the past year; I plan to continue development and fix any outstanding issues in the new year. Thank you for your continued support of ServerSigns - Exloki
ServerSigns (SVS) provides the ability to bind player-dispatched and server-disptached commands, messages and actions to signs and every other block in Minecraft.
As soon as a player clicks on a ServerSign, the configured actions are executed in the order and with the settings you specified.
Source:
Main Features:
- No limit: Unlimited commands per ServerSign
- Multi-role: Assign a variety of actions whenever a sign is clicked (even define different commands for right/left clicks)
- Messages: Send messages to the player
- Broadcasts: Send messages to the whole server
- Player commands: Executes commands as if the player typed it in chat
- Server commands: Executes commands as if it was executed from the server console
- Delayed actions: Any action can be delayed (from seconds to months)
- Looped actions: Any ServerSign can be converted to loop server commands with defined intervals
- Require permissions: ServerSigns can be set up to require permissions to use
- Grant permissions: Grants players temporary permissions to execute the commands
- Per-sign costs: Bind exp, money, and item costs to ServerSigns
- Protected: Automatically protects every ServerSign and any attached blocks.
- Basic scripting: Implement if/else and return statements in commands on ServerSigns
Please note that version 2.6 and above will notify you when a ServerSigns developer joins, this is so you're aware of who we are when we join, and we can help you with any issues you may be having with ServerSigns as quickly as possible. Version 4.1 and above will also send the developer a message stating the current plugin version.
This plugin utilizes an auto-updating feature that will check for the latest ServerSigns build and automatically download that build if it is newer than the currently installed one. This can be disabled by setting 'check_for_updates' to false in the config.yml
This plugin uses Metrics to gather basic non-identifiable statistical data such as the number of ServerSigns you are using, your plugin version, and other standard mcstats.org data. You can opt-out of this feature by setting 'metrics_opt_out' to true in the config.yml. A full list of gathered information can be found here:
Known bugs
- ALL VERSIONS: Spawn protection prevents non-ops using ServerSigns This issue cannot be 'fixed', as stated by md_5 - known sollutions include setting spawn-protection to 0, or clearing ops.json
Reporting Bugs / Requesting Features
When reporting bugs, requesting features, or providing any other constructive feedback that will require code alterations you must submit a ticket to have your voice heard and action taken (if required). Any topics of this nature that arise in the comments section will henceforth be ignored.
Before you raise a ticket, you need to make sure that the feature you are requesting isn't already implemented (read all of the help pages which show SVS features), or the bug you want fixed hasn't already been resolved in the latest development build (a rolling change log is kept on the development build page, use this for reference)
When submitting a ticket, please be as descriptive and informative as possible. If reporting a bug or flaw, then show all the steps required to reproduce the problem, also attach any and all related screenshots or other files to the ticket. If requesting a new feature, then please be as detailed as possible so we have a very clear idea of what it is you're suggesting - that way if we do implement your suggestion, this ensures it is exactly as you want it to be.
Once you have submitted a ticket, rest assured that it will be handled. We do not give a definite time frame for replies or actual alterations, but we try our absolute best to get tickets resolved as soon as possible. Please do not: bump tickets, raise multiple tickets for the same issue, send PMs to our developers, or discuss the ticket in the comments section. Tickets that do not meet the expectations outlined here will likely be declined without comment.
评论 0
登录后参与评分
还没有评论,来抢沙发吧