Friends&Foes (Forge/NeoForge)

Friends&Foes (Forge/NeoForge)

22M Downloads

Disabling Beekeeper profession breaks Productive Bees beekeepers

brisingraerowing opened this issue ยท 10 comments

commented

Minecraft version information

1.20.1

Mod loader information

Forge

Mod loader version information

47.3.22

Mod version information

3.0.7

Expected Behavior

Using F&F and Productive Bees with the F&F beekeeper disabled allows the Productive Bees beekeeper profession to be obtainable by villagers.

Actual Behavior

When using F&F and Productive Bees with the F&F Beekeeper disabled, putting down an advanced hive and a villager will result in the villager briefly taking a job, then reverting to unemployed.

Reproduction Steps

  1. Install F&F and Productive Bees
  2. Disable F&F beekeeper
  3. Try to get a Productive Bees beekeeper.

Screenshots & files

No response

commented

Running F&F and Productive Bees with beekeeper disabled, i normally get productive bees beekeepers:

Image

commented

Weird. Didn't work in a minimal test instance (Just JEI, EMI, PB, and F&F). I'll mess around with it more.

commented

If it helps, this is currently my test instance:

Image
Image

commented

I was testing with Forge 47.3.22. Might be a Forge bug.

EDIT: Even with Forge 47.3.6 it's broken for me. WTF.

commented

Can you show your instance, versions etc. please? Basically if both of us can get the steps to reproduce, i can try to fix it.

commented

Image

I've also tested without EMI and JEI. No change.

EDIT: Jei is 15.20.0.106, since I had it disabled in the last test.

commented

Well I just found something weird. I tested with a test instance in the CF launcher and the villager took the job perfectly fine. I usually use Prism to play by symlinking the CF instance to a Prism instance. I wonder if Prism is somehow breaking things.

commented

OK, so with identical setups in Prism and CF, there's an additional log entry saying 'POI mismatch, never registered' in the Prism instance.

commented

Yup. Something got corrupted in the Prism instance and somehow broke this. Completely removing and reinstalling Prism fixed the issue.

This is honestly the weirdest bug I've run into. How does the launcher cause an in-game feature to break?

commented

Yeah, random stuff happens all the time, glad i dont have to fix anything then :D