文件:Mojang錯誤追蹤器指導方針和常見問題解答

出自Minecraft基岩版开发Wiki

指導方針[編輯]

Mojang錯誤追蹤器（也被暱稱為Mojira）是回報、記錄和追蹤Minecraft和其他由Mojang Studios建立的遊戲中的所有錯誤的平台。在建立錯誤回報或參與錯誤追蹤器之前，請仔細完整地閱讀本指導方針。

如果您在回報錯誤方面需要其他幫助或對錯誤追蹤器有任何疑問，請隨時造訪我們的官方Minecraft社交渠道或造訪以下社群連結之一詢問社群中的其他玩家。

什麼可以在錯誤追蹤器上回報，什麼不能？[編輯]

對於您的錯誤回報，我們僅當它是真正關於一個錯誤時才會接受。錯誤是指遊戲中由於遊戲程式碼的問題而未按應有的方式執行的某些行為。因此，它應該是可復現的，而且不是由遊戲之外的環境引起的。讓錯誤追蹤器的關注點位於真正的錯誤上有助於Mojang Studios更快地解決它們。

以下型別的問題並不是錯誤，並且不允許出現在錯誤追蹤器上：

  • Minecraft帳戶或付款問題
    如果您無法存取您的Minecraft帳戶，或者您有付款或購買問題（包括Realm和市集），請聯繫Minecraft支援。我們無法在錯誤追蹤器上對此提供幫助。
  • 建議和功能請求
    要為Minecraft推薦新功能或發布建議，請在Minecraft官方意見回饋站點上進行操作或造訪社群連結的其中一個。
  • 在嗡嗡蜂群更新之前引入的等稱問題
    要回報等稱問題（遊戲不同的版之間的差異），請在回報之前先檢視官方等稱問題指導方針。如果您的回報並不符合裡面所述的所有準則，則它應該提交至Minecraft官方意見回饋站點。
  • Minecraft：Java版和Minecraft啟動器的翻譯問題
    這些翻譯的問題需要在Minecraft或Minecraft啟動器的Crowdin專案中提出，因為遊戲的翻譯是由Minecraft社群的成員在Crowdin完成的。
    錯誤追蹤器允許提交原始的「English (US)」語言的問題，因為它們沒有包含在社群翻譯過程中。
  • 一般的網路連接問題（Realm、市集）和身分認證問題
    這些問題通常不在遊戲程式碼的控制範圍內，通常是由於伺服器維護、停機或本地網路組態造成的。如果問題仍然存在，請考慮詢問社群（請參閱常見問題解答）。

如何有效地使用錯誤追蹤器的搜尋功能[編輯]

在每次回報錯誤之前，都請先搜尋現有的回報。以下是有關搜尋現有錯誤回報的一些技巧：

  • 儘量少用關鍵字。搜尋引擎只會找到包含全部所查詢單詞的錯誤回報。例如，請搜尋「squid suffocate」而不是「Squid will frequently suffocate for no reason when swimming around in a river」。
  • 確認所有單詞都拼寫正確。
  • 嘗試使用同義詞分別進行多次搜尋。例如，「workstation」、「job site」和「profession block」。
  • 將您的搜尋限制在您要向其回報錯誤的專案裡。目前所有的專案及其描述的列表寫在了一般錯誤準則段落中。
  • 按建立日期對搜尋結果進行排序，使最新的錯誤回報排在頂部。依次檢查以檢視它們中是否有回報描述了您的問題。
  • 如果有太多錯誤回報以至於無法很輕鬆地進行檢查，您可以變更排序標準（例如，按投票排序）、進一步最佳化搜尋查詢或排除已解決的錯誤回報。但請記住，您正在搜尋的問題可能已存在於已解決的回報中。

如果您發現您的問題已被回報，請檢視回報的Resolution以確定下一步要採取的步驟。

解決狀態[編輯]

  • Unresolved – 該錯誤尚未修復。在這種情況下，請投票支持該錯誤回報。這有助於我們衡量有多少玩家受到該錯誤的影響。如果您認為還需要補充一些內容，您還可以在該錯誤回報中加入更多資訊。
  • Awaiting Response – 請檢視「Comments」部分以得知該錯誤回報中缺少的內容。您可以在評論中提供此缺失資訊以重新開啟該回報。
  • Duplicate – 請點擊「Issue Links」部分中指向其父回報的連結。您的問題已經在該父回報處追蹤。
  • Fixed – 請找到「Fix version」部分。這是Mojang Studios修復該錯誤的版本。如果您使用的是比該版本更新的版本，且查找不到關於您的問題的另一個更新的回報，則請建立一個新的錯誤回報。如果修復版本是「Future version」，則該錯誤將在尚未向公眾發布的版本中修復。
  • 其他解決方案 – 請仔細閱讀評論（如果有的話），以了解它為什麼已被解決。

