ReferenceBy IDLE_DIRECTIVE Guide EditorialPublished

Component Behavior and Current Questions

A version-aware component reference that separates confirmed behavior from current launch questions.

A dense IDLE_DIRECTIVE body grid containing powered and timed components
Test one component, one source, and one destination through a complete work cycle.
Table of contents

Several components can look broken when the real cause is a work condition, cooldown, destination, full storage, or pulse phase. Start with behavior that is currently confirmed, then isolate unresolved cases instead of rebuilding the entire body.

Confirmed current behavior

Collector

The full-release base Collector uses a 20-second cooldown. The tier-two version is more compact and has a faster cooldown. Multiple Collectors can reduce the wait between collection events, but every extra copy also consumes body space and energy.

Treat the Collector as timed automation, not an instant substitute for manual pickup. If it appears idle, allow one complete cooldown before changing the layout.

Harvester, Salvager, and processing demand

Some work components draw no energy while idle and begin drawing energy only when a valid job starts. An idle zero-consumption reading does not prove the component is disconnected.

Test with:

  1. a valid source or POI;
  2. free destination capacity;
  3. a stable positive energy baseline;
  4. one complete work cycle;
  5. the energy rate observed before and during work.

Biomass chain

An ordinary Biomass Cell is filled manually from Biomass storage. The filled Cell connects directly to the Bio Generator, and the Generator connects to the main grid. A Harvester supplies Biomass storage from a compatible POI; it does not fill the ordinary Cell directly.

Use the complete Biomass sequence when that chain is the problem.

Questions that are not settled

Component or symptom What is currently safe to say What is not established
Smart Grabber Test its selected target with free body inventory and storage Automatic routing into the matching container
Sensor stacking More than one Sensor can be placed and compared A repeatable linear range formula or an efficient stacking recommendation
Spinner and Repeater phase A player resolved one chain by offsetting Repeater placement timing A universal phase interval for every orientation and frame rate
Long-session slowdown Restarting can recover a session for some players A confirmed memory-leak root cause or permanent fix
Maximum item level Level 250 is an achievement milestone That level 250 is the absolute cap

An unresolved row is not a hidden recommendation. It means the current evidence is not strong enough to tell every player to build around that claim.

A controlled component test

Use this order whenever a component's behavior is disputed:

  1. Record the version. A launch-day result may be obsolete after a hotfix.
  2. Clear the destination. Leave inventory or storage capacity available.
  3. Provide one valid source. Use a known resource, POI, fuel Cell, or pulse.
  4. Simplify the connection. Move the component to a clear grid edge with the shortest possible powered path.
  5. Observe a complete cycle. Timed components cannot be judged from one second of idle state.
  6. Change one variable. Adjust orientation, source, destination, or timing, never all four together.
  7. Restore the original chain only after the isolated test works.

For a visual layout experiment, open the Body Grid Planner. A planner can test geometry and its modeled constraints, but the current game remains the authority for cooldowns, item tiers, and post-launch behavior.

Spinner and Repeater timing experiment

If a visually connected Spinner chain never reaches working speed:

  1. confirm the energy connection first;
  2. isolate one Spinner and the required Repeater relationship;
  3. allow the first Repeater to enter its cycle;
  4. add the second timed connection at a different phase;
  5. compare the result through several complete pulses.

This is a diagnostic experiment based on a resolved player case, not a guaranteed optimal layout. Frame rate, current version, and component tier may change the observation.

Related guides

Inventory Connections and Grid Troubleshooting

Check component ports, orientation, timing, storage, and energy when an item looks connected but does not run.

Read guide
Community tool

IDLE_DIRECTIVE Body Grid Planner

Use Zdendys79’s community Body Grid Planner, learn its fast and SMART modes, and transfer a layout without dismantling a working grid at once.

Read guide
Updated Jul 29

Launch Troubleshooting and Known Issues

Check the dated status of the v1.0.1 frame-rate, Trader, Augment-label, and POI pickup fixes before changing a layout or save.

Read guide