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

Reformation (Replication) #137

Closed
21 tasks done
klikli-dev opened this issue Jun 10, 2023 · 0 comments · Fixed by #157
Closed
21 tasks done

Reformation (Replication) #137

klikli-dev opened this issue Jun 10, 2023 · 0 comments · Fixed by #157

Comments

@klikli-dev
Copy link
Owner

klikli-dev commented Jun 10, 2023

  • re-texture the emitter to fit the reformation color theme

  • add reformation recipes

  • add recipes for apparatus

  • ensure emitter when picked up stores MF but not linked pedestals

  • test network

  • add jei renderer

    • fix: input/output not found, only catalysts
  • in ENUSProvider provide usage instructions

  • add book pages

    • document that right-click shows linked
    • document that right-click validates linked locations - allows to re-enable after breaking a necessary pedestal
    • document the sal ammoniac bucket -> crystal recipe
  • particle effect above the pedestal if active

    • one glowing bubble, slightly moving. Color should fit the colors of the particle effects shooting betwen pedestals
  • recipes should only load if the materials represented by the tags is available -tricky!

  • the alchemical process is called reformation, it changes the sulfur (e.g diamond to emerald) within the same tier and type tag.

  • Structure:

    • the whole thing is called "Reformation Array"
    • particle flies from energizer to source sulfur, changes color to indicate it carries something, then from source sulfur to target sulfur, changes color again, and then ends at the output pedestal where it places the sulfur
      • particle can just be a visual indicator without really being 100% in sync with server
  • selection mechanism to link multiblock to emitter?

    • we might have multiple source pedestals, one result, and one target
    • so the emitter should select all the pedestals
  • handle pedestals being destroyed?

  • show linked pedestals

    • maybe also print status? Like "missing target". Or just use the selection prints?
  • update selection prints to show errors if not at least one of each is present

  • Concurrent recipes up to x10 possible? -> potential future feature

    • increases mercury cost by e.g. x1.2
    • bigger particle
  • the "source" will just be a small block placed on the mercury catalyst that is also used for the heat stuff

    • we call the source a sulfuric flux emitter
@klikli-dev klikli-dev transferred this issue from another repository Jul 26, 2023
@klikli-dev klikli-dev changed the title Replication Reformation (Replication) Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant