Immersive Engineering

Immersive Engineering

134M Downloads

[1.12.1] Chute Glitch on SMP on FTB Revelations 3.2.0

Meserion opened this issue ยท 5 comments

commented

Initially placing Chutes in Multiplayer works fine, can be adjusted as work as intended. However, upon relogging the Chutes seem to glitch out losing both functionality and their appearance. Issue seems to only be in multiplayer, on creative singleplayer the chutes work fine. I've only tested Iron Sheetmetal Chutes.

I will note when placing the Chutes it seems to, "refund", the chutes placed as though they where not placed at all.

image

commented

@Meserion
FTB Revelations is using an outdated version of IE, this bug was fixed in build 92.

@Halo3fanz are you sure that you are running that version on client and server, and the chutes were placed after updating to 92? Because the bug should be gone.

commented

@BluSunrize I have confirmed with the server host that it is 0.12-92. FWIW we upgraded from 0.12-89 straight to 0.12-92 while chutes were added in 0.12-90 according to the changelog. I crafted the chutes after the upgrade.

commented

I'm getting a similar glitch, running 0.12-92 on client and server, When I place a steel chute and break it instead of giving the chute item it gives a "tile.immersiveengineering.conveyor..name" item, with a conveyor belt icon. When I place that item it looks like that purple and black tiled item in the picture.

commented

I am also getting this issue on 0.12-92 in multiplayer except that the functionality is not present at all after placement. Breaking the chutes yields the broken conveyor belts shown in the photo by OP as an item with the name

tile.immersiveengineering.conveyor..name

commented

@malte0811 I see where you closed this issue back on October 27 2019 with commit 67c74c2, however the version on Curseforge has not been updated since September 2019 and is still version 92. Is there any plans to push the update for the chute fix, or is IE for 1.12.2 dead as far as updates go? I ask since this was reported, fixed, committed, and closed 5 months ago, with no update having been posted to Curseforge.