| Search |
|---|
| ID | Rating | Category | Description | Screenshot | Date |
|---|---|---|---|---|---|
| 5969 | 😟 | Suggestion | Current Pain Points In many-to-many setups (e.g., 10 suppliers × 10 consumers), configuration complexity explodes and scaling becomes very expensive to operate. When Behavior logic and Transport Route logic are used together, the resulting behavior is often hard to predict and control. It is difficult to duplicate a full production line including Bots and their role settings via Blueprints, which slows down horizontal expansion. Management relies heavily on per-unit hidden IDs, while area/group-level visibility and control are limited. Repro Example (Short) Build suppliers A/B/C/D/E and one aggregate storage Z. Try to enforce fair pickup (round-robin style). In practice, some suppliers are drained less often, inventory accumulates unevenly, and total throughput does not scale as expected. Adding/removing sites requires repeated manual parameter assignment, which becomes time-consuming. Requested Improvements Add UI-level Area/Group definitions so we can configure flows like Group A -> Storage Z. Provide an explicit priority mode for control conflicts: Behavior-first vs Route-first (with visible conflict handling). Allow Blueprint-level bulk copy of buildings + Bot roles/settings together. Add standard scheduling nodes/policies for many-to-many logistics (e.g., round-robin, weighted, least-stock-first). Expected Impact Significant reduction in setup/maintenance time for mid- to large-scale factories. Better readability and easier onboarding (lower learning curve). Higher long-term retention by making scaling less painful. Practical Posting Tips Split this into 4 separate posts (one for each pain point) to improve triage and adoption. In each post, include: 3-step reproduction Expected vs Actual behavior Measured impact (e.g., extra setup time in minutes) Keep the tone technical and reproducible rather than emotional. | 2026-02-12 09:41:09 |
| ID | Reply | Author | Date |
|---|