Files
DSP_Mods/UXAssist/docs/ProductionArchitecture.md
T
soarqin 51af1430bc fix(uxassist): anchor blueprint options and use native popup controls
Follow the Auto-fill entry after native layout and scrolling, flip or constrain placement at canvas edges, and close detached or hidden popups.

Use the native close-X artwork with an isolated callback, compact settings, and one footer Generate action. Keep dropdown choices above the action and preserve native blueprint layout and production calculations.
2026-11-04 22:57:23 +08:00

35 KiB

Production Calculation Architecture

UXAssist exposes a shared production catalog, a material planner, a fixed-building black box analyzer, and blueprint capture. These APIs calculate reports without changing DSP production or replacing factory updates. The blueprint inspector also offers an explicit, click-to-generate description; it is not a continuous factory calculator.

Data and lifecycle

  • ProductionCatalogService.Current is an immutable snapshot of loaded item, recipe, technology, building, PrefabDesc, and Cargo data. The service rebuilds after data preload and on game begin, so changes made by later preload callbacks are captured. It clears the snapshot when a game ends. It can be null before preload. Subscribe to ProductionCatalogService.Changed to invalidate derived reports and retry against the current snapshot; the event also reports clearing the catalog.
  • Capture a live blueprint selection on the game thread. The planner, black box analyzer, adapters, and simplex implementation read only immutable snapshots and managed request data. They do not retain game component references or inspect current inventories during calculation.
  • Material rates use double items per minute; process executions, hashes, and launches are also per minute. Native simulation runs at 60 ticks per second, so recipe cycle rates use 3,600 ticks per minute, not 60. Convert fixed-point speed values by 10,000 and energy per tick to watts by 60. Gas speeds arrive in items per second and must also be converted to per-minute outputs. Round only for display and for the separately reported building deployment count.
  • A report carries separate MaterialComplete and PowerComplete flags, Diagnostics, individual ItemFlows, and Groups. ProductionPower is null if any power requirement is unknown; a group's unknown Dyson-sphere demand is also null. PowerBreakdown additionally reports independently complete factory and logistics consumption, with nullable category totals and known portions. The planner's breakdown has zero logistics consumption because logistics is outside its scope. Never interpret an absent result or incomplete category as zero.

Accumulator charging and critical photon production have no native RecipeProto entries. The catalog adds calculation-only recipes from the captured exchanger and receiver metadata, with stable IDs equal to the negative output item ID. ProductionRecipe.IsSynthetic identifies these entries. Resolve them through ProductionCatalog.Recipes, never through LDB.recipes or a native building recipe setter. They supply default routes only when no native recipe provides one.

An item's default recipe follows the native maincraft choice, the recipe listing the item at the lowest result index, but skips recipes that consume their own product. Reforming Refine, for example, cannot start a Refined Oil chain, so Plasma Refining remains its default.

Global production planning

Select a target and, if desired, a building for the recipe or its category:

var request = new ProductionPlanRequest();
request.Targets.Add(new ProductionTarget(itemId, 60));
request.BuildingByCategory[ProductionRecipeCategory.Assemble] = assemblerItemId;
request.ExternalMaterials.Add(rawResourceItemId);

var report = new ProductionPlanner(ProductionCatalogService.Current).Calculate(request);
if (report.MaterialComplete)
{
    var rawImportsPerMinute = report.ItemFlows[rawResourceItemId].ExternalImports;
}

The solver includes all selected recipes, coproducts, finite external supplies, permitted imports, and proliferator consumption in one material balance. It never silently chooses another recipe. Explicit boundaries and Dark Fog materials are external; natural items are external unless an explicit recipe overrides their default collection source. Without a building choice, material flows that do not depend on that choice remain available, but building power is incomplete. This also keeps the material flows of recipe types the catalog does not recognize, such as ones added by other mods. An explicit extra-products mode for a recipe without that native capability is an error.

When proliferation is enabled, ordinary recipes default to their native extra-products or acceleration capability. Fractionation and accumulator exchange use acceleration; a ray receiver uses acceleration only with a lens. Per-item choices can override these defaults when the process supports the selected mode. A recipe runs in one mode: the explicit choice of any product it is selected to make applies to the whole recipe, and conflicting choices for products of one recipe are an error when that recipe is used.

SelfSprayProliferator uses the captured spray count and extra-products bonus to calculate effective sprays per produced proliferator, including the spray spent coating the proliferator itself. SprayDeliveredItems adds spraying for requested deliveries. Accumulators retain their coating during both charging and discharging: adapters expose PreservedSpraysPerCycle, and the planner credits that coating only against demand for the same item. Each credit is bounded by both preserved output and sprayed input or delivery demand, so coating is neither created nor charged twice. Credits reduce proliferator consumption, not material quantities. The solver minimizes process executions, then imports, maximizes valid spray reuse, and finally minimizes remaining surplus.

GrossProduction and GrossConsumption are independent ledgers. NetFlow is their difference; imports, known supply, target delivery, and surplus remain separate fields. Power.ConsumptionWatts uses equivalent fully utilized buildings, whereas PeakConsumptionWatts uses rounded deployment counts. Fixed layout power is not inferred: add explicitly selected sorters, spray coaters, or other non-logistics auxiliary devices to request.AuxiliaryBuildings. The power scope then changes from ProductionBuildings to ProductionBuildingsAndAuxiliary.

Fixed-building analysis

By default, the black box evaluates each selected building at full load, even if another selected building cannot provide all its inputs. It does not simulate belt layouts, startup storage, or logistics throughput. Missing inputs appear as RequiredExternalSupply; byproducts and internal deficits retain producer and consumer group attribution. GrossProduction and GrossConsumption remain separate even when a recipe returns some of its own input. Material classification uses each process's net per-item flow, so that return cannot become a false external requirement or coproduct. The optional blueprint production basis below changes material ledgers only when explicitly requested.

IntermediateShortage records the missing externally supplied portion of an item produced and consumed within the selection. OverbuildSurplus and CoproductSurplus are independent nullable amounts; both can be positive for the same item. Equivalent buildings are grouped by recipe, building, proliferation mode, speed, and operating settings in stable order. Whole-building reductions are tested against every item's shared balance: no final-product capacity may decrease and no internal shortage may increase. The reduction identifies redundancy only; gross flows, original full-load inputs, outputs, and power never change. Coproduct supply counts only retained whole buildings required by a process's other products, and internal net consumption is credited before exposing the remainder. Headroom from a single-output producer or a joint process's limiting product remains ordinary balance, not a coproduct. When materials are incomplete, overbuild and coproduct amounts are unknown rather than fabricated from a partial layout.

SteadyStateExternalSupply is a separate input estimate from the known processes. After whole-building classification for complete selections, a fractional reduction of surplus intermediate producers propagates downstream limits through upstream processes. The reduction stops after a bounded number of passes, because a lossless cycle such as charging and discharging accumulators can otherwise pass a tiny leftover around indefinitely; stopping early only keeps the input estimate conservative. Every reduction applies to the entire process, keeps rated final-product capacity, and never worsens an existing intermediate shortage; deterministic grouping and ordering keep results independent of blueprint building order. For partial selections, skip whole-building classification but still cap independently known upstream inputs against known demand. Protect any known inputs of an unresolved downstream process, or all known products if its possible inputs are unknown, instead of treating its demand as zero. Only the blueprint description uses this estimate, marked as a known portion when incomplete. Gross ledgers, RequiredExternalSupply, uncertain overbuild and coproduct classification, independently known rated outputs, and power retain their original meaning.

FactoryBlackBoxRequest.ProductionBasis defaults to BlueprintProductionBasis.FinalProducts, preserving these existing full-load semantics for all callers. The blueprint inspector can explicitly select BottleneckIntermediate. This mode reuses TwoPhaseSimplex to maximize one common fraction, no greater than 1, of the selected final-product mix, bounded by each selected process's capacity. Terminal consumers without item outputs, such as launchers, fuel generators, or precisely configured research, operate at that same fraction. Every internally produced material must balance without external imports; only materials with no selected producer can enter from outside. Capacities are converted through recipe ratios and shared consumption, rather than comparing different items' absolute per-minute rates. Joint products and selected cycles participate in the same balance; no unselected recipe is introduced. After maximizing the common fraction, the solver minimizes used building capacity, then remaining normalized surplus.

