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

Add "one to many" AE2 wireless connector. #14729

Open
5 tasks done
AbdielKavash opened this issue Oct 18, 2023 · 5 comments · May be fixed by GTNewHorizons/ae2stuff#24
Open
5 tasks done

Add "one to many" AE2 wireless connector. #14729

AbdielKavash opened this issue Oct 18, 2023 · 5 comments · May be fixed by GTNewHorizons/ae2stuff#24
Labels
Mod: AE2Stuff Status: Ready for Developer Issue ready for a developer to pick up and implement Suggestion Type: Enhancement

Comments

@AbdielKavash
Copy link
Member

Your GTNH Discord Username

abdiel_kavash

Your Pack Version

2.4.1

Your Proposal

Add a new version of the AE2 Stuff Wireless Connector, which supports one source and multiple destination connectors. The channel count should still be limited to 32 total across all connections, to not overshadow wired p2p connections. Running AEU (EU/t) cost should be proportional to a similar setup built using existing one-to-one connectors.

Your Goal

Wireless AE connectors offer a much cleaner alternative to spaghetti wiring AE cables everywhere, especially in situations where multiple networks are used in the same setup. However, if I want to wirelessly connect several places (for example, link all ME output buses/hatches from a machine line), currently each destination needs an individual wireless connection, taking up much physical space near the ME controller.

Alternatively, one can daisy chain a group of machines where each has an "incoming" and an "outgoing" connection passing the AE channels to the next machine; however this setup is sensitive to adding new channels when one wishes to expand the setup.

Your Vision

Being able to place one Wireless ME Transmitter next to the ME controller, and then a Wireless ME Receiver next to every machine or logical setup would simplify the task, as one could simply link all the individual receivers to the same transmitter block. To add more than 32 channels to the setup, one can simply add another Transmitter block for every 32 channels, and as many Receivers as necessary.

Final Checklist

  • I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying I like this feature please reconsider adding it will prompt us to investigate and reopen it once we confirm your report.
  • I believe there is nothing similar in the pack already, or the existing solution isn't good enough.
  • I understand this change request may not attract enough attention and thus not be implemented.
  • I understand this change request may be rejected due to other community members thinking it's inappropriate.
  • I believe this feature would make the pack better.
@AbdielKavash AbdielKavash added Status: Triage Issue awaiting triage. Remove once this issue is processed Suggestion labels Oct 18, 2023
@GTNH-Afx237v7
Copy link
Contributor

Seconded.

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Jan 16, 2024
@Dream-Master Dream-Master removed the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Jan 16, 2024
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Apr 15, 2024
@AbdielKavash AbdielKavash removed the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Apr 15, 2024
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Jul 14, 2024
@Ethryan Ethryan added Mod: AE2Stuff and removed Status: Stale Automatically close this issue in 2 weeks if there are no new responses labels Jul 14, 2024
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Oct 12, 2024
@TheEpicGamer274 TheEpicGamer274 removed the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Oct 12, 2024
@Ruling-0 Ruling-0 added Type: Enhancement Status: Ready for Developer Issue ready for a developer to pick up and implement and removed Status: Triage Issue awaiting triage. Remove once this issue is processed labels Nov 8, 2024
@lordIcocain lordIcocain linked a pull request Nov 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mod: AE2Stuff Status: Ready for Developer Issue ready for a developer to pick up and implement Suggestion Type: Enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants