Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Machine Operator "Forgets" Its Job After Reloading World? #886

Closed
TrashCasterMage opened this issue Jan 31, 2023 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@TrashCasterMage
Copy link

Bug Description

Assigning a djinni machine operator a job works initially, but it must be "retaught" using the Book of Calling each time after reloading the single player world.

Logs and Crash Reports

Not facing a crash, but the logs do have this message being printed to the console repeatedly:

[Render thread/ERROR] [minecraft/Brain]: No key memories in MapLike[{}]

which seems to me like it could be related

Screenshots and/or Videos

No response

Bug Reproduction

  1. Use a Book of Calling to ensure the Djinni Machine Operator has a machine it is bound to.
  2. Save and Quit to title screen.
  3. Re-open the minecraft world.
  4. The Operators are now unable to interact with their respective machine blocks.

Expected Behavior

Expected Operators to retain their machine blocks and be able to use them between closing and re-opening the world.

Minecraft Version

1.18.2

Mod Version

1.66.2

Modpack

Other

@TrashCasterMage TrashCasterMage added the bug Something isn't working label Jan 31, 2023
@klikli-dev
Copy link
Owner

Thanks for the report!
The log statement is not the issue, it's expected, and as the operator is not using the Brain system it's unrelated.

That said, it should save the instructions on World close, I'll look into it.

Meanwhile, can you please try if this occurs when using just occultism + required dependencies (eg by installing occultism via curseforge launcher)?

@klikli-dev
Copy link
Owner

Disregard the above - it reproduces in dev.
Fixed in 1.67.2

Turns out when adding the option to have a separate extract location it was accidentally overwriting the wrong save data thus making it impossible to load on world load

@TrashCasterMage
Copy link
Author

Disregard the above - it reproduces in dev. Fixed in 1.67.2

Turns out when adding the option to have a separate extract location it was accidentally overwriting the wrong save data thus making it impossible to load on world load

Really did not expect this to get fixed overnight while I was asleep. That was fast! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants