Common Issues

目錄

• 漂浮文字
• Unplaceable blocks
• Circuit Boards not dropping

此頁面將包含有關遊戲常見問題以及如何解決它們的資訊.
以下大多數情況都需要有不同程度權限的工作人員: 如果沒有, 請將此連結給有更高權限的人!

WARNING: some issues have more than one viable solution, indicated by a division in stages from the least to the most intrusive; it is HIGHLY recommended you try all previous stages before you follow any further approach as lower stages are less risky and will solve most occurencies anyways. If you've tried everything in the list with no success, consider filing a bug report!

漂浮文字

有些Slimefun的物品會在放置時自動創建漂浮文字, 尤其是 能量調節器 和 物流核心.
這些漂浮文字應在破壞機器時消失, 但有時可能出錯, 並留下一些不想消失的文字. 你要怎麼解決?

注意: 請確保這不是由鬼方塊引起的 (請檢察 "不可放置的方塊")!

如何解決這個 (第一階段)

移除任何在漂浮文字下方的調節器/核心, 然後靠近他並以管理員身分運行:

/execute as <你的遊戲ID> at @s run execute as @e[type=armor_stand,nbt={Invisible:1b},distance=..3] run data merge entity @s {Invisible:0}

你現在可以直接用手打掉盔座. 你可能需要打好幾次, 因為它們可能已經升成了一些並堆疊在一起, 這取決於你所使用的插件.

提示: 建議使用 MyCommands, CommandOverride 或任何相似的插件來設定一個別名, 以便於記憶與教導 (一個範例像是 /holokill).

How to fix this (Stage 2)

Switch to spectator mode via

/gamemode spectator

You should see the invisible armor stand and better gauge where the feet are; using this information, place a new regulator just below the tag on the first block not occupied by the armor stand itself (get one via /sf cheat).
The regulator will try to place its own armor stand which will replace the corrupt ones and behave normally: you should now be able to remove the regulator you've just placed, removing all tags.

How to fix this (Stage 3)

If the hologram keeps respawning you're very likely to be dealing with a ghost block like the ones dealt with under Unplaceable blocks, with the only difference it's also spawning a hologram because it's one of the items listed up top. Simply follow the procedure to get rid of any ghost block and you should be golden.

Unplaceable blocks

If you encounter a location that seems empty but will cancel your action when you try to place any block there you're probably looking at a ghost Slimefun block.
This means a Slimefun item used to be placed there (usually an android or a cargo component) and its data was not correctly removed.

How to fix this (Isolated block)

Get a debug fish by running the following as operator:

/sf debug_fish

(Optional): Use the shift right click function to place a dummy head where the ghost block is and try to punch it out: if a Slimefun head drops you're sure to have a ghost block (the opposite is not necessarily true as the ghost Slimefun item could've been a full block and not a head, it's less likely though and just good to get a confirmation if possible).

Shift right click to place a dummy head, then shift left click it: an animation of the head being broken and the event being canceled should be seen and you'll get a message in chat; this will remove whatever data is still linked to the location.

Punch out the dummy head.

How to fix this (Cluster of blocks)

This is very similar to the procedure for isolated blocks: in this case instead of placing all the dummy heads one by one you can run WorldEdit commands to speed up the placing process.

Use WorldEdit to select the cluster of blocks and its surroundings and execute:

//set stone

As per the isolated blocks procedure, shift right click all the incriminated spots to remove any data they may retain.

Remove the stone by executing:

//undo

Circuit Boards not dropping

If you kill Iron Golems and they don't seem to drop any Iron Golems, it may be due to a conflicting plugin.
Plugins like MobStacker or similar are known to have a lot of issues with custom item drops.

How to fix this (Stage 1)

The best solution to this problem is to enable custom item drops in that plugins config, if such an option exist.
Or ask the authors of that plugin whether there is a way to toggle this behaviour.

How to fix this (Stage 2)

A more drastic approach would be to switch over to a Mob-Stacking plugin that supports custom drops.
At this point we do not have a list of mob-stacking plugins that are confirmed to work with Slimefun, if you use a plugin that works without any issues, feel free to name it right here. See Expanding the Wiki