Turret control register
Controls
Keep current control labels, units, and transfer checks together before operating the turret.
Use the controls database
This register is generated from the current validated snapshot, not copied from a competitor list. Every control 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.
Control records preserve visible labels and units, then place them inside a transfer check. They do not substitute an unverified ballistic formula for the current game calculator.
Current snapshot
1 qualified controls records
- Gun elevation controlsOfficial Control
The turret exposes separate manual elevation controls and readouts for the left and right guns.
Also listed as: Elevation wheels, Gun elevation
- Observed gun readouts
- Left gun elevation, Right gun elevation
- Displayed angle unit
- Degrees
Operator method
Work with the controls register
Start from the objective you are trying to solve, then open the narrowest relevant control 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 controls 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 controls 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.