貢獻的準則[編輯]

如果您發現存在一個有關您問題的錯誤回報，您可以透過評論或附加檔案（例如，畫面截圖或螢幕錄製）來加入更多資訊。不管您正在以何種方式為錯誤追蹤器做出貢獻，都請遵循以下準則：

一般[編輯]

重要：錯誤追蹤器是一個公共場合。在任何情況下都請勿共享您的密碼、電子郵件位址、交易ID或其他個人資訊。

  • 請勿以任何方式冒充他人，例如偽裝您的使用者名稱或顯示名稱。

評論[編輯]

  • 如果您沒有任何新內容要加入，請勿對某個錯誤回報發表評論。
  • 請勿加入如「me too」或類似於除了說明您遇到了該錯誤之外沒有任何進一步的資訊的評論。
  • 請保持所有評論僅與錯誤本身的資訊相關。錯誤追蹤器不接受對Mojang Studios、其員工或其他任何人的投訴和批評。
  • 錯誤追蹤器上不允許出現任何形式的褻瀆和少兒不宜的內容。
  • 如果您想發起有關錯誤的討論或需要舉報某人，請在錯誤追蹤器之外進行討論（請參閱常見問題解答），不要直接在錯誤追蹤器上發表評論。
  • 請勿模仿或使用只有helper或moderator才能使用的預先格式化過的回覆。
附件
  • 除非顯示的內容與錯誤回報中已經包含的內容有明顯不同，否則請勿附加新的畫面截圖。
  • 將檔案附加到現有錯誤回報時，請發布一個能充當上下文的支援性評論。
  • 在評論（或錯誤回報的描述）中內嵌圖片時，請確保圖片大小不要太大。

要內嵌圖片，請在文字編輯模式下使用以下標記： 

!picture_name.png|thumbnail!

重要：在發布附件之前，請從附件中移除所有個人資訊（電子郵件位址、玩家代號、Realm連結等）。

一般錯誤回報的準則[編輯]

在建立錯誤回報時，請謹記以下準則：

重要：如果您的錯誤回報包含您不想公開可見的敏感資訊，請將回報的「Security Level」設定為「Private」並明確表示您不希望其公開。

  • 如果您發現了該錯誤可能被惡意利用或存在安全問題，請將錯誤回報的「Security Level」設定為「Private」，以便只有您、Mojang Studios員工和錯誤追蹤器的moderator才能檢視您的錯誤回報。
  • 在建立錯誤回報之前，請花些時間檢查是否其他人已經回報了該錯誤。請參閱上面有關有效使用搜尋的技巧。
  • 我們只接受英文書寫的錯誤回報；請不要用其他語言建立錯誤回報。
  • 請只在每個錯誤回報中回報一個問題。如果您的錯誤回報包含多個錯誤，我們將不會接受您的錯誤回報。
  • 如果您正在使用任何遊戲模組或第三方工具，請在回報之前檢查該問題是否在完全未修改的Minecraft環境中依舊存在。如果不再存在，請將錯誤回報給遊戲模組創作者，而不是Mojang Studios。
    • 這包括第三方伺服器端軟件，例如Spigot或Paper。
    • OptiFine在任何情況下都被認為是一個遊戲模組。
    • 使用第三方工具開啟過的世界也將不受支援。
    • 如果您在大型多人伺服器（如Hypixel或The Hive）上遇到問題，請在建立錯誤回報之前先聯繫伺服器的工作人員。這些型別的伺服器通常執行著Mojang Studios不支援的修改過的伺服器端軟件。
  • 請您只有在確定該錯誤在最新版本的遊戲中仍然存在時才進行回報。我們不接受除最新版本和最新開發版本之外的其他任何版本的錯誤回報。
  • 請將問題回報給正確的專案：
  • 「Labels」是供helper或moderator用於幫助組織錯誤回報的欄位。請僅使用現存的標籤，不要建立新標籤。有關標籤如何工作的更多資訊，請參閱我們的常見問題解答。
  • 在建立錯誤回報後，請注意相關電子郵件或定期檢查錯誤回報以取得更新或潛在的進一步診詢。
  • 也請謹記各個專案特定的準則。

