AC6 ASSEMBLE TOOL /about
This page introduces AC6 ASSEMBLE TOOL, explains why it exists, highlights the current features—including the new parts exploration workspace—and outlines what comes next so that pilots can rely on the application while planning their builds.
What Is AC6 ASSEMBLE TOOL?
AC6 ASSEMBLE TOOL is an unofficial companion web application for ARMORED CORE VI FIRES OF RUBICON. It consolidates the game’s extensive parts catalogue and helps pilots reach the builds they imagine through a platform that emphasizes simplicity and repeatable results.
The project focuses on making build exploration effortless. Instead of complex dashboards or heavy simulations, the interface keeps interactions clean and responsive so that users can sketch an idea, lock a few essential components, and immediately see a playable assembly on any device, including smartphones.
Responsibilities are now split between the assembly page and a dedicated parts list. Slot-specific exploration and final build adjustments stay in sync through shared URL queries, so you can bounce between pages without losing context—even on mobile. There is still no hidden theme detection or automatic goal setting: pilots combine filters and locks intentionally, and every state can be shared verbatim through query parameters for collaborative planning.
Why the Tool Exists
In the ARMORED CORE series, inspiration often strikes outside the game. AC6 ASSEMBLE TOOL aims to make it possible to experiment with loadouts anywhere and at any time, without waiting to boot a console or sit in front of a PC.
Every major regulation update forces pilots to rebuild their understanding of parts performance. Historically that knowledge lived in spreadsheets and forum posts, which meant information went stale quickly and recreating the same steps was hard. By storing parts data inside the repository and when necessary refreshing it with visible history, the tool keeps changes transparent and easy to follow.
The development approach prioritizes reproducibility. All calculations are based on public information and community-driven testing; in accordance with FromSoftware’s terms of use, no game data is extracted through reverse engineering. The earliest use cases revolved around “manufacturer-only” runs, attribute-specific restrictions, and pure random assemblies, and those playful constraints continue to guide the project. At the same time, campaign efficiency and role-play centric builds benefit from the same structure.
Key Features and Play Styles
The current feature set was shaped by observing how pilots iterate on their machines: lock core ideas, explore alternatives, validate status numbers, and share results.
Random assembly generation is primarily designed for challenge runs. Whether you limit yourself to a single manufacturer, an elemental affinity, or simply want the thrill of a surprise loadout, you can anchor the parts that matter and let the remaining slots roll. Many users also treat it as a spark for discovery, picking out the best outcomes to refine manually.
The parts list page keeps filters scoped per slot and folds everything into a single workspace: numeric ranges for weight or EN load, name search with match modes, multi-select manufacturer and category filters, sorting, and favorites. Every change is serialized back into the URL, so returning to the assembly page preserves the same candidate pool and context.
Keeping Regulations in Sync
Trust in a build planner depends on how quickly it reflects balance updates. AC6 ASSEMBLE TOOL follows the latest regulation and documents each refresh so that users know exactly which values drive their assemblies.
Whenever a regulation changes, the site publishes the update date and the major adjustments. New or modified parts are highlighted through release notes and social channels so pilots can adjust without digging through multiple sources.
At the moment the tool shows the combined status of your full assembly as soon as parts are selected. Detailed per-part inspection is still under development, together with comparison views that will let you switch between regulations and examine how individual components differ across versions.
User Experience and Accessibility
The interface is built to guide first-time visitors while staying fast for veterans who iterate repeatedly. Dense information is laid out along a natural reading flow, reducing the need for constant scrolling or context shifts.
Core actions are grouped by use-case order: define constraints, inspect candidates, save or share. Modal triggers live together on the navigation bar, minimizing visual noise while keeping advanced tools close at hand. Usage metrics—stripped of any personal identifiers—highlight confusing steps so that improvements are always informed by real interaction patterns.
Accessibility checks cover contrast, typography, and keyboard navigation. ARIA attributes are gradually being refined, and the initial build already prepares the infrastructure needed to add more languages through SvelteKit’s context-backed i18n system.
Security and Privacy Approach
Even in a hobby project, privacy matters. AC6 ASSEMBLE TOOL is deliberately designed without long-term personal data storage.
All inputs stay in the browser; the application reads static data and never sends assemblies to a server. Sharing relies exclusively on query parameters, so players keep full control over what they disclose. Dependencies are pinned and go through a checklist before upgrades land, limiting the risk posed by vulnerable packages.
Diagnostic logs use structured JSON but omit personally identifiable information such as IP addresses. Only the maintainer has access to the logs, and external links are wrapped with safe defaults like `rel="noopener noreferrer"` to guard against clickjacking vectors.
Community Feedback Channels
The tool grows alongside its users. Feedback loops are intentionally simple so anyone can report issues or pitch ideas.
Bug reports and feature requests share a dedicated in-app entry point that leads to separate forms. Submissions are triaged on a planning board with visible priority and scope, and answers that benefit everyone are published as FAQs to reduce repeated questions.
The GitHub repository uses issue and pull-request templates to streamline contributions. Clear contributing guidelines describe coding conventions, review expectations, and how to demonstrate build scenarios when proposing changes. This ensures that additions—whether from the maintainer or the community—arrive with the same level of care.
Roadmap Highlights
The immediate focus is on better discovery tools, followed by richer collaboration features that help squads plan together.
Near-term milestones emphasize test coverage and performance. Integration and end-to-end suites will validate the round-trip between the parts list and assembly pages, while profiling data will guide memoization, virtualization, and other optimizations for filter application and slot switching.
Further ahead, visual aids that map part synergies and tactical indicators are under evaluation. The long-term vision explores exposing the domain logic through an API so that community-made tools can integrate with the same dataset. Each stage of the roadmap is validated with user surveys and anonymized usage patterns to confirm that the direction still matches what pilots need.