Armored Fist
1994 video game
Armored Fist is a video game developed and published by Novalogic for the PC. It was followed by Armored Fist 2 and Armored Fist 3.
Gameplay
Armored Fist is a tank simulation and strategy game involving the armed forces of both the United States and the Soviet Union.
Development and release
Armored Fist was developed by American studio NovaLogic. Produced and designed by the company's head John A. Garcia, development began in 1990. Garcia found that the state of computer technology at the time allowed for more realistic tank warfare such as strategic terrain masking. He explained that the whole team was "keyed into the process" of researching tanks in books, television, and other popular media. "It's not uncommon to come into work at NovaLogic and have an artist run in with a tape from The Discovery Channel with the first ever recording of a certain tank firing," he said. "The entire staff will analyze it over and over for art perspectives, design ideas, and so forth." The developers even spent a day learning about tanks at Marine Corps Air Ground Combat Center Twentynine Palms.
The game originally went by the working title Battlefield 2000 with development overlapping with other NovaLogic projects including the combat helicopter simulator Comanche: Maximum Overkill and the science fiction mech shooter Ultrabots. The company had planned to release the Armored Fist in mid‐1993 using polygon graphics, but it was delayed when this was substituted with the company's Voxel Space, a raster graphics engine designed by Kyle Freeman.
“Armored Fist” enters the record as 1994 video game. Crown Archives preserves that source wording while asking what Armored, Fist and video can confirm, complicate or overturn.
Why this record matters
“Armored Fist” is worth following because a concise public description often conceals a longer documentary argument. Here, Armored, Fist and video provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Apr 3, 2026. The linked authority identifier is Q55604214. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1990, 2000 and 1993.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Armored Fist”, its source revision and the description used here.
- Expand the search: follow Armored Fist primary sources, Armored Fist archive and Armored research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Armored Fist”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Armored Fist” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.