On a successful bottleneck calculation, all material ledgers, external inputs, final outputs, and research-matrix outlets use the normalized process rates. Unused positive intermediate capacity, including fractional building capacity, is reported as excess. This measures spare rated capacity rather than actual surplus stock or extra throughput; that capacity may not be simultaneously attainable from the normalized upstream flow. Surplus necessarily produced alongside required joint products remains coproduct output. A complete, balanceable chain therefore has no internal shortage within numerical tolerance. Groups and power retain the full selected building capacities, so normalized material rates must not be used to infer reduced power demand. Unknown material data, an unidentified final outlet, zero feasible throughput, or a failed or limited solve produces BlueprintBasisUnavailable; the inspector then preserves the existing description and fields. A pure cycle without a final outlet cannot establish this basis. A selection with no internal intermediate can retain its rated final output; a known selection with no material flows can still generate its power field without a material solve. Independently unknown power does not become known through balancing.

var capture = BlueprintSelectionReader.Capture(factory, selectedObjectIds);
var selection = capture.CreateRequest(proliferationEnabled: true);
var report = new FactoryBlackBoxAnalyzer(ProductionCatalogService.Current).Analyze(selection);

Capture accepts existing entity IDs and negative prebuild IDs. Its optional third argument is a BlueprintSelectionContext; use OperatingParametersByObjectId to supply missing settings keyed by those same signed IDs. FromBlueprint(blueprintBuildings, context) captures a blueprint without live game objects, decodes settings through the native blueprint-paste path, and uses OperatingParametersByIndex, keyed by blueprint index. Supplied settings override captured values before validation. In particular, fractionator circulation and stack size must describe the intended full-load input, not transient inventory contents; FluidItemId can identify the input when the fractionator has not been filled. Transient runtime throttles, such as a miner's output backlog damper, are never captured.

The capture is read-only and does not alter the game's selection. CreateRequest carries capture diagnostics into the analyzer, so stale or unrecognized selected objects cannot turn into a falsely complete empty report. Duplicate selected IDs are diagnosed and counted once. Assembler proliferation modes are decoded from the native parameter array; lab modes use their native mode field. Nonproductive recipes use native acceleration rather than an invalid extra-products mode.

The global proliferation switch uses the highest level supported by the captured proliferator items while preserving each production building's acceleration or extra-products setting. It also controls fuel and launch-ammunition proliferation. The black box assumes input coating is supplied externally and does not add proliferator consumption for that coating.

Selected Planetary and Interstellar Logistics Stations, Logistics Distributors, and Battlefield Analysis Bases contribute their configured maximum charging power to both Power.ConsumptionWatts and PeakConsumptionWatts. These are charging limits, not current draw, inventory flow, or accumulator exchange. A manual building snapshot supplies ChargePowerWatts in watts; live capture reads the consumer's configured work energy per tick, while prebuild and blueprint captures use native stored settings or prefab defaults when no setting is applied. Missing or invalid charging power leaves logistics consumption and the combined power result unknown, without discarding known factory consumption or material results. Factory consumption also includes selected sorters, Spray Coaters, and other powered auxiliary buildings. Charging power nodes such as Satellite Substations and Wireless Power Towers count at their idle draw, because only mecha charging raises them above it. Advanced Mining Machines retain their mining power calculation rather than gaining a second charger; orbital collectors recover their own fuel instead of drawing grid power. A miner missing resource context can still report independently calculable speed-ratio power; a ray receiver missing Dyson loss settings retains its known factory draw even though total power remains incomplete.

All selected research-mode labs contribute their full prefab working consumption to factory and total power, regardless of current technology validity or transient idle state. When proliferation is enabled, apply the highest supported matrix power multiplier; with no supported spray level, use base working power. This intentionally conservative blueprint estimate avoids undersizing the power supply. An invalid power rating or unavailable multiplier remains unknown.