如何寫出有幫助的錯誤回報[編輯]

為了幫助確保您的錯誤回報有效，強烈建議您遵循以下準則：

  • 請寫一個簡潔的摘要，使其清楚地說明問題。避免使用諸如「Help!」、「It doesn't work」、「It’s broken」或「There’s a bug」之類的通用陳述式，而是使用簡短的短語來準確地總結您的問題。嘗試思考一下您應該搜尋什麼才能找到這個問題對寫清問題的摘要很有幫助。
  • 請在文字中包含能夠復現問題的精確步驟。寫下您到底做了什麼導致了問題出現。如果您不確定，請嘗試在一個測試世界中復現該錯誤。對步驟使用數字進行編號，以便其他人可以輕鬆遵循這些步驟來復現您的問題。
  • 列出步驟後，請清楚地說明最後會發生了什麼，以及您認為應該發生什麼。
  • 請在文字中包含發生問題時出現的任何訊息（例如，錯誤訊息）的確切文字。
  • 請將畫面截圖附加到回報中以便更清楚地展示問題。如果條件允許，您也可以附上一個簡短的影片。在某些情況下，提供世界存檔（作為ZIP檔案）也可能對我們是很有意義的。
  • 如果附件檔案太大，請將其上傳到其他地方並錯誤回報的描述中連結到它或者是將其壓縮成一個較小的壓縮檔並附加在回報中。
  • 如果您的錯誤與某個特定世界相關，例如世界生成、傳送門傳送、生態域或結構問題，請確保在文字中包含種子碼和所有相關座標。
  • 不要使用過多的格式（粗體、全大寫、大文字、多個空行等）。
  • 如果您知道您正在回報的遊戲行為在某些情形下被當做了特性，請在錯誤回報的描述中提及這件事。透過這種方式，開發人員可以決定是要保留該行為還是為其加入相應的替代行為。
  • 不要急躁。請仔細閱讀您的錯誤回報，以確保您沒有遺漏任何內容並且所有內容都得到了清楚的解釋。

特定於專案的準則[編輯]

Minecraft: Java Edition[編輯]

  • 如欲回報崩潰問題，請將崩潰回報附加到錯誤回報中。您可以在.minecraft資料資料夾的「crash-reports」子資料夾中找到崩潰回報。如果沒有相關的崩潰回報，請附上啟動器記錄。
  • 如果您想建立一個關於伺服器端效能問題的錯誤回報，請在回報時包含除錯分析檔案。您可以使用/debug來建立它們。
  • 如果您想建立一個有關用戶端效能問題的錯誤回報，請提供有關您的系統規格和有關該效能問題發生情況的詳細資訊。通常不接受關於一般效能問題的錯誤回報（例如「Minecraft的FPS總是很低」）。

Minecraft (Bedrock) 和Minecraft Dungeons[編輯]

  • 請始終明確地指定您正在使用的裝置（平台）。
  • 崩潰記錄會被自動收集並回報給Mojang Studios。所以請您只在認為您能提供復現該崩潰的步驟列表時才回報崩潰問題。

Minecraft Realms[編輯]

  • 請確保Affected Version和Platform相匹配。
  • 請在Environment欄位中指定您正在使用的裝置。
  • 請指定您是否是Realm所有者。
  • 您也可以搜尋對應的主專案（MC或MCPE）以尋找既有的錯誤回報。
  • 如果您無法連接到以前能正常工作的Realm，請檢查官方Mojang Status以檢查是否存任何定期維護或其他連接問題。

範例模板[編輯]

這是一個指導您如何格式化新的錯誤回報的範例；您可以隨意複製和粘貼這個模板： 

[在此简要描述漏洞]

Steps to Reproduce:

  [第一步]
  [第二步]
  [第三步]


Observed Results:
[描述发生了什么]

Expected Results:
[描述应该发生什么]

Screenshots/Videos:
[可选：附加图片或简短视频]

Notes:
[您可以提供的有关该漏洞的任何进一步的信息，例如对您文中包含的任何附件进行说明，描述该漏洞何时开始发生，您如何对该漏洞进行的测试，显示的消息（例如，错误消息），以及该漏洞如何影响的游戏玩法。]
範例錯誤回報

