SkyFactory 5

SkyFactory 5

280k Downloads

Spawners tooltip doesn't show details, has "Error: placebo:plugin"

nogweii opened this issue ยท 5 comments

commented

Bug Description

When I hover over a spawner, naturally spawned or modified by a player, it shows the name, tool, redstone signal, mob, and then an error line. "Error: placebo:plugin". Sneaking does not change the information displayed. No difference between mobs from a mod, or a regular blaze spawner in the nether.

Screenshots:

electric sheep spawner in my base
Here I modified the spawner to be silent and to controlled via redstone

blaze spawner in the nether
A blaze spawner naturally found in the nether

Did this behavior used to work in the previous version?

No

If you answered Yes above...

N/A

Steps to Reproduce (for bugs)

Not 100% sure, but it's always reproducible for me.

  1. Find or place a spawner
  2. Hover over it

Client/Server Log:

N/A

Crash Log:

N/A

Modpack Version world created in:

v5.0.6

Additional Content Installed?

N/A

Modpack Version:

v5.0.7

Java Version:

v17.0.8

Launcher Used:

Prism

Memory Allocated:

8192

Single Player/LAN/Server:

Server

Optifine Installed:

No

Shaders Enabled:

No

commented

PS: The energetic sheep still make the squeaky toy sound even with soundproofing. Intentional? Should that be another bug report?

commented

This is a known issue in apotheosis, happens when running on the server but not in SP, closing this as we can't fix it and it has to be fixed in the mod itself.

commented

I think this is actually fixed in later versions of Apotheosis, see this commit from last week in their Github repo.

Since then, v7.4.6 has been released.

EDIT: Actually, in fact, 7.4.5 has this bug fix explicitly:

7.4.5

Fixed TOP always showing an error for Mob Spawners on dedicated servers.

commented

@Dutchs could this be reopened until the pack releases with an updated Apotheosis?

commented

This issue is known by the team, and Apotheosis should be updated as a matter of course for the next update, I see no reason to specifically keep an issue for it open.