Ultimate PinataParty
Ultimate PinataParty 将服务器投票转化为一个共享事件,整个社区朝着同一个目标努力,同时玩家之间竞争最高贡献者。
每次被接受的击打都会推进固定的会话目标。玩家可以通过Boss栏和物品栏菜单跟踪事件进度、比较各自的贡献,并根据参与方式获得奖励,而不是依赖单一的最终奖品。
带有公平竞争的社区活动
- 每个事件会话都有固定的击打目标。
- 仅基于被接受的击打进行实时贡献排名。
- 可配置的击打冷却时间。
- 每位玩家的最高贡献上限,防止单人控制整个事件。
- 社区奖励所需的最低参与要求。
- 可配置的事件持续时间和最大同时事件数量。
- 允许的击打物品列表与禁止的击打物品列表。
五个奖励阶段
奖励分为独立的组别:
- 每次被接受的击打。
- 最后一次击打。
- 符合条件的参与。
- 最高贡献者。
- 幸运贡献者。
幸运贡献者通过以被接受的击打作为加权票券来选出。更多的参与能提高中奖几率,但不保证结果。
每个奖励组支持 ALL、INDEPENDENT 和 WEIGHTED_ONE 选择模式。条目可以定义自己的概率、权重以及包含玩家、击打次数、排名、总数和会话占位符的控制台命令。
MCVote 与 NuVotifier
Ultimate PinataParty 可以从以下来源接收事件进度:
- MCVote。
- NuVotifier。
- 管理命令。
AUTO 模式优先使用 MCVote,当 MCVote 不可用时回退到 NuVotifier。同一时间只启用一个投票监听器,防止同一张投票被重复计算。
事件展示
- 可配置用作皮纳塔的活体实体。
- 显示当前击打数和所需击打数的共享 Boss 栏。
- 击打粒子效果与音效。
- 可配置的事件完成烟花效果。
- 用于查看状态、投票进度、连击数和排名的玩家菜单。
- 用于常见事件控制的管理专用菜单。
菜单位置独立于 Java 行为,可在 menu/main.yml 和 menu/admin.yml 中编辑。
MythicMobs、BetterModel 与 ModelEngine
事件实体及其视觉模型是独立配置的。这使得设置更加灵活,无需将事件进度或奖励转移到其他插件中:
- Ultimate PinataParty 控制命中、参与情况、进度、奖励、过期和清理。
- MythicMobs 可以提供实体,并在每个事件阶段运行自定义技能。
- BetterModel 或 ModelEngine 可以提供视觉模型及其动画。
实体引用接受 vanilla:<entity> 和 mythicmobs:<mob>。模型引用接受 none、bettermodel:<model> 和 modelengine:<model>。
event:
appearance:
entity-source: 'mythicmobs:UltimatePartyPinata'
model-source: 'modelengine:party_pinata'
fallback-on-error: true
fallback-entity-source: 'vanilla:llama'
cleanup-delay-ticks: 30
animations:
spawn: spawn
hit: hit
complete: break
expire: despawn
mythic-signals:
spawn: PINATASPAWN
hit: PINATAHIT
complete: PINATACOMPLETE
expire: PINATAEXPIRE
生命周期钩子
当所选的模型提供者支持时,Ultimate PinataParty 会播放配置的 spawn(生成)、hit(命中)、complete(完成)和 expire(过期)动画。MythicMobs 实体也会收到匹配的 PINATASPAWN、PINATAHIT、PINATACOMPLETE 和 PINATAEXPIRE 信号,允许服务器管理员附加粒子效果、声音、机制和其他 MythicMobs 技能。命中和完成技能可以使用负责的玩家作为触发器。
选择一个模型所有者
有两种支持的设置:
- 推荐: 在
model-source 中选择 bettermodel:<model> 或 modelengine:<model>。Ultimate PinataParty 将附加模型并控制其生命周期动画。不要同时从 MythicMobs 生物中附加该模型。
- 高级: 使用
model-source: 'none',让 MythicMobs 生物拥有其 Model: 配置和 state{} 技能。生命周期信号仍然可用于更改状态。
对同一生物使用这两种方法会导致模型被附加两次。请选择一个所有者并将责任保留在一个配置中。
安全回退与诊断
启用 fallback-on-error 后,如果缺少可选插件、生物 ID 无效或模型不可用,则会回退到 fallback-entity-source,以便事件仍可正常使用。/pinataadmin providers 报告当前可用的集成。自定义模型仍需要安装相应的资源包并将其分发给玩家。
语言
包含英语和西班牙语。选定的区域设置控制聊天消息、物品栏标题、物品名称和描述,而无需更改任何菜单布局。
plugins/UltimatePinataParty/
|-- config.yml
|-- ultimate-pinata-party.db
|-- languages/
| |-- en_US.yml
| `-- es_ES.yml
`-- menu/
|-- main.yml
`-- admin.yml
要求
| 要求 |
用途 |
| Paper 1.21.x |
服务器平台 |
| Java 21 |
运行环境 |
MCVote、NuVotifier 和 PlaceholderAPI 为可选集成。
命令
| 命令 |
描述 |
/pinata |
打开事件面板。 |
/pinata top |
打开面板并查看当前贡献者。 |
/pinataadmin |
打开管理面板。 |
/pinataadmin spawn |
在默认位置启动事件。 |
/pinataadmin stop |
停止所有正在运行的事件且不发放奖励。 |
/pinataadmin location set <id> |
保存当前位置。 |
/pinataadmin location remove <id> |
移除已保存的位置。 |
/pinataadmin location list |
列出已保存的位置。 |
/pinataadmin votes set <amount> |
设置本地投票进度。 |
/pinataadmin reload |
验证并重新加载用户文件。 |
/pinataadmin validate |
验证用户文件但不应用更改。 |
PlaceholderAPI
%ultimatepinataparty_votes%
%ultimatepinataparty_vote_goal%
%ultimatepinataparty_votes_left%
%ultimatepinataparty_active%
%ultimatepinataparty_hits%
%ultimatepinataparty_required_hits%
%ultimatepinataparty_player_hits%
%ultimatepinataparty_player_rank%
%ultimatepinataparty_vote_streak%
支持
在报告问题时,请提供 Paper 和 Ultimate PinataParty 的版本号、所选的投票源、已安装的投票集成插件,以及完整的控制台错误信息。
Discord:
Ultimate PinataParty
Ultimate PinataParty turns server votes into a shared event where the whole community works toward one goal while players compete for the top contribution.
Each accepted hit advances a fixed session target. Players can follow the event through a boss bar and inventory menu, compare their contribution, and earn rewards based on how they participated instead of relying on a single final prize.
Community events with fair competition
- Fixed hit target for every event session.
- Live contribution ranking based only on accepted hits.
- Configurable cooldown between hits.
- Maximum contribution per player to prevent one person from controlling the event.
- Minimum participation requirement for community rewards.
- Configurable event duration and maximum number of simultaneous events.
- Allowed and blocked hit-item lists.
Five reward stages
Rewards are separated into independent groups:
- Per accepted hit.
- Final hit.
- Qualified participation.
- Top contributor.
- Lucky contributor.
The lucky contributor is selected using accepted hits as weighted tickets. More participation provides a better chance without guaranteeing the result.
Each reward group supports ALL, INDEPENDENT, and WEIGHTED_ONE selection modes. Entries can define their own chance, weight, and console commands with player, hit, rank, total, and session placeholders.
MCVote and NuVotifier
Ultimate PinataParty can receive event progress from:
- MCVote.
- NuVotifier.
- Administrative commands.
AUTO mode prefers MCVote and falls back to NuVotifier when MCVote is unavailable. Only one vote listener is enabled at a time, preventing the same vote from being counted twice.
Event presentation
- Configurable living entity used as the pinata.
- Shared boss bar with current and required hits.
- Hit particles and sounds.
- Configurable completion fireworks.
- Player menu for status, voting progress, streak, and ranking.
- Separate administrative menu for common event controls.
Menu positions remain separate from Java behavior and can be edited in menu/main.yml and menu/admin.yml.
MythicMobs, BetterModel, and ModelEngine
The event entity and its visual model are configured independently. This keeps the setup flexible without moving event progress or rewards into another plugin:
- Ultimate PinataParty controls hits, participation, progress, rewards, expiration, and cleanup.
- MythicMobs can provide the living entity and run custom skills at each event stage.
- BetterModel or ModelEngine can provide the visual model and its animations.
Entity references accept vanilla:<entity> and mythicmobs:<mob>. Model references accept none, bettermodel:<model>, and modelengine:<model>.
event:
appearance:
entity-source: 'mythicmobs:UltimatePartyPinata'
model-source: 'modelengine:party_pinata'
fallback-on-error: true
fallback-entity-source: 'vanilla:llama'
cleanup-delay-ticks: 30
animations:
spawn: spawn
hit: hit
complete: break
expire: despawn
mythic-signals:
spawn: PINATASPAWN
hit: PINATAHIT
complete: PINATACOMPLETE
expire: PINATAEXPIRE
Lifecycle hooks
Ultimate PinataParty plays the configured spawn, hit, complete, and expire animations when the selected model provider supports them. A MythicMobs entity also receives the matching PINATASPAWN, PINATAHIT, PINATACOMPLETE, and PINATAEXPIRE signals, allowing server owners to attach particles, sounds, mechanics, and other MythicMobs skills. Hit and completion skills can use the responsible player as their trigger.
Choose one model owner
There are two supported setups:
- Recommended: select
bettermodel:<model> or modelengine:<model> in model-source. Ultimate PinataParty attaches the model and controls its lifecycle animations. Do not also attach that model from the MythicMobs mob.
- Advanced: use
model-source: 'none' and let the MythicMobs mob own its Model: configuration and state{} skills. The lifecycle signals remain available for changing states.
Using both methods for the same mob can attach the model twice. Pick one owner and keep that responsibility in one configuration.
Safe fallback and diagnostics
When fallback-on-error is enabled, a missing optional plugin, invalid mob ID, or unavailable model can fall back to fallback-entity-source so the event remains usable. /pinataadmin providers reports which integrations are currently available. Custom models still require the corresponding resource pack to be installed and delivered to players.
Languages
English and Spanish are included. The selected locale controls chat messages, inventory titles, item names, and lore without requiring changes to every menu layout.
plugins/UltimatePinataParty/
|-- config.yml
|-- ultimate-pinata-party.db
|-- languages/
| |-- en_US.yml
| `-- es_ES.yml
`-- menu/
|-- main.yml
`-- admin.yml
Requirements
| Requirement |
Purpose |
| Paper 1.21.x |
Server platform |
| Java 21 |
Runtime |
MCVote, NuVotifier, and PlaceholderAPI are optional integrations.
Commands
| Command |
Description |
/pinata |
Open the event panel. |
/pinata top |
Open the panel and view current contributors. |
/pinataadmin |
Open the administration panel. |
/pinataadmin spawn |
Start an event at the default location. |
/pinataadmin stop |
Stop all active events without rewards. |
/pinataadmin location set <id> |
Save the current position. |
/pinataadmin location remove <id> |
Remove a saved position. |
/pinataadmin location list |
List saved positions. |
/pinataadmin votes set <amount> |
Set local vote progress. |
/pinataadmin reload |
Validate and reload user files. |
/pinataadmin validate |
Validate user files without applying them. |
PlaceholderAPI
%ultimatepinataparty_votes%
%ultimatepinataparty_vote_goal%
%ultimatepinataparty_votes_left%
%ultimatepinataparty_active%
%ultimatepinataparty_hits%
%ultimatepinataparty_required_hits%
%ultimatepinataparty_player_hits%
%ultimatepinataparty_player_rank%
%ultimatepinataparty_vote_streak%
Support
When reporting a problem, include the Paper and Ultimate PinataParty versions, the selected vote source, installed vote integration, and the complete console error.
Discord:
评论 0
登录后参与评分
还没有评论,来抢沙发吧