以下是一些質量優異的錯誤回報，您可以將其用作範例：

我在哪裡可以檢視或提交錯誤？[編輯]

想要提交一個錯誤或檢視一個問題的狀態，請造訪下面列出的錯誤追蹤資源之一。如欲提交問題，請先使用搜尋功能以確保其他人尚未提交過相同的問題。

想要在我們的錯誤追蹤器中提交錯誤回報，您首先需要建立一個錯誤追蹤器帳戶。

注意：如果您點擊一個錯誤追蹤器並看到頁面顯示「No issues were found to match your search」，請在左上角定位到Open Issues，然後點擊Switch filter旁邊的下箭頭。然後點擊其中一個選項來切換目前的問題過濾器。

Minecraft: Java版（PC/Mac）

Minecraft：Java版啟動器

Minecraft Realms

適用於移動裝置（iOS、Android等）的Minecraft

適用於Windows的Minecraft

適用於Xbox One的Minecraft

適用於PS4的Minecraft

Minecraft：Wii U版

適用於Nintendo Switch的Minecraft

常見問題解答[編輯]

What are 「Labels」 and how should I use them?[編輯]

Bug reports are labeled with certain keywords to group them together to make them easier to find. A label can be any word or phrase if it doesn’t contain a space. There are no limits to how many labels a bug report can have.

The 「Labels」 field is for use by helpers or moderators to help organize bug reports. Don’t create new labels and only use presently existing labels. There are certain rules which labels should follow:

  • If something has an ID in the game (like blocks, entities, and items), use that ID without the 「minecraft:」 prefix as the label (e.g., 「glowstone_dust」 or 「zombie_villager」)
  • Prefix the label with a slash (「/」) for commands only (e.g., 「/gamerule」)
  • Use the 「ing」 suffix for verbs (e.g., 「breeding」 or 「fishing」)
  • No plurals unless it’s the actual name of the element (e.g., 「statistics」)
  • For everything else, connect words with a dash (e.g., 「stronghold-portal」)

Why can’t I log in to the Mojang bug tracker?[編輯]

This is most likely to be a result of one of the following scenarios:

  • You have not created a JIRA account
    You will need to create a separate JIRA account to use the Mojang bug tracker – you cannot log in with your Microsoft or Mojang account.
  • Your username may have changed
    You need to log in with your current JIRA username, not your email address. Please make sure usernames do not contain any personal or contact information. If you have forgotten your login details or think they have been changed by an administrator, you may wish to use the 「Can’t access your account?」 link on the login page for help accessing your account.
  • Your account may have been restricted
    User accounts may be restricted from accessing the bug tracker if they do not adhere to the Community Standards, or if users do not follow the bug tracker guidelines and direction from Mojang staff, moderators, and helpers.

What account do I need to log in with to use the bug tracker?[編輯]

The bug tracker uses a separate account system than Minecraft. You need to create a separate account that is used only for the bug tracker. You can do that here: Sign up for a bug tracker account.

Why do I need to specify my 「Full name」 when I sign up for an account?[編輯]

You do not need to sign up with your real name. The Full name field can be your 「Display name」. You can use anything you want, as long as you don’t use inappropriate language or try to impersonate a moderator, helper, or someone else.

Now that I have reported my bug, what should I do?[編輯]

Thank you! You should watch for related emails or regularly check the bug report for updates or potential further inquiries. If there are any questions by a helper or moderator in a comment, please answer them.

Also, it’s best to check regularly whether the bug is still in the game and update the bug report accordingly. It is not necessary to check every single version that is released, though.

What happens to my bug report after it is submitted?[編輯]

A helper or moderator will review the report to make sure it follows the bug tracker guidelines. The majority of new bug reports are duplicates of issues that have already been reported, while others do not contain enough information to identify or reproduce the issue.


If the report does not follow the guidelines, it will be marked as resolved. If the report is accepted, the helper or moderator may attempt to reproduce the bug using the information provided and if they are able to do so, it will be marked as confirmed. Then, Mojang Studios will look at the bug report and decide when and how they want to fix it.

How long will it take for my bug to be fixed?[編輯]

This depends on how severe the issue is, how large the risk of fixing it is, and how much effort is involved in fixing it. In some cases, Mojang may decide that a bug will not be fixed. These bug reports are resolved as 「Won’t Fix」.

There is no general rule for how long it will take for your bug to get fixed. Some issues get fixed within a couple of days others may take a long time.