Native research uses the current lab technology's matrix point requirements, with 3,600 points consumed per item. Precise live or manually supplied research settings still require TechId and ResearchSpeed. ProductionCatalogReader independently captures native LabComponent.matrixIds as immutable ResearchMatrixItemIds. FromBlueprint sets ResearchMatrixSink rather than using the current technology or research speed. In this blueprint-only model, one selected research lab provides a virtual outlet for every native matrix item manufactured in the blueprint. Protect this production against whole and fractional upstream reductions; classify its positive net rate after other buildings' known consumption as a final research product, not a redundant building or exported coproduct. Do not add a fabricated matrix consumption rate, external matrix requirement, or research hash rate to the lab's numeric report. Known matrix use by other selected processes remains a real material input; if native matrix IDs are unavailable, material completeness is unknown while separately known lab power remains available. The outlet is a planning convention, not a simulation of real lab throughput or belt connectivity.

Blueprint descriptions

The shared UIBlueprintInspector in browser, copy, and paste modes adds a compact Auto-fill entry to the existing description header. Its options panel is an owned child of inspector.rectTrans, outside the scroll mask. On opening, actual entry corners and root-canvas bounds are converted into that parent's coordinates. The private placement method in InspectorControls prefers a position below the entry with their right edges aligned, flips above when needed, and clamps against canvas bounds; a panel too large for those bounds is closed. A Canvas.willRenderCanvases subscription follows the entry after native layout and scrolling only while the options are open; hiding the entry or scrolling it completely outside its viewport closes the popup. Native fields, groups, anchors, and scroll height remain owned by the game. Closing, disabling, and destruction unsubscribe the positioning callback and remove only owned controls as appropriate.

The options use a title and the actual native X subtree, then a 20-pixel proliferation checkbox row, a 28-pixel production-basis row with help, and one 30-pixel Generate action at the lower right. Width is measured from the localized labels and choices. The normal 154-pixel panel gains 54 pixels when the two 24-pixel dropdown rows open, moving the footer below the list. The cloned X must receive a new Button.ButtonClickedEvent: its source has a persistent callback to the original inserter window that RemoveAllListeners does not remove.

The production-basis selector clones the star-detail combo. Disable and remove the clone root's inherited Localizer before assigning owned dimensions: that source component writes a star-panel-specific width on enable and language changes. Turn off the clone's UIComboBox.autoWidth before populating items, stretch its main button within the owned root, and align its selected and template text to the left. Preserve the native dropdown, content, item-template, and selection anchors; native UIComboBox.SetState controls row heights and the native row event selects an item before closing the list. These adjustments belong to this selector rather than the shared combo helper.

Handle dismissal in the owning inspector's _OnUpdate postfix. Processed VFInput.escape respects an earlier native message-box handler; close an expanded dropdown first, otherwise close the popup, then consume Escape before later native window-closing handlers run. Left, right, or middle clicks outside the popup, entry, and open dropdown close the options while preserving the clicked native target's normal behavior. Successful generation, blueprint replacement, and inspector closure also close the options.

Each inspector open resets the basis to Final-product output, retaining existing calculation behavior; selecting Lowest intermediate throughput opts into BottleneckIntermediate for generation. The checkbox initially reflects the blueprint's Spray Coater prefab capability and tracks content changes until manually changed in the current editing session; changing it does not modify the blueprint. Generation captures only blueprint.buildings with BlueprintSelectionReader.FromBlueprint on the game thread, then runs FactoryBlackBoxAnalyzer against the captured catalog. A successful bottleneck solve supplies classification and steady-state balances directly; the original classifier runs only in final-product mode or after an unavailable bottleneck result. The maximum supported proliferation level applies while each building keeps its acceleration or extra-products mode. Input coating is assumed to be supplied externally; no spray routing or spray consumption is inferred from the Spray Coater.

