Super Mario 64 Hacks Wiki
Super Mario 64 Hacks Wiki

Welcome to the Super Mario 64 Hacks Wiki! Please have a look at our rules and guidelines before making any edits or contributions. These exist alongside the standard rules of any wiki, such as respecting other's contributions, not spamming, etcetera.


1. Do NOT post ROM files of .z64 files to this wiki! The distribution of ROM files containing copyrighted material is illegal, and this includes ROMs for Super Mario 64, hacked or not. Please instead link to .bps files, websites that distribute .bps files. Anyone caught posting ROM files or links to ROM files on this wiki may be banned from contributing.

 

2. Do not use this wiki to advertise. This includes advertising social media, such as YouTube channels, even if they are producing content for the SM64 community. To advertise an upcoming ROM hack, please see rule 8.1.

 

3. If the download link for a hack is one that automatically begins a download, you must put a warning before it saying so. No exceptions! Use the template DLWarn to do so; see below for an example of how this can look:

{{DLWarn|[https://api.romhacking.com/game/emote-challenge-64/Emote%20Challenge%2064%20(v1.0).zip v1.0 BPS Patch]}}
 


4. Stay unbiased. It's not necessary to add in your own opinion on the hack or any part of it, we're just here to document information.

 

5. Generic file names are disallowed. This includes file names such as "Screenshot [date/time]", "Image", "IMG", and so forth. It must have an easily identifiable name.

 

6. Please do not create pages for upcoming hacks. Because this usually results in a bunch of abandoned pages for hacks floating around that often have incorrect names/info, or give the impression that a now-cancelled hack is still in the works. It's also worth noting that Upcoming Hacks are generally only published here as some kind of self-promotion, or promotion for a friend. If you would like to promote an upcoming hack, please make a blog post instead.

 

7. When typing, please Do Not Use Excessive Capitalisation Like This. It's very annoying to fix!

 

8. Before creating new pages:

 

8.1. Do not create an article page for a hack that doesn't yet exist. If a demo of it is released, then that's fine- an article can be made for the demo. But if its release has still not happened, a dedicated article for it should not be created. If you want to advertise a new hack, create a blog post instead.
 

8.2 If you are creating a page for a level in a hack, the article must be informative enough to warrant needing its own page. If you do not have any further information to add to the page that isn't already on the associated hack's article page, the level page will likely be deleted after it remains uninformative for long enough.

 

9. All content on the wiki must be relevant to Super Mario 64 ROM hacks. This includes all files, videos, and pages.

 



Recommendations for those unsure of where to start:
  • If you see an article that is missing a significant amount of information, please add the Stub template to the top. In source editor, simply add in {{Stub}}. If the article is in a bit of a bad state (for example, has a lot of misinformation/outdated information, or is written in a way that makes it very difficult to understand), please add the {{Rewrite}} template. If you're uncertain, send me a message.
  • Try to link any sub-pages (such as gallery pages) for hacks to their main page, and vice versa. I would recommend using the template Seealso/wikitext for the main page (here's the doc showing how to use it), or Seealsomulti for lots of links. Both templates have instructions for use available in visual editor.
  • When uploading a file, please state where you sourced it from and which hack(s) it is regarding, if applicable. This can be done in the file name to make it easier to find and use. For example, a screenshot from the first course in SM64: Last Impact could be named "LastImpact-c1.png". This means that if the file is ever floating around unused, it's easier to track down which article to put it into.
  • If you are willing to fill in the edit summary (please do, it's so helpful), a few words is all that is needed. For example, "proof reading", "added pic", "added level info", or even just "stubbed" if your edit was solely adding the Stub template. Also, please refrain from insulting previous versions of the page you're editing, as it tends to create bad blood between editors and discourage collaborative editing.

Thank you for reading, and happy editing!
If you have any further questions or queries, you are always welcome to message me on my profile wall, no matter how trivial or weird you feel it may be.