Placing default:sign_wood_yard (obtained from a loot chest) and am disconnected with:
Access denied. Reason: This server has experienced an internal error. You will now be disconnected.
Note that default:sign_wood_yard is not in the crafting guide, and was obtained from lootchests_default:urn loot chest. When default:sign_wall_wood (from crafting guide) is placed on build-able ground, it becomes default:sign_wood_yard and does not have the disconnection issue. When the default:sign_wood_yard as obtained from the loot chest is placed then there is the problem and on re-log the placed sign exists and can be dug wherein it is converted to default:sign_wall_wood (so no longer has this problem onward).
Placing `default:sign_wood_yard` (obtained from a loot chest) and am disconnected with:
`Access denied. Reason: This server has experienced an internal error. You will now be disconnected.`
Note that `default:sign_wood_yard` is _not_ in the crafting guide, and was obtained from `lootchests_default:urn` loot chest. When `default:sign_wall_wood` (from crafting guide) is placed on build-able ground, it becomes `default:sign_wood_yard` and does not have the disconnection issue. When the `default:sign_wood_yard` as obtained from the loot chest is placed then there is the problem and on re-log the placed sign exists and can be dug wherein it is converted to `default:sign_wall_wood` (so no longer has this problem onward).
i can confirm, this happened to me, exact same scenario. i had placed a protector icon, then added a player, then placed a protected chest just behind it, then tried to place a "wall sign" on the chest, didn't work, so i placed it on the ground, to the right of the chest, 1 node diagonal to protector, and server immediately crashed.
i can confirm, this happened to me, exact same scenario. i had placed a protector icon, then added a player, then placed a protected chest just behind it, then tried to place a "wall sign" on the chest, didn't work, so i placed it on the ground, to the right of the chest, 1 node diagonal to protector, and server immediately crashed.
i can confirm, this happened to me, exact same scenario. i had placed a protector icon, then added a player, then placed a protected chest just behind it, then tried to place a "wall sign" on the chest, didn't work, so i placed it on the ground, to the right of the chest, 1 node diagonal to protector, and server immediately crashed.
i can confirm, this happened to me, exact same scenario. i had placed a protector icon, then added a player, then placed a protected chest just behind it, then tried to place a "wall sign" on the chest, didn't work, so i placed it on the ground, to the right of the chest, 1 node diagonal to protector, and server immediately crashed.
Placing
default:sign_wood_yard
(obtained from a loot chest) and am disconnected with:Access denied. Reason: This server has experienced an internal error. You will now be disconnected.
Note that
default:sign_wood_yard
is not in the crafting guide, and was obtained fromlootchests_default:urn
loot chest. Whendefault:sign_wall_wood
(from crafting guide) is placed on build-able ground, it becomesdefault:sign_wood_yard
and does not have the disconnection issue. When thedefault:sign_wood_yard
as obtained from the loot chest is placed then there is the problem and on re-log the placed sign exists and can be dug wherein it is converted todefault:sign_wall_wood
(so no longer has this problem onward).i can confirm, this happened to me, exact same scenario. i had placed a protector icon, then added a player, then placed a protected chest just behind it, then tried to place a "wall sign" on the chest, didn't work, so i placed it on the ground, to the right of the chest, 1 node diagonal to protector, and server immediately crashed.
i can confirm, this happened to me, exact same scenario. i had placed a protector icon, then added a player, then placed a protected chest just behind it, then tried to place a "wall sign" on the chest, didn't work, so i placed it on the ground, to the right of the chest, 1 node diagonal to protector, and server immediately crashed.