BlueprintDescriptionFormatter builds replacement multiline blueprint.desc text in this order: optional Missing: and Excess: lines for intermediate shortages and excess classified by the selected production basis; Input: for external inputs capped by downstream demand; Output: for ordinary final products and necessary coproduct surplus; and Research: for positive net matrix production accepted by a selected research-mode lab. Each warning category has one label followed by comma-separated items; warnings do not repeat in Input, and a matrix on Research does not repeat in Output. It uses SteadyStateExternalSupply for complete and independently known partial inputs, labeling partial values as known portions. The assumed lab adds no numerical matrix consumption or external input; other buildings' known matrix demand is subtracted from the Research rate. Omit each empty line, including Research when no produced matrix remains. A single optional Power custom field separates factory and configured logistics consumption, omitting categories with no demand and removing the field altogether if neither consumes power; a present but unknown category displays Unknown rather than zero. Material rates remain items per minute even though the description labels omit the unit. Rates are rounded only for display. Large displayed rates use the largest exact K/M/G suffix with at most one decimal place (for example, 1,234,000 becomes 1,234K); if no suffix preserves that display precision, keep the ordinary number. Numbers with four or more integer digits use comma thousands separators, including coefficients before material or power units. Rates are ordered by item ID within each category, and use native item icon/name tags with comma-separated entries inside each description line. Uncertain final-product, overbuild, or coproduct conclusions are omitted. Veins and other scene objects are not blueprint entries or requested parameters.

BlueprintDescriptionFields matches only exact English or Simplified Chinese power field titles, updates or removes matching power fields, and collapses duplicate matches; all other fields, including input/output custom fields, stay intact. The inspector first collects pending custom-field edits, checks the native 2,000-character description limit and kMaxFieldCount, and applies native ExternalFieldEscape and ExternalFieldUnescape rules to the remaining power field. An invalid blueprint, unavailable catalog, failed calculation or bottleneck basis, malformed fields, overlong description, or insufficient capacity does not overwrite the description or generated fields. A successful update replaces the original description, synchronizes its native input control, and refreshes the inspector and share-code preview through the native modification path, leaving save and copy actions to the native buttons. Native Refresh owns the groups' positions and scroll height. Refresh(forModify: true) does not reload descTextInput, so assign it explicitly. BlueprintData.Validate strips newlines from custom fields, so multiline text belongs only in the main description. Recheck these inspector behaviors against the original DLL after game updates. The formatting and field updater remain pure-managed so ProductionCheck can verify them without loading Unity. See blueprint description validation for native layout evidence and manual compatibility checks.

Special-process settings

All parameters below are numbers in a building snapshot's OperatingParameters. A live capture supplies available values from the selected factory; either capture path may need supplementary context. Do not infer missing resource coverage, inventory contents, research technology, orbit readiness, or sandbox settings. Planner callers supply recipe-specific values through OperatingParametersByRecipe, including for synthetic recipes.

