Pac-Man 256
2015 endless running video game developed by Hipster Whale
Pac-Man 256 is a 2015 endless runner video game developed by Hipster Whale, 3 Sprockets and Bandai Namco Studios Vancouver, and published by Bandai Namco Entertainment. The game is part of the Pac-Man series and is inspired by the original Pac-Man game's infamous Level 256 glitch, as well as Hipster Whale's own game Crossy Road, which previously featured a Pac-Man mode.
The game was originally released for iOS and Android devices on August 19, 2015 in commendation of Pac-Man's 35th anniversary. An enhanced version, Pac-Man 256+, was released for the Apple Arcade subscription service for iOS, macOS and Apple TV.
Gameplay
Pac-Man 256 sees the players take control of Pac-Man as he continues across an endless maze, collecting dots and power-ups while avoiding enemy ghosts. The game ends if Pac-Man comes into contact with a ghost or falls behind and is consumed by a chasing glitch at the bottom of the maze. Eating 256 dots in a row awards the player a blast that clears all on-screen enemies. Along with power pellets, which enable Pac-Man to eat ghosts, Pac-Man can equip and obtain various power-ups such as lasers, tornadoes, and clones to attack the ghosts, as well as collect score-multiplying fruit. Up to three power-ups can be equipped. Power-ups are unlocked by waiting 24 hours after unlocking a power-up. In the console and PC versions, they are unlocked by eating a specified number of Pac-Dots.
Begin with the source’s own compact description: “Pac-Man 256” is 2015 endless running video game developed by Hipster Whale. The dossier treats that line as a proposition to test through Pac-Man, endless and running, not as a finished interpretation.
Why this record matters
The phrase “2015 endless running video game developed by Hipster Whale” 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.
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 16, 2026. The linked authority identifier is Q21061092. 3 of 3 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2015.
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 “Pac-Man 256”, its source revision and the description used here.
- Expand the search: follow Pac-Man 256 primary sources, Pac-Man 256 archive and Pac-Man 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 “Pac-Man 256”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Pac-Man 256” 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.