Heavy Fire
video game series
Heavy Fire is a series of on-rails arcade shooter video games developed by Polish video game developer Teyon between 2010 and 2013 and Anshar from 2018 to present. The series includes five games: Heavy Fire: Special Operations (2010), Heavy Fire: Black Arms (2011), Heavy Fire: Afghanistan (2011), Heavy Fire: Shattered Spear (2013), and Heavy Fire: Red Shadow (2018).
Games
Special Operations
Heavy Fire: Special Operations is an on-rails arcade shooter developed by Teyon for the WiiWare and Nintendo 3DS. It first appeared as a WiiWare title in North America on July 26, 2010 and in the PAL region on December 31, 2010. An updated version for the Nintendo 3DS, called Heavy Fire: Special Operations 3D, was released on September 13, 2012 in North America, and on October 25, 2012 in the PAL region for the Nintendo eShop.
Heavy Fire: Special Operations is a shooting game set in Somalia where players join the elite special force fighting against terrorists. A player starts the game as a Private equipped with a pistol and his goal is to eliminate opponents and gain as many points as possible to advance in the military hierarchy. Players can get several bonuses and perform combos like ‘Leader Kill’, ‘Demolition Man’, ‘Lord of Destruction’ and others, helping to achieve a higher score. Missions can be run using the light-gun from the ground, Humvee or Blackhawk.
There are 6 ranks to achieve: Private First Class, Corporal, Sergeant, Staff Sergeant, Master Sergeant and Sergeant Major. Each of them is linked to one of 7 specific guns, so the more points are gathered, the better the weapon can be used.
Begin with the source’s own compact description: “Heavy Fire” is video game series. The dossier treats that line as a proposition to test through Heavy, Fire and video, not as a finished interpretation.
Why this record matters
The phrase “video game series” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jun 18, 2026. The linked authority identifier is Q25413149. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2010, 2013, 2018 and 2011.
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 “Heavy Fire”, its source revision and the description used here.
- Expand the search: follow Heavy Fire primary sources, Heavy Fire archive and Heavy 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 “Heavy Fire”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Heavy Fire” 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.