Facility Settings and behavior
Fractionator A fractionation recipe, CirculatingItemsPerMinute, and StackSize. The throughput limit is 30 cargo per second times the stack size, or 1800 * StackSize items per minute. Only successful conversions consume inputs; circulation changes throughput and power without becoming an external material input. The native power formula uses items per second, not per minute.
Energy exchanger Mode0: charging 1, discharging -1, idle 0. Charging converts empty accumulators to full ones and draws grid power. Discharging converts them back and is reported as discharge capacity, not generation. Coating accelerates both directions and is preserved on the output accumulator.
Ray receiver Mode0: 0 for grid generation or its native photon item ID; LensItemId: zero or a compatible catalyst; SolarEnergyLossRate: technology loss fraction. Missing loss leaves photon flows available but Dyson power incomplete. Without a selected receiver, the planner keeps lens-free photon flows and leaves power incomplete; lens wear and speedup require a receiver. Ideal full illumination and warmup use the native 2.5 warmup factor, eightfold photon mode energy, and one lens per 36,000 game ticks. Grid generation and Dyson demand are separate.
Renewable generator Wind, solar, and geothermal use ideal standard conditions and their rated generation. Local wind strength, day/night illumination, and geothermal ground heat do not modify this full-load model.
Miner or water extractor ResourceItemId, MiningSpeedMultiplier, and VeinCount or OilUnits for the matching resource. Optional MachineSpeedFactor defaults to 1; live capture records the raw miner speed divided by 10,000, and prebuild and blueprint captures read an Advanced Mining Machine's stored speed setting. The native speed damper only throttles backed-up output, so full load assumes its unobstructed value of 1. Output scales by machine speed; power uses ratio = MachineSpeedFactor * MachineSpeedFactor and workingWatts * ratio + idleWatts * (1 - ratio).
Gas collector GasCount, GasTotalHeat, MiningSpeedMultiplier, and each GasItemId{n} and GasSpeedPerSecond{n}. Native self-power recovery and collection technology scale all gas outputs, which are reported per minute. Collector working energy reduces recovered gas; it is not counted again as grid consumption.
Fuel generator FuelItemId compatible with the generator. Artificial stars also require the native boost mode Mode0, with BoostEnabled when it is set. Output and burned fuel follow the native fuel type and proliferation rule.
EM-rail ejector or vertical launching silo LaunchAvailable plus the native boost mode (Mode1 for ejectors, Mode0 for silos), with BoostEnabled when it is set. An available ideal target consumes one ammunition item per completed charge/cooldown cycle. Proliferation changes both launch speed and working power. LaunchesPerMinute is separate from item production.
Research-mode lab ResearchMode = 1; precise research needs TechId and ResearchSpeed, neither stored in a blueprint. Blueprint capture sets ResearchMatrixSink: a single lab can receive all six native matrix types produced by the selection, without a numerical input or hash-rate estimate. All labs count at full working power even when technology is missing or invalid; apply the supported proliferation power factor or base power when no spray level exists. Precise native matrix proliferation increases hashes and power, not matrix input per base hash.

Native blueprint paste applies a stored boost mode only while sandbox tools are enabled, so BoostEnabled states whether the boost is actually applied. Live capture reports the applied boost of ejectors, silos, and artificial stars; blueprint callers must supply it for boosted buildings.

The ejector and silo assume a usable orbit or node when LaunchAvailable = 1; their native geometric visibility and construction schedules are outside this full-load model. Planner power excludes logistics charging, transport, and mecha charging; the fixed-building report includes charging limits for selected logistics facilities but does not simulate transport energy. Auxiliary power must come from an explicitly supplied list.

CheatEnabler migration

The belt-signal generator uses ProductionPlanner material reports, not its former recursive ingredient table. Its caller-side preset keeps the legacy recipe preference: explicit recipes, including the rare-resource alternatives, supply items first through ProductionRecipe.Explicit, except explicit recipes that consume their own product, such as X-ray Cracking and Reforming Refine; natural items stay raw. The preset also chooses a proliferator with valid captured Proto capabilities and permits legacy natural-source boundaries only when those item IDs exist in the catalog. For each generated target unit, it records upstream gross production plus external imports, subtracts the already delivered target, and applies gross consumption independently. Each belt keeps separate fractional progress for production and consumption, while per-unit reports are cached by item, spray configuration, and catalog. ProductionCatalogService.Changed invalidates cached reports and refreshes existing belts; clearing the catalog drops their derived statistics without accessing unloaded factory objects. The game logic tick applies cached rates only. Signals can change inside the tick, for example when drones finish a blueprint, so a cache miss queues the belt and the planner runs from the next frame update. Request construction, calculation, and report conversion fail softly: if data is missing or calculation fails, only additional upstream statistics pause and a warning explains why; item generation and its own configured count switch remain unchanged.

Validation

Use compilation, the synthetic game-free checks, and static review for development checks:

dotnet build UXAssist/UXAssist.csproj -c Release --no-restore
dotnet build CheatEnabler/CheatEnabler.csproj -c Release --no-restore
dotnet build UniverseGenTweaks/UniverseGenTweaks.csproj -c Release --no-restore
dotnet run --project UXAssist/tools/ProductionCheck/ProductionCheck.csproj -c Release
git diff --check

ProductionCheck compiles the pure-managed production sources and the belt-signal statistics with hand-built catalogs. Update its expectations together with any intended change to production rules.

