Requisition system register
Requisition
Keep confirmed currency and card workflow separate from unsupported costs, unlock tables, and optimization claims.
Use the requisition database
This register is generated from the current validated snapshot, not copied from a competitor list. Every requisition row must point to a current entity version and at least one retained source. Evidence labels describe what the source can support; they are not popularity scores and they do not make an unknown field true.
Open a record to inspect its factual fields, verification date, source locator, patch scope, aliases, and related field files. Missing values remain missing. If a record is single-source, conflicted, or stale, it moves to Community Radar and cannot create an indexable detail page or feed an operational calculator.
Requisition records document the visible system boundary and linked cards. Exact costs, unlock timing, and optimization advice require stronger current-client evidence.
Current snapshot
1 qualified requisition records
- Requisition systemOfficial Requisition
The official interface shows Requisition Credits spent through a physical card machine inside the turret.
Also listed as: Requisition credits, Card machine
- Currency label
- Requisition Credits
Operator method
Work with the requisition register
Start from the objective you are trying to solve, then open the narrowest relevant requisition record. Read the summary and qualified facts before following an alias, relation, or outside source. Keep the record name, verification date, snapshot checkpoint, and any current-client value on the same note. This makes it possible to tell which part came from the public requisition database and which part you observed during the present session.
Use related records as a navigation graph, not as permission to invent missing mechanics. A mission can link to an achievement, ammunition can link to a target role, and a card can link to requisition only when the retained relation states that connection. Open both records and compare their individual evidence boundaries. If a required field appears on neither page, check the current client or leave it unknown instead of carrying a number across categories.
After an official patch, review the records touched by changed names, interfaces, rules, or content. Stable descriptive facts may remain useful, but source-scoped values need a fresh check before automation republishes them. If evidence becomes stale or contradictory, the public route must fail closed and the item moves to Radar. That maintenance rule lets this requisition register grow without requiring manual approval for every unchanged record.
- Open one qualified record and identify the exact supported field.
- Follow explicit relations only when they answer the current task.
- Keep session observations separate from public database facts.
- Recheck build-sensitive values after a patch checkpoint changes.