File:H5G-Camo.png: Difference between revisions
From Halopedia, the Halo wiki
(Fred-104 uploaded a new version of File:H5G-Camo.png) |
(Oops, wrong map) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
[[ | {{file info | ||
|summary = A Spartan with [[active camouflage]] active on the map [[Fathom]]. | |||
|game = Halo 5: Guardians | |||
|type = screenshot | |||
|subject = weapon | |||
|source = self | |||
}} | |||
[[Category:Images of Halo 5: Guardians multiplayer Spartans]] | [[Category:Images of Halo 5: Guardians multiplayer Spartans]] | ||
[[Category:Images of MJOLNIR Centurion]] | |||
[[Category:Images of MJOLNIR Vigilant]] | |||
[[Category:Images of Domotos-pattern energy sword]] | |||
[[Category:Images of M6H2 magnum]] | |||
[[Category:Images of Qothal]] | |||
[[Category:Images of Fathom]] |
Latest revision as of 21:17, August 18, 2024
Summary[edit]
File information | |
---|---|
Summary | A Spartan with active camouflage active on the map Fathom. |
Type | Screenshot of weapon |
Game | Halo 5: Guardians |
Source | File created by the uploader |
License | This file is subject to copyright. Copyright is most likely held by the company that published the game or media portrayed in the image. Halopedia's use of this work qualifies as fair use under United States copyright law, or the author's permission is given. It is used on the wiki only in the belief that the information the image portrays is designed to be an accompaniment to playing the game or media, and its use here will not:
|
File history
Click on a date/time to view the file as it appeared at that time.
Date/Time | Thumbnail | Dimensions | User | Comment | |
---|---|---|---|---|---|
current | 21:04, August 18, 2024 | 1,920 × 1,080 (3.34 MB) | Fred-104 (talk | contribs) | ||
03:28, August 28, 2016 | 1,920 × 1,080 (3.43 MB) | Sith Venator (talk | contribs) | Category:Images of MJOLNIR Venator Category:Images of SPARTAN-IVs |
You cannot overwrite this file.
File usage
The following page uses this file: