GlowstoneMC/Glowstone

Command blocks

Open

#338 建立於 2016年8月16日

在 GitHub 查看
 (6 留言) (1 反應) (0 負責人)Java (1,825 star) (278 fork)batch import
Category: gameplay featureCategory: server featureType: storyhelp wanted

描述

I am currently working on Command Blocks (with >1.8 functionality). This is to track the progress of these branches: API & Server implementation.

To-Do:

  • Update the Command block API for the new functions
  • Place the new command blocks
  • Save TileEntity and MaterialData for command blocks
  • Incomplete Open command blocks when clicked
    • Save data when closed
    • Fix a bug with duplicate interaction packets (opening the command block twice)
    • Incomplete Use op permission levels
      • Set permission level when joining the server (EntityStatus)
      • Add permission level to configuration
  • Make command blocks reactive to redstone
  • Execute commands on behalf of the block
  • Chain command blocks

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

貢獻者指南

技術棧
java
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
JavaMinecraft server internalsGlowstone APICommand block mechanics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Examine the linked branches (command blocks api and command blocks) to assess current progress. Look at recent commits and comments to see if any subtasks have been completed or if the issue is still valid. Familiarize yourself with the Glowstone codebase, especially how other block entities are implemented. Since the issue is a large tracking task, consider asking maintainers for a specific subtask that needs help.