| [#60] |
Hey all,
Recently on the Discord, myself and a couple of others have been brewing a new project, which will be pretty wide-reaching if implemented in its current form. Consequently, I've written this forum post to make sure that those who don't frequent the Discord are able to get their opinions in, and aren't blindsided by the change.
To explain, I believe that while we are undoubtedly the best resource out there for Halo lore information and have competent coverage of most other areas, the gameplay aspect of our wiki is sorely lacking. To that end, I intend to spearhead a project to overhaul how our pages are organised and laid out with regards to gameplay. Under this proposal, all gameplay information for a given topic would be contained within a single page, rather than spread out across multiple related lore pages. This page would take the colloquial name of the subject as its title, and would take precedence over any other page that might already share that title (except in very exceptional cases where said page is more notable). Additionally, the lore pages relating to the topic would then be able to shed their gameplay information, including only a cursory ==Gameplay== section that links to the main gameplay page with Template:Main, freeing them up to focus entirely on lore.
To illustrate what this would mean in practice, let's examine the sniper rifle as an example, since it's the one I've been using on the Discord. Currently, we have the following pages (not including redirects):
There are a number of issues with this approach. First: if you're a user looking for general gameplay information about the sniper rifle, where do you go? All of the gameplay info is spread out across nearly 10 different pages, and worse, many of these pages use the lore designations as their titles. Consequently, readers who are unfamiliar with the lore will end up landing on the disambiguation page, and being forced to parse through a huge list of options to find the sniper rifle from the particular game they're looking for, and then click that link. Worse even still, they likely won't even find the gameplay page for that lore sniper rifle, because it's sequestered away in a tiny link at the very bottom of the page (we'll come back to that). This is not an ideal reader experience at all, and it only obfuscates the information we do have.
Regarding the gameplay pages specifically, they're also very poor quality. There seems to be little-to-no standardisation between them, and much of the information they contain is simply informal advice based on the experiences of editors - which isn't necessarily a bad thing, but more objective information would be ideal. The biggest issue with these pages, though, is how they're accessed. Typically, they're not linked to by any navboxes, and are usually only found by scrolling down to the trivia section of the relevant sniper rifle, where a linkbox template links to it. The result of this is not only that readers don't find these pages, but also that we don't! They're almost never found by editors, so they become outdated quickly and mistakes are never caught and corrected. Allow me to illustrate this problem with some quantitative data: the SRS99-S5 sniper rifle article received 658 unique page views in the last 30 days, the SRS99C-S2 got 633 and the SRS99D-S2 had 437. Collectively, their respective gameplay articles had 24. I think that speaks for itself.
Finally, the gameplay info shouldn't be split up by the in-universe weapon to begin with. We have to remember that as far as the casual player is concerned, the Halo sniper is the Halo sniper. They don't care about the SRS99, 99C, 99D, 99-S5, etc - they think of it as all the same weapon, and when looking for information about it, they'll just be searching something like "Halo sniper rifle" in Google. As a result, the way we currently arrange it is not at all helpful for them.
Under this proposal, the setup would instead be like this:
- Sniper rifle - A gameplay page, with a minimal lore section linking to the relevant articles.
- Sniper rifle (disambiguation) - A disambiguation page.
- SRS99 series - A lore page with a minimal gameplay section, just linking to the gameplay article.
- SRS99-AM sniper rifle - A lore page with a minimal gameplay section.
- SRS99C-S2 AM sniper rifle - A lore page with a minimal gameplay section.
- SRS99D-S2 AM sniper rifle - A lore page with a minimal gameplay section.
- SRS99-S5 AM sniper rifle - A lore page with a minimal gameplay section.
- M99 Stanchion - A lore page with a minimal gameplay section.
- M99A2S3 Stanchion - A lore page without any gameplay info (it's never been in a game - not confirmed, at least).
- Signature-suppressed anti-material rifle - A lore page with a minimal gameplay section.
- Unidentified sniper rifle - A lore page with a minimal gameplay section.
- Hard sound rifle - A lore page without any gameplay info (it's never been in a game).
The /Gameplay pages would be outright removed, as they would no longer be needed.
Not only does this reduce the strain on the lore pages - with them no longer having to contain much more gameplay info than "This is the sniper from ''Halo 4'' and ''5''. Go to [[sniper rifle]] for gameplay info." - but it also unifies the gameplay information, and puts it front-and-centre. Readers who are looking for gameplay info can now easily find it, and editors are more likely to see the page and hence more likely to maintain it.
So, what would this gameplay page look like? Well, I have laid out a skeleton for that I think the page would look like here. It contains all of the subheadings we usually have for gameplay information, and also has a "Universe and lore" section which will be used to give a brief and easily digestible (i.e. not a dense, lore-filled text wall) primer on the sniper rifles seen in the games (not those only seen in expanded media), allowing the reader to delve further into the lore should they so please. Additionally, I intend to include concrete statistics about the performance of the weapon in gameplay, including the magazine size, number of shots needed to kill various enemies, etc. I am open to suggestions on how to expand or improve this proposed layout - please let me know if you have any.
Now, as for which topics would get this treatment, I intend to do it for weapons, vehicles, grenades, equipment/armour abilities, friendly and enemy units, buildings in the Halo Wars games and units in the Halo Wars games (although these would share the page with the existing gameplay page on the vehicle/FPS AI unit, if one exists). I additionally intend to create new or overhaul existing pages on the mechanics in all of the Halo games, to ensure they are up to as high a standard as these new gameplay pages would be.
BaconShelf has also been prototyping an overhaul to the layout of map and level pages, which has been designed in tandem with this proposal to ensure consistency in the heading titles and in the way gameplay and lore info are presented.
Before rounding out, I'd like to address a few likely questions:
Q: Will the gameplay pages have their own infoboxes and navboxes?
A: Yes in both cases. I have yet to create an infobox for them, but I have created some example navboxes: Template:Navbox/Weapons/Gameplay and Template:Navbox/Vehicles/Gameplay. Feedback is welcome!
Q: What happens if there's only one in-universe topic correlating to a gameplay topic? Would they get different pages or would we merge them into one?
A: This would depend upon the particular situation. In the case of the sticky detonator, the M363 RPD has enough lore to make it worthy of its own page, separate from the sticky detonator gameplay page. However, something like the machine pistol from Spartan Assault does not have enough lore to justify two separate pages. Instead, all of the lore would be contained on the main machine pistol page. The same would be true of REQ variant pages. However, we would, of course, split them as soon as we receive enough lore to justify it.
Q: How would this interact with CIA391's hub page project?
A: If you don't know, CIA's hub page project intends to collate together general lore information about a given topic onto one page, rather than have it spread out across multiple pages for variants. It also provides a location for information about unspecified variants and whatnot which aren't notable enough for an "Unidentified X variant" page. For an example of a hub page, see Scarab. Having discussed the matter with CIA, we've agreed that in the case where the hub page and gameplay page would clash, the gameplay page would take precedence and the hub page would be given a suffix (current working suffix is (fiction) (subject to change, suggestions welcome) - so for the sniper rifle, you'd have Sniper rifle and Sniper rifle (fiction), the latter of which would be linked to in the universe and lore section of the former).
Q: Why restrict the size and depth universe and lore section on the gameplay page?
A: The primary target of these pages is more casual fans, who aren't here to read up on the lore. Consequently, while we absolutely do need to provide a gateway into the lore pages for the purposes of easy navigation, filling the gameplay page's universe and lore section with a huge text wall just forces the average reader to scroll past to get to what they're actually looking for. The function of the universe and lore section is to act as an entry point into the wider lore on the subject for someone potentially new to the universe as a whole, rather than to barrage them with all the lore info they could possibly want.
Q: If I support this proposal, will I be forced to help implement it?
A: Nope! I'm happy to take the brunt of the work for this project if necessary, as I think it is critical to the future of the wiki. However, if you're willing to pitch in and lend a hand, I would absolutely love the help :)
Apologies for the text wall, but I wanted to outline absolutely everything from my motives to my proposed changes, in as clear a way as possible, to make sure everyone fully understands. Feedback is welcome - don't hesitate to contact me if you have suggestions or criticisms. I intend to start work on this within the next week or so, as soon as I've cleared off my current to-do list.
–  Dab1001 (talk • contributions) 
Posted by Dab1001 (administrator) on June 15, 2020 at 23:26.
Edited by Dab1001 (administrator) on June 16, 2020 at 00:19. |
|
As stated in previous discussions in Discord (and hopefully evident given I'm spearheading a somewhat parallel project to this one), I fully support this initiative.
Posted by BaconShelf (administrator) on June 16, 2020 at 00:18.
Edited by BaconShelf (administrator) on June 16, 2020 at 00:19. |
| I support this proposal in general, though that I don't know if the gameplay sections on the individual lore pages needs to be quite so nerfed. I don't think they should have nearly the amount of game info they do now or should go to into too much detail, but I think there is room for some general info. As an example, the "SRS99-S5 AM sniper rifle" gameplay section could have a few sentences about the levels its found on or a few other minor details about how it functions in game or it's REQ variants (especially if we aren't going to do pages for REQ variants that don't have much lore related to them).
I say this for two reasons mainly, one being that I think there some specific information that might be equally relevant on the individual's rifle page. The second is the inverse to how gameplay people reading the blurbs of lore on the Sniper rifle page and getting more interested in the story info; maybe some of the lore readers might have their interest piqued from reading some gameplay info.
| Posted by CMDR RileySV (administrator) on June 16, 2020 at 00:55. |
| Fully support this proposal, it's well-justified, and an overhauling of our current, rather neglected approach to gameplay pages can only be a good thing.
I'm not sure if it's in your current plans, but regardless I also think it would be great idea to list specific technical info on the gameplay pages, so that Halopedia becomes a go-to place for players who are seeking to understand what's going on between the lines of the gameplay, or looking to theory-craft. Being part of the Halo Speedrunning community, I know that were this information detailed on Halopedia rather than the community relying on word of mouth, we would gain a ton of traffic.
To go with the Sniper rifle example, we could list the exact damage values, maximum rate of fire, etc for each title it appears in, describe other mechanics, like the fact that it's rounds penetrate enemies doing full damage to anything behind them, state the exact damage penalty it has against Flood, and so on. Readers would be able to easily compare this with stats from the gameplay pages of enemies and vehicles from the respective games.
| Posted by Two EEzy on June 16, 2020 at 05:25. |
| - Being part of the Halo Speedrunning community, I know that were this information detailed on Halopedia rather than the community relying on word of mouth, we would gain a ton of traffic.
What kind of info would this be? In regards to levels and maps, this kind of thing would definitely be welcome. The only real thing preventing us from doing it is that there's not many people with an active knowledge of these sorts of tricks, but I definitely think it's a good idea to include.
| Posted by BaconShelf (administrator) on June 16, 2020 at 11:43. |
| @Riley:
I believe we should do pages for all REQ variants, in the same manner as we'll do pages like the Machine pistol page. However, yeah, I wouldn't necessarily oppose making the gameplay sections on the lore pages slightly longer, but I'd want the same rule to apply to them as would apply to the universe and lore sections of the gameplay pages - they must remain brief and digestible. I'd say two or three paragraphs max. All of the specific gameplay information unique to that one lore weapon model should still be on the main weapon gameplay page, though, as well as on the lore page.
@Two EEzy:
Regarding the idea of including exact stats on the weapon pages, I like the idea, but I've no idea where we would be able to find such stats, and nor how we'd cite them. If you know of a resource we could use, let me know! Another issue, though, would be the fact that stats differ between campaign and multiplayer, and can vary between title updates in some cases. Still, it's definitely something to investigate.
| Posted by Dab1001 (administrator) on June 16, 2020 at 15:56. |
| Oh I get it, your REQ plans make sense to me now. As for the info on the lore pages, I think that works. The stats or anything like that weren't what I had in mind, more just general info about the gameplay opportunities or abilities and some of the uniquer stuff about it.
| Posted by CMDR RileySV (administrator) on June 16, 2020 at 21:50. |
| Works for me, then, Riley.
| Posted by Dab1001 (administrator) on June 16, 2020 at 22:26. |
| I'm happy with this proposal. Just two thoughts on page layout, outlined below:
- I'm not sure if it needs a "trivia" section at the risk of the page losing focus, editors adding useless trivia, or creating redundancies (between articles and within the page itself). Any cross-game information (e.g. changes from Halo 2 to Halo 3) should go into the "Evolution" section, and if the information is limited to a single game (and thus a single weapon), then it should go to the page about the weapon itself. I've gone through each of the individual sniper rifle pages, and none of the trivia feels like it could go in here. The closest one I could think of was the trivia about players receiving more sniper rifle ammo in the level Nightfall being a homage to Truth and Reconciliation, but I personally don't think that should be in there as "trivia" - maybe as production note. This may change in the future, but I'd rather prevent chances of clutters being thrown into these pages.
- Whilst a gallery section is nice, I'd suggest either 1) remove the gallery section and have images dispersed in the article (similar to what's been done in the Scarab hub), or 2) limit the number of images allowed in the gallery. The sniper rifle has appeared in every game, and I'm worried it'd create a rather long image list in a page on gameplay, which should be about gameplay information and technical details like Two EEzy suggested. I understand the example page is a work-in-progress draft, but right now there are seven images of the H2AMP sniper rifle in a 20-image gallery, when two or three images would likely suffice. As 343i release more visual media, there would be more competition for space (if we limit the number of images in the gallery section) or more than half a page of images (if we don't put a limit on the number of images in the section). If someone wants to see more images of the Halo 3 sniper rifle, they can go to the page on the Halo 3 sniper rifle.
| Posted by JackVibe (administrator) on June 17, 2020 at 07:11. |
| In regards to the gallery issue, we've talked about introducing Gallery pages for subjects with lots of visual depictions for that exact reason. That way, on-page gallery sections can just show a curated selection of images, then a dedicated page can act as a curated guide to the thing in question (be it a weapon or otherwise), allowing us to focus on small details with some more commentary. I agree with what you said.
| Posted by BaconShelf (administrator) on June 17, 2020 at 11:22. |
| Regarding the trivia section, I think we should leave the door open for there to be a trivia section on these pages in future. However, I agree that the sniper rifle one doesn't really need it. Honestly, though, editors adding useless trivia to the trivia sections is a pretty common problem on the wiki as a whole. Perhaps we should do something larger to address that.
As for the gallery, I do believe we should still have a gallery (potentially even an entire gallery page on top of it, as Bacon suggests), but yeah, the current gallery in that mockup isn't great. IIRC, I just copy/pasted part of the SRS99 AM sniper rifle gallery and stuck a handful of images of the other snipers in to show a wider variety. If/when we go ahead with this idea, I'd suggest that the gallery sections have 2-4 images from each game (although in cases where it's a weapon that's not appeared in many games, potentially more), and not be longer than a couple dozen images or so. It should definitely be a lot more curated than the pages on each of the individual weapons/variants.
| Posted by Dab1001 (administrator) on June 17, 2020 at 13:13. |
| I like Bacon's idea. Gallery pages would help alleviate my concern.
An on-page gallery would need to be carefully curated. I'd say 2-4 images per game would be too many, even. We already have the list of images under "Universe and lore" which showed the appearance of each sniper rifle. A gallery section should complement the information presented on the article - if the page is about gameplay, then the images should be related to gameplay - like applications of the weapons in-game, like the Spartan Laser penetrating two Spartans at once, or a well-timed gravity hammer swing throwing off a rocket off-course. But then again, wouldn't these images go into the "Gameplay" section of the page, where surely such information would be mentioned? I simply don't think having a gallery showing all the sniper rifles in different contexts (like cutscene appearance, HUD appearance and in-game appearance) from each game would significantly enhance a page which focuses on gameplay.
As for trivia section, I'd say we can keep it open for the future when the need arises, but for now, keep it away to maintain a focused article. If we come across something that doesn't fit anywhere else in the page, it can be the first entry in the trivia section.
| Posted by JackVibe (administrator) on June 17, 2020 at 14:50. |
| Regarding the trivia section, yeah, I agree. I only included it on this pitch to illustrate what the maximal number of headings and sections would be in the worst case scenario.
Now, concerning the gallery sections, it would likely vary depending on the topic. For the sniper rifle, we've got CE, H2, H3, Wars, ODST, Reach, CEA, SA, H2A, SS, H5G, Wars 2 and Infinite to deal with, so we're going to need it to be very closely curated (although bear in mind that for some of these games, we have basically nothing to show - e.g. the Wars and Spartan games). However, many other topics will have a lot less images, for instance even a weapon as common as the BR will only have H2, H3, H4, SA, H2A, SS, H5G and Infinite to deal with.
As for whether we should have a gallery section at all, this actually brings up a larger point of discussion. From what I've seen, we're pretty unique in our gallery sections to begin with. The vast majority of wikis I've seen don't have galleries at all, and use images exclusively within their text to illustrate the points being made. Of the wikis that do include galleries, none that I've found go quite as far with the idea as we do (save for Halo Alpha, which was derivative of Halopedia in the first place). I would argue that they don't really directly enhance the lore pages any more than they would the gameplay pages. However, I feel that they do complement the pages' contents rather well, and they make Halopedia a useful resource for folks looking for images. Consequently, I feel we should keep including them on pages, both gameplay and lore.
Posted by Dab1001 (administrator) on June 17, 2020 at 16:02.
Edited by Dab1001 (administrator) on June 18, 2020 at 12:16. |
| I would argue that images in "lore pages" do already enhance the written information by showing the weapon/vehicles in different contexts, what character has used them, which battle they're used in, and the method of operation. In order for pictures to "complement well", they should visually depict the page's information. The gameplay images should show what's being said in the article, otherwise it's just a bunch of pictures asking for editors to throw in more.
The gallery of the proposed gameplay article would need an overall cap (e.g. 20 images) and individual-media cap (e.g. 1-2 images per game) to prevent content unbalance or image dumps.
| Posted by JackVibe (administrator) on June 18, 2020 at 10:45. |
| By that same token, though, I would argue the gallery would enhance the gameplay page in a similar way, then. Naturally, images like these ones wouldn't be featured, and nor would images from the books, comics, films, etc. However, stuff like concept art and renders from various should still stay on the gameplay page in addition to in-game images, I feel, because the former shows the out-of-universe evolution of the weapon, and the latter helps to demonstrate to players exactly what to look for in-game. However, I definitely agree that we shouldn't exceed roughly 20 images or so.
| Posted by Dab1001 (administrator) on June 18, 2020 at 12:15. |
| I think this project is definitely a good idea. You've laid out your plans and reasoning very well.
I'd also agree that having a gallery on the gameplay pages can enhance them, but it's important that they don't get too bloated.
| Posted by Rusty-112 (administrator) on June 19, 2020 at 03:55. |
| Posted by Dab1001 on June 16, 2020 at 15:56.
Regarding the idea of including exact stats on the weapon pages, I like the idea, but I've no idea where we would be able to find such stats, and nor how we'd cite them. If you know of a resource we could use, let me know! Another issue, though, would be the fact that stats differ between campaign and multiplayer, and can vary between title updates in some cases. Still, it's definitely something to investigate.
The large majority of the in-game information can easily be found through Assembly, the only difficulty being knowing where to look, but that's something that the Halo modding community is always eager to help with.
I believe weapon stats differing between campaign and multi are the exception rather than the norm, but we'd still need to figure out how to handle it. As for title updates, that's something I would consider ignoring completely, in fact I'd suggest our gameplay pages as a whole should be geared towards the most recent versions (namely MCC), but that's another matter entirely.
In hindsight, the idea of having technical info on the wiki is probably something to consider after the proposed gameplay overhaul has been implemented, but may be useful to keep the possibility in mind.
Some examples for the Sniper Rifle in Halo: Reach:
(Weapon Stats)
-"Enables integrated Night Vision"
-"Magnetizes Only When Zoomed"
-"Fire Recovery Time": 0.75
(Projectile Stats)
-Maximum Range: 500
-Velocity: 6000
(Projectile Impact Stats)
-Damage: 80
-"Can Cause Headshots"
-"Ignores Headshot Obstructions"
Posted by BaconShelf on June 16, 2020 at 11:43. :
What kind of info would this be? In regards to levels and maps, this kind of thing would definitely be welcome. The only real thing preventing us from doing it is that there's not many people with an active knowledge of these sorts of tricks, but I definitely think it's a good idea to include.
I was more thinking of examples like, instead of someone having to ask "how many rockets does it take to blow up a Phantom on x difficulty in x game again?" they could just quickly hop to the relevant gameplay pages and find the exact numbers (there's currently no place on the internet that displays this info, as far as I know)
As far as glitches, the wiki does have already articles for a significant amount of tricks and glitches, though many of them are quite old. I do think that eventually having technical information either on, or linked to by our gameplay pages would help attract the kind of editors with the most active knowledge in that department though.
| Posted by Two EEzy on June 20, 2020 at 13:18. |
| Posted by Two EEzy on 20 June 2020 at 13:18.
The large majority of the in-game information can easily be found through Assembly, the only difficulty being knowing where to look, but that's something that the Halo modding community is always eager to help with.
I'm concerned about how we would cite that on the page, though. If there's no other option, we could definitely just cite something like <ref>''Halo 3'', datamined information</ref>, but this isn't ideal as it's hard to fact-check, so if there is an alternative source, we should take it. Do you know of any existing resources that list out data like this?
Posted by Two EEzy on 20 June 2020 at 13:18.
I believe weapon stats differing between campaign and multi are the exception rather than the norm, but we'd still need to figure out how to handle it. As for title updates, that's something I would consider ignoring completely, in fact I'd suggest our gameplay pages as a whole should be geared towards the most recent versions (namely MCC), but that's another matter entirely.
As I understand it, it's actually very common. The only FPS game in the Halo series with unified weapon stats across campaign and competitive multiplayer is, I believe, Halo 3. All the others (to my knowledge, at least) are balanced separately between them.
Regarding title updates, I think it's crucial that we keep info about both, especially in cases like Halo: Reach and Halo 4, where non-TU gametypes can also be played alongside TU ones (Reach actually has three different settings in MCC: vanilla, TU and zero bloom no sprint or ZBNS).
Posted by Two EEzy on 20 June 2020 at 13:18.
In hindsight, the idea of having technical info on the wiki is probably something to consider after the proposed gameplay overhaul has been implemented, but may be useful to keep the possibility in mind.
On the contrary, I would love to implement them as soon as possible. I just personally wouldn't know where to start, given that we need it for all games.
Posted by Two EEzy on 20 June 2020 at 13:18.
Some examples for the Sniper Rifle in Halo: Reach:
(Weapon Stats)
-"Enables integrated Night Vision"
-"Magnetizes Only When Zoomed"
-"Fire Recovery Time": 0.75
(Projectile Stats)
-Maximum Range: 500
-Velocity: 6000
(Projectile Impact Stats)
-Damage: 80
-"Can Cause Headshots"
-"Ignores Headshot Obstructions"
I would want to format this as a table in most cases, although stuff like the night vision and the fact that it can headshot enemies would be included in the text body itself. In particular, the official gameplay term for the latter is "precision weapon".
Posted by Two EEzy on 20 June 2020 at 13:18.
I was more thinking of examples like, instead of someone having to ask "how many rockets does it take to blow up a Phantom on x difficulty in x game again?" they could just quickly hop to the relevant gameplay pages and find the exact numbers (there's currently no place on the internet that displays this info, as far as I know)
This sort of stuff I would totally advocate including. In fact, I was thinking of doing a full table that tells you how many shots each weapon takes to kill each enemy on every difficulty across every game, similar to what the French Halo wiki, WikiHalo, does here. Although we'd probably need to split that into its own article (or use tabbers or something), 'cause otherwise it's going to be a lot of info.
Posted by Two EEzy on 20 June 2020 at 13:18.
As far as glitches, the wiki does have already articles for a significant amount of tricks and glitches, though many of them are quite old. I do think that eventually having technical information either on, or linked to by our gameplay pages would help attract the kind of editors with the most active knowledge in that department though.
As I understand it, CIA wants to kill most of the tricks and glitches pages, as many of them aren't very notable or are just spurious to begin with. In terms of putting that sort of stuff on the gameplay pages, I do think a sort of tips and tricks section is necessary, but I think we ought to curate them carefully, and pull from the official strategy guides wherever we can - or at least, use reputable online sources for gameplay advice and tips as citations. This would help to avoid people just writing down any random stuff that comes into their head with regards to gameplay, which (I think) is where a lot of our current walkthrough and gameplay pages go wrong - they're just a slapdash collection of tonnes of subjective and anecdotal advice added bit-by-bit by tonnes of different people over the years.
However, yeah, it is my hope that this project will encourage people who have an interest in the gameplay or technical/modding sides of the franchise to jump in and start editing. We ourselves can do a lot, but there are others who are much more knowledgeable than us who would be able to do even more.
| Posted by Dab1001 (administrator) on June 21, 2020 at 22:23. |
| FYI, folks, I intend to start implementing these pages within the next few days :D
| Posted by Dab1001 (administrator) on June 27, 2020 at 17:34. |
| Sounds like a good idea!
| Posted by Covenant PhD on July 1, 2020 at 21:59. |
| Just a heads-up: Sniper Rifle page is taking longer than expected - just the gameplay section left now, though. I've began collecting some of the official game guides for this project, so that we can have something to cite in the gameplay section. Once those all arrive, I'll finish it up and push it onto the mainspace. I anticipate that other weapon pages, while they will still take a while (this is a big undertaking, after all) will be faster once I get to them, as I'll have created all the templates, polished and fine-tuned the page layout fully and will already have all the guides to use for reference.
In the meantime, Riley has begun work on the Mongoose page. I have also gone ahead and done the gameplay overhaul for the Machine Pistol because it's the only weapon that doesn't appear in a game that has a guide book because it's hands-down the best weapon in the series and it needs more love.
EDIT: Oh, and I'm also looking into automatic the stats tables by pulling values from the games using the Assembly modding tool, and using Scribunto to calculate stuff like shots to kill, time to kill, etc and then load it all into a table to put on the page. No idea when I'll be able to get all this working by, though.
Posted by Dab1001 (administrator) on July 10, 2020 at 21:45.
Edited by Dab1001 (administrator) on July 10, 2020 at 21:48. |
| Yes can we please do this. I struggle trying to find gameplay information on here, It's all lore. I mean I love the lore but still, Halo is more than just lore.
| Posted by Smankey415 on January 13, 2022 at 06:25. |
| |