Compare special mechanics against method bodies in the original DSP DLL; the publicized repository reference is not an implementation source. Builds and DLL inspection do not establish in-game correctness. In-game acceptance is manual; automated tests and save parsing are not required.

Use a test game for the following manual checks. Compare full-load rates only with sufficient inputs, power, and output capacity; do not compare a throttled statistics window with theoretical capacity.

  • Check ordinary production and mining against native cycle periods and the per-minute UI. A 60-tick recipe at unit speed completes 60 cycles per minute before proliferation.
  • Capture assemblers in acceleration and extra-products modes, nonproductive recipes, prebuilds, and stacked labs. Confirm that each captured mode and building count matches the selection.
  • Select logistics stations, distributors, and battle bases with different charge-power settings. Compare live, prebuild, and blueprint maximum demand with their native charging sliders; confirm that advanced miners and gas collectors do not gain an additional charging term.
  • Supply fractionator circulation and stack context. For native 1% fractionation with fully sprayed input, 1,800 circulating items per minute yield 36 conversions per minute; at stack size 4, 7,200 circulating items per minute yield 144. Check throughput-dependent power separately.
  • Request full accumulators and critical photons through the catalog's default synthetic routes. Confirm that missing building or receiver-loss settings produce incomplete power rather than an invented result.
  • Charge and discharge sprayed accumulators, then consume or deliver them with spraying enabled. Confirm acceleration in both directions and no repeated spray charge for inherited coating. Compare self-spraying enabled and disabled.
  • Select miners at different machine speeds, including one with a backed-up output, a gas collector, and renewable generators. Check native miner power scaling, full-load miner output regardless of the output backlog, per-minute gas output without added grid demand, and ideal rated renewable power rather than local conditions.
  • Select ray receivers in both modes, fuel generators, ejectors, and silos. Toggle proliferation and compare working power, generation, accumulator exchange, and Dyson demand as separate quantities. In a sandbox game, capture boosted artificial stars and launchers, and confirm that blueprint analysis of boosted buildings requires BoostEnabled.
  • Remove an upstream producer from a mixed production selection. Confirm that downstream capacity is unchanged and the missing material appears as required external supply. Add one producer more than downstream demand needs, and confirm that only that whole building's output is reported as excess.
  • In browser, copy, and paste inspectors, check that the localized options follow their header entry when scrolling and use the available canvas space. Verify the native X, outside-click dismissal, and Escape priority, including an expanded dropdown and a native message box. Confirm both dropdown rows fit above the footer, options close after successful generation or inspector closure, and native settings and description fields retain their positions. Check Spray Coater defaults and manual overrides, generate twice and at the 20-field limit, and verify pending edits, unrelated fields, native item tags, and save/copy behavior.
  • Compare both production bases on an undersupplied chain, uneven recipe ratios, shared intermediate branches, and a joint-product chain. Final-product mode must retain rated final outputs and expose intermediate shortages. Bottleneck mode must scale final outputs together, update raw inputs to the same throughput, and leave no internal shortage for a complete, balanceable chain. Confirm unused intermediate capacity and necessary coproduct output remain distinct, and that power stays at the same full-load estimate. Test a chain without internal intermediates, missing building settings, and a cycle without a final outlet; an unavailable bottleneck basis must preserve existing description and fields.
  • Place one research-mode lab alongside one or all six matrix production chains. Confirm the matrices' positive net production appears only in the Research line, other final products stay in Output, and known in-blueprint matrix consumption reduces the Research rate. Do not fabricate lab matrix imports, excess, or an estimated lab consumption rate; change current technology, add more labs, and toggle proliferation to check matrix routing stays independent while full working power updates. Without the lab, normal matrix output and overbuild rules resume.
  • Combine planner targets with shared coproducts, explicit raw-material boundaries, and alternate selected recipes. Confirm material conservation, shared surplus reuse, and no introduction of unselected recipes.
  • Toggle belt-signal proliferation and reload a game. Confirm that existing belts use the new catalog, item generation continues, and fractional production and consumption statistics remain independent.