Skip to content

Conversation

@tomprince
Copy link
Contributor

This allows determining whether there are any available CPUs that can handle requests from automation. This is relevant if some crafting CPUs have been reserved for use by players.


PLEASE READ THE GUIDELINES BEFORE MAKING A CONTRIBUTION

  • Please check if the PR fulfills these requirements
  • The commit message are well described
  • Docs have been added / updated (for features or maybe bugs which were noted). If not, please update the needed documentation here. This is not mandatory
  • All changes have fully been tested
  • What kind of change does this PR introduce? (Bug fix, feature, ...)

Feature

  • What is the new behavior (if this is a feature change)?

meBridge.getCraftingCPUs() returns objects with a new field selectionMode which can have one of ANY, PLAYER_ONLY or MACHINE_ONLY.

  • Does this PR introduce a breaking change? (What changes might users need to make in their scripts due to this PR?)

No.

  • Other information:

This PR is against the 1.18 branch, since the modpack I am currently playing is a 1.18 modpack. I've not tested this change against newer versions.

This allows determining whether there are any available CPUs that can
handle requests from automation. This is relevant if some crafting CPUs
have been reserved for use by players.
@SirEndii SirEndii changed the base branch from release/1.18 to dev/1.18.2 March 30, 2024 17:56
@SirEndii SirEndii merged commit 8ecadb3 into IntelligenceModding:dev/1.18.2 Mar 30, 2024
@tomprince tomprince deleted the me-crafting-cpu-mode branch March 30, 2024 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants