Mage Knight: Apocalypse
2006 video game
Mage Knight: Apocalypse is an action role-playing game developed by InterServ International and released for Windows alongside companion title Mage Knight: Destiny's Soldier for the Nintendo DS in September 2006. The video game is set in the same universe as the related collectable miniatures game, Mage Knight.
Plot
The campaign takes the characters through a world known as The Land, where various fantasy races are at war. The Solonavi, a group of spirit masters fear the world will come to an end if the war is not stopped. Throughout the game a group of heroes is formed, known as the Oathsworn. The Oathsworn set out to destroy the source of the evil force to save the world from destruction by recovering five "Aspects of Apocalypse" scattered throughout The Land.
Characters
Janos the Dwarf (melee, gunner, explosives)
Tal the Elf (fighter, healer, ranged attacker)
Kithana the Nightblade (assassin, necromancer, vampire)
Sarus the Draconum (earth, fire, wind magic)
Chela the Amazon (bear/melee, eagle/ranged, jaguar/agile)
Gameplay
Players assume the role of one of five playable characters, each with three separate skill paths. Skills are developed depending on playstyle, rather than manual selection of a skills. Individual skills and attributes gain experience and increase in level as they are used. As the game progresses, the player is partied with the other members of the Oathsworn and are able to control the other characters with basic commands (attack, follow, stop).
This brief starts where responsible research should: with the source description of “Mage Knight: Apocalypse” as 2006 video game. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as 2006 video game. Its deeper value depends on whether names, dates, institutions and citations support that framing.
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 Dec 12, 2024. The linked authority identifier is Q108809855. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2006.
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 “Mage Knight: Apocalypse”, its source revision and the description used here.
- Expand the search: follow Mage Knight: Apocalypse primary sources, Mage Knight: Apocalypse archive and Mage 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 “Mage Knight: Apocalypse”?
- 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 “Mage Knight: Apocalypse” 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.