Star Wars: Battlefront
series of video games
Star Wars: Battlefront is a series of first- and third-person shooter video games based on the Star Wars franchise. Players take the role of characters from the franchise in either of two opposing factions in different time periods of the Star Wars universe. The series was launched in 2004 by LucasArts with Star Wars: Battlefront, developed by Pandemic Studios for LucasArts. The game received positive reviews and sold well. In 2005 Pandemic developed a sequel, Star Wars: Battlefront II, which was also critically and commercially successful.
The games were followed by Star Wars Battlefront: Renegade Squadron (2007) and Star Wars Battlefront: Elite Squadron (2009) for handheld game consoles and Star Wars Battlefront: Mobile Squadrons (2009) for mobile devices. LucasArts made several attempts to develop a third major Battlefront game, but no projects were released before The Walt Disney Company's acquisition of LucasArts. Subsequently, Electronic Arts (EA) acquired an exclusive license to develop console Star Wars titles from Lucasfilm, leading to the development of a reboot under DICE. Titled Star Wars Battlefront, the game was released on November 17, 2015. A sequel, Star Wars Battlefront II, was released on November 17, 2017, and was co-developed by EA DICE, Criterion Games, and Motive Studio. A collection of the first two entries in the original series was ported to modern platforms by Aspyr, and was released as Star Wars: Battlefront Classic Collection on March 14, 2024.
The public source identifies “Star Wars: Battlefront” as series of video games. This brief keeps that definition visible, then builds a research path around Star, Wars and Battlefront.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Star Wars: Battlefront”, the useful work is to connect “series of video games” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jul 19, 2026. The linked authority identifier is Q54869. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2004, 2005, 2007 and 2009.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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 “Star Wars: Battlefront”, its source revision and the description used here.
- Expand the search: follow Star Wars: Battlefront primary sources, Star Wars: Battlefront archive and Star 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 “Star Wars: Battlefront”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Star Wars: Battlefront” 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.