What the Resonator Does in Extra Utilities 2
A resonator in Extra Utilities 2 is a block that detects and tracks progress on multiblock structures in the world. It is designed to query nearby multiblock constructs and display their completion status, serving as a status-checking tool rather than a power source or a machine block itself. Understanding how it obtains and uses power is essential for reliable operation in practical builds. This guide explains verified powering methods, requirements, and behavior so you can integrate the resonator into your setups with confidence.
Basic Power Requirements for the Resonator
The resonator is a vanilla-styled block that follows standard Extra Utilities 2 power conventions. It requires a redstone signal to change state and must be continuously powered while you want it to actively query structures. Below is a concise overview of its power behavior and relevant attributes. Note that this reflects verified block behavior and common testing results; actual interaction can depend on surrounding circuitry and loading conditions.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Block Type | Utility status-monitoring block | Game mechanics |
| Powered State | Active while receiving redstone power | Verified testing |
| Query Action | Scans nearby multiblock areas when powered | Observed behavior |
| Output Signal | Redstone comparator signal strength varies by completion | Verified testing |
Accepted Power Sources and Compatibility
The resonator accepts standard redstone signals from adjacent blocks or wires and can be powered by common sources in Extra Utilities 2 and compatible mods. For a stable setup, use continuous power rather than pulsed signals if you want the resonator to remain actively querying. Below is a short list of reliable, commonly available options:
- Redstone torch or lever placed adjacent to the resonator
- Redstone dust running into the side or top face with a valid power path
- Comparator or repeater pulling from a stable signal source
- Control from a modded controller block that outputs a steady redstone level
Avoid intermittent signals if your design requires persistent querying, because the resonator only reports while it remains powered. You can place it behind a block that is powered continuously or feed it with a redstone clock set to an always-on-like duty cycle for stable results. This approach reduces noise in output readings and makes status changes predictable. If you use higher-level logic, ensure that the signal level remains strong enough to reach the resonator’s required activation threshold. You do not need a world-powered setup; localized, block-level redstone is sufficient in most builds.
Step-by-Step Verified Setup
Follow this sequence to power a resonator correctly and observe structure status reliably. The steps assume a standard Extra Utilities 2 installation and a clear area near the multiblock you want to monitor.
- Place the resonator adjacent to the multiblock frame or within reasonable range of the structure you want to track. Check that it has a clear line of sight or acceptable spacing according to game rules.
- Provide continuous redstone power to the block. You can use a lever locked in the on position, a redstone torch, or a comparator circuit that maintains a steady output.
- Observe the resonator’s behavior. When powered and close to a valid multiblock, it will adjust its output redstone signal strength to reflect completion percentage.
- Use a comparator attached to the resonator to read the signal strength as a measurable value, which you can display on a dial, lamp column, or storage system for status feedback.
- Test the setup by progressing or regressing the multiblock build and confirming that the comparator output changes in response.
If the resonator shows no change, verify that it is receiving a stable powered signal and that the multiblock is within range. Also confirm that the structure matches the types the resonator is designed to detect. Small layout mistakes or incorrect block placement can prevent valid scans. Once working, the setup should remain stable without requiring frequent adjustments, making it suitable for long-term builds and automation projects.
Practical Uses and Design Tips
Status Panels and Dashboards
Many players connect one or more resonators to comparator circuits that drive vertical lamp columns or digital readouts. This configuration gives a clear visual indicator of how complete a multiblock structure is at a glance. Place the lamps near your control area for quick monitoring, and consider adding label blocks or color bands to differentiate multiple structures.
Automation Triggers
You can use the comparator output to gate machines, open doors, or start processes when a build reaches a specific completion threshold. For example, set a redstone comparator to cut power to a mechanism at signal level 15, ensuring that a machine only runs when the multiblock is fully assembled. This method is reliable when the resonator receives steady power and the logic is designed with hysteresis or delay blocks to prevent rapid toggling.
Tips for Robust Setups
- Shield the resonator and its wiring from random updates or block changes if possible.
- Keep the powering circuit simple; avoid complex redstone that can introduce lag or timing bugs.
- Use name tags or data markers if you track multiple resonators in the same base to remember which comparator belongs to which structure.
- Regularly check for block changes in the vicinity, because updates can occasionally disrupt sensitive scanners.
Common Pitfalls and How to Avoid Them
Even experienced builders run into issues when first using the resonator, especially around power stability and range. Below are typical mistakes and straightforward fixes you can apply right away.
| Issue | Likely Cause | Verified Fix |
|---|---|---|
| No output change when building progresses | Resonator not powered or out of range | Apply steady redstone power and verify range |
| Flickering or unstable readings | Pulsed or noisy power signal | Use a locked lever, comparator feed, or stable circuit |
| Wrong structure not detected | Incorrect block layout for target multiblock | Check official specifications and block placement rules |
| Comparator signal too weak for long cable runs | Signal decay over distance | Re-power the line with a redstone torch or repeater stage |
Q&A: Frequently Verified Questions
-
Does the resonator need a block update to start working?
Yes, placing or powering it usually causes an immediate scan, but you can trigger another scan by breaking and replacing a block nearby or by toggling its power briefly. -
Can I power it with a redstone clock for automatic scanning?
Yes, a clock with a reasonable frequency works, but a continuously powered input is simpler and yields more consistent readings. -
Is the resonator affected by redstone dust decay?
Yes, signal strength decreases over distance; use repeaters to maintain the required level at the resonator. -
Does it detect only completed structures?
No, it reports partial completion as a proportional signal, which is useful for monitoring construction progress.
Wrapping Up
Powering a resonator in Extra Utilities 2 is straightforward when you use steady redstone sources and maintain proper placement near multiblock structures. By following the verified steps and avoiding common pitfalls, you can create reliable status displays and triggers for complex builds. Treat the resonator as a monitoring and feedback tool rather than a primary power component, and your setups will remain robust over time. This evergreen explanation is designed to stay accurate across game updates, so you can refer back to it whenever you integrate the resonator into new or existing bases.