On some projects, bug reports are assigned to certain developers, which can be seen in the Assignee field. This means that the developer is working on the issue, but it does not necessarily imply that the bug will be fixed soon.

For Minecraft: Java Edition, you might also see that a 「Mojang Priority」 is assigned to the bug report, which indicates how important the bug is to Mojang Studios (more details below).

Why was my bug report resolved, but the problem still happens?[編輯]

There are multiple ways in which a bug report can be resolved. On each bug report, you can find its resolution at the top of the page below the status. You can find the meanings of the different resolutions below.

Only the resolution Fixed implies that the bug has been fixed by the developers. If your bug report has a different resolution, read its comments for an explanation for how and why it has been resolved.

Do you have some more tips on how to use the search function?[編輯]

Some advanced search tips to try:

  • Search terms are reduced to word stems, so for instance if you search for 「breeding」, JIRA will also return bug reports which only contain 「breed」. To avoid that, surround a word or phrase in double-quotes.
  • You can use wildcards such as 「enderm?n」 (which will catch both 「enderman」 and 「endermen」) or 「connect*」 (which will match everything starting with 「connect」, so 「connection」, 「connectivity」, etc).
  • When using the Quick Search bar in the top right, you can use some shortcuts for searching.
  • If the search query contains a project key (e.g., 「mcpe」), it only returns bug reports for that project.
  • You can also filter by resolutions (e.g., 「fixed」) or reporter (e.g., 「r:me」 returns bug reports reported by you).
  • See more information in the JIRA documentation.
  • The 「Advanced」 search looks complicated, but it is very handy if you invest a little time understanding it. Read more about how it works in the JIRA documentation.

I believe my bug report was resolved incorrectly! Where can I appeal?[編輯]

You can leave a comment on the resolved bug report. For extra visibility, you can also ask other players and moderators. (See Community Links .)

I want to discuss this issue; can I comment on it?[編輯]

If you have any suggestions or extra information to improve a bug report, we encourage commenting on it. The bug tracker is for gathering and organizing information that is helpful to the developers in replicating and fixing bugs.

However, if you want to discuss an issue, for instance, whether you think it should count as a valid bug, or whether it should be fixed or not, take the discussion outside of the bug tracker. (See Community Links.)

What Does Voting for an Issue do?[編輯]

By voting for an issue, you show that you are affected by the issue described by the bug report. This way we can estimate roughly how many players in total are affected. Mojang Studios uses this metric among others to decide how urgent a bug is to fix. However, this is not the only relevant criteria.

What are 「Labels」 for and how should I use them?[編輯]

Bug reports are labeled with certain keywords to group them together to make them easier to find. A label can be any word or phrase, but it cannot contain a space. There are no limits as for how many labels a bug report can have.

Every user can create a new label by simply adding it to their own bug report, however, this is discouraged, and you should only add already existing labels to your bug report. In most cases there is no need to add labels to your own report.

There are certain rules which labels should follow:

  • If something has an ID in the game (like blocks, entities, and items), use that ID without the 「minecraft:」 prefix as the label (e.g., 「glowstone_dust」 or 「zombie_villager」)
  • Prefix the label with a slash (「/」) for commands only (e.g., 「/gamerule」)
  • Use the 「ing」 suffix for verbs (e.g., 「breeding」 or 「fishing」)
  • Don’t use plural unless it’s the actual name of the element (e.g., 「statistics」)
  • For everything else, connect words with a dash (e.g., 「stronghold-portal」)

「Confirmation Status」是什麼意思？[編輯]

「Confirmation Status」 is used to document if the bug has been reproduced by someone else. There are four different confirmation statuses:

  • Unconfirmed – No one except the reporter has experienced the issue so far.
  • Plausible – A helper or moderator has reviewed the bug report but has not yet reproduced the issue.
  • Community Consensus – Someone other than the reporter has experienced the issue.
  • Confirmed – A helper or moderator has successfully reproduced the issue. Usually, this also requires that a list of steps to replicate the bug is included in the description and that a screenshot or video showcasing the issue is attached.

My attachment’s file size is too large, what should I do?[編輯]

You can always upload your attachment somewhere else and simply link to it in your comment or your bug report description.

For videos, often reducing the resolution of your video makes a significant difference in terms of the video’s file size. Also, some file formats produce smaller file sizes than others, for instance, .mp4 files are almost always smaller than .avi files. For most video formats, you can reduce the bitrate as well for extra savings (for reference, YouTube videos at 1080p usually use 10000).

