RankCapes
RankCapes 专为希望为玩家提供更多内容的服务器而设计。这是一款有趣的美观模组,允许服务器根据赋予玩家的权限向其发放披风。RankCapes 并不局限于捐赠或贡献者;任何人都可以获得披风,因为任何人都可以被授予权限。RankCapes 易于使用,实现了类似资源包的“披风包”,可以轻松地来回切换。
官网 - 维基 - 客户端模组
Bukkit(开发版)构建状态:
功能:
- 为服务器玩家制作专属披风。
- 每个玩家可拥有多个披风。
- 支持动画和高清披风。
- 基于动作触发的动画披风。
- 类似资源包的披风包,便于轻松切换。
- 基于 Bukkit 权限的披风访问系统。
工作原理
在服务器上有一个 披风包,其中包含所有纹理以及一个将图像与披风名称关联的文件。当安装了 RankCapes 模组的客户端连接到服务器时,他们可以在披风更改 GUI 中将披风切换为他们拥有权限的任何披风。所有其他安装了该模组的玩家都可以看到他们的披风以及其他玩家的披风。
权限
通过以下权限节点授予披风:rankcapes.cape.use.$CAPE_NAME。
命令
RankCapes 只有一个命令,仅用于调试目的。
mycape - 用于调试,告知发送者其当前持有的披风。
客户端模组
玩家需要安装 RankCapes 客户端模组才能看到自己的披风。插件会发送披风包,并告知客户端它可以访问哪些披风以及其他玩家的披风。目前仅提供 Minecraft Forge 版本。安装和使用非常简单。
在此处下载 此处。
设置
设置通常很简单。请参阅 维基 以获取详细信息和文档。
支持
如果您在使用 RankCapes 插件或模组时遇到任何问题,您可以在 GitHub 上创建 Issue。
版本控制
RankCapes 使用带有额外 BUILD 版本的语义化版本控制 2.0.0系统。每当进行不兼容的 API 更改(包括 SERVER<->CLIENT 协议)时,MAJOR 版本号加 1。每当 Minecraft 更新时,MINOR 版本号加 1。每当进行向后兼容的更改时,PATCH/REVISION 版本号加 1。此外,每当 MAJOR 或 MINOR 版本号增加时,PATCH/REVISION 版本号重置为 0。每次 Travis 执行构建时,BUILD 版本号加 1。
复杂吗?也许吧。只需记住,仅使用具有相同 MAJOR.MINOR 版本的服务器和客户端版本即可。
RankCapes
RankCapes was made for servers that would like to offer something more to their players. It is a fun aesthetic mod that allows servers to give their players capes based on permissions given to them. RankCapes is not restricted to donating or contributing players, though; anyone can be given a cape, as anyone can be given a permission. Easy to use, RankCapes implements Cape Packs that are like Resource Packs and can be swapped back and forth easily.
Website - Wiki - Client Mod
Bukkit (bleeding edge) build status:
Features:
- Make you own capes for server players.
- Multiple capes per player.
- Animated and HD capes.
- Movement-triggered Animated capes.
- Cape Packs that are similar to Resource Packs for easy swapping.
- Bukkit permission-based cape access system.
How it Works
On the server there is a Cape Pack that contains all the textures as well as a file that associates images and cape names. When clients with the RankCapes mod installed connect to the server, they can change their cape to whatever they have permissions for in the cape change GUI. All other players with the mod installed can see theirs, and other player's capes.
Permissions
Capes are given with this permission node: rankcapes.cape.use.$CAPE_NAME.
Commands
RankCapes has one command, it's there for debug purposes only.
mycape - Used for debug, tells the sender what cape it has.
Client Mod
The RankCapes Client mod is required for the player to see their cape. The plugin sends the cape pack and tells the client which capes it has access to, as well as the other players' capes. Currently there is only a Minecraft Forge version available. Installation and use is simple.
Download it here.
Setup
Setup is generally simple. See the wiki for details and documentation.
Support
If you have any problem with the RankCapes plugin or mod, you may create an issue on GitHub.
Versioning
RankCapes uses the Semantic Versioning 2.0.0 system with an added BUILD version. Every time an incompatible API change is made, including SERVER<->CLIENT protocol, the MAJOR version is incremented. Every time Minecraft is updated, the MINOR version is incremented. Every time a backwards-compatible change is made, the PATCH/REVISION version is incremented. Also, whenever the MAJOR or MINOR version is incremented, the PATCH/REVISION version is reset to 0. Every time Travis does a build, the BUILD version increments.
Complicated? Maybe. Just remember to only use server and client versions that have the same MAJOR.MINOR versions.
评论 0
登录后参与评分
还没有评论,来抢沙发吧