不同的連結型別是什麼意思？[編輯]

  • duplicates – It is a duplicate of the linked bug report.
  • is duplicated by – The linked bug report is a duplicate of this bug report.
  • relates to – This and the linked bug report are related in some way, e.g., they are very similar to each other or are about the same mechanic or feature of the game.
  • clones – This about the same bug as the linked bug report, which has been resolved as fixed before.
  • is cloned by – The linked bug report is a newer report about the same bug.
  • blocks – The bug in the linked bug report cannot be tested or fixed before this bug report is resolved.
  • is blocked by – The linked bug report needs to be resolved before this bug report can be tested or resolved.
  • discovered while testing – This bug was discovered while testing the linked bug report.
  • testing discovered – While testing this bug, the bug in the linked bug report was discovered.

What does 「Mojang Priority」 mean?[編輯]

「Mojang Priority」 is set by Mojang Studios on Minecraft: Java Edition bug reports to document how important it is to them to fix the bug. This also considers how much effort is involved in fixing the bug.

If a bug report has 「Mojang Priority」 set, it is considered a valid bug by Mojang Studios.

What is the 「CHK」 field used for?[編輯]

In the past, CHK was set whenever a moderator checked a bug report. Today it is set to the date and time when the confirmation status of the bug report was initially changed by a helper or moderator. It is not particularly significant.

I found more than one unresolved bug report that seems to describe the same issue. Which one is the main report?[編輯]

If one of the bug reports already has duplicates linked to it (i.e., if there are bug reports listed in the is duplicated by issue links section), that is the one that has been designated as the main report for the issue. Otherwise, the oldest (first reported) bug report is usually preferred unless a later one has more useful detail or has already been confirmed. Remember to only comment if you have new information to add, but still vote for the bug report.

Finally, thank you for taking the time to search, as this helps the moderators to have more time to replicate and confirm bug reports instead of resolving them as duplicates.

What else can I do to help?[編輯]

You can look at other people’s bug reports, test them, or try to help improve their bug reports by leaving comments with extra information about the bug at hand. Often the most useful information is a list of steps to reproduce the bug, and a screenshot or clear video if there isn’t one already.

In case a bug report has not been updated by the reporter for a long time, you may also request ownership so you can take over updating the report.

You can also get in touch with other players who frequent the bug tracker through our Community Links, where you can communicate with others who want to help.

Who are the helpers and moderators, what do they do, and how did they become helpers/moderators?[編輯]

Helpers and moderators are volunteers. They are not Mojang Studio employees and are normal players of the game, just like you. However, they have helped with organizing bug reports on the bug tracker for a long time, and as such have been chosen by Mojang Studios and the existing moderators.

Helpers can edit any bug report as if it was their own, in order to add additional information about the bug or to clarify wording or an unclear description. They can also update the Confirmation Status.

Moderators can also resolve, link, move, and delete bug reports. They can also remove comments and see private bug reports.

Why can’t I log in to the Mojang bug tracker?[編輯]

This is most likely to be a result of one of the following scenarios:

  1. You have not created a JIRA account
    You must create a separate JIRA account to use the Mojang bug tracker; you cannot log in with your Microsoft or Mojang account.
  2. Your username may have changed
    You must log in with your current JIRA username, not your email address. Make sure usernames do not contain any personal or contact information. If you have forgotten your login details or think they have been changed by an administrator, you may wish to use the Can’t access your account? link on the login page for help accessing your account.
  3. Your account may have been restricted
    User accounts may be restricted from accessing the bug tracker if they do not adhere to the Community Standards, or if users do not follow the bug tracker guidelines and direction from Mojang Studios staff, moderators, and helpers.

What does 「Mojira」 mean?[編輯]

「Mojira」 is the nickname of the Mojang bug tracker. The software that the bug tracker uses is called 「JIRA」 and is made by Atlassian. 「Mojira」 is a portmanteau of 「Mojang」 and 「JIRA」.

我還有更多問題，在哪裡可以提問？[編輯]

If you still have a question that’s left unanswered, try asking other players directly on our official Minecraft social channels. There are other sites that you might find useful, too, but remember these are external links and are not owned or moderated by the Minecraft team:

取自「https://wiki.mcbe-dev.net/w/index.php?title=Documentation:Mojang漏洞追踪器指导方针和常见问题解答&oldid=12698」