How Submissions and Updates Work on MFGG (Mario Fan Games Galaxy)

MFGG handles submissions and updates through a public, staff-reviewed content system: members submit games, hacks, sprites, tutorials, sounds, and other Mario fan works, and approved items appear in the site's content sections and on the Updates page under "Recent Additions." The Updates page also carries community announcements, so it functions as both a changelog and a notice board. You need an account to submit or comment; browsing the Updates page itself does not require one.

What the Updates page actually shows

The Updates page mixes two kinds of posts:

• Site news and community announcements — for example, a post wishing members a happy Left Handers' Day, or a call for artwork for a group photo with a submission deadline.
• Recent Additions — a running list of newly approved content, grouped by category.

Each Recent Additions entry typically includes:

Graphics entries follow the same pattern — title, author, and a short note — such as a Super Mario World-style Luigi Casino tileset, a custom Gothic tileset, or an NES-style Bowser sprite. Some entries are marked as updated rather than new, and version or release labels can appear in the title itself (for example, a "Beta Demo" or a "SAGE2026 Release").

How submissions are organized

The site's navigation lists the content areas that accept submissions:

• Games
• Hacks
• Sprites
• Tutorials
• Sounds
• Misc
• Other

This tells you the practical rule: pick the category that matches what you made, and the entry will be filed and displayed under that section. Because the Updates page labels each item with its category and type tag, readers can tell at a glance whether something is a full game, a demo, a minigame, or an asset pack.

The submission and update flow

1. Create an account or log in. The navigation includes Login and a "Not Registered?" link, and commenting requires being signed in.
2. Choose the matching content category from Games, Hacks, Sprites, Tutorials, Sounds, Misc, or Other.
3. Submit your work with a title, author credit, and short description. The Recent Additions entries show that approved items display exactly these fields, so prepare them up front.
4. Wait for it to appear under Recent Additions once approved. Updated versions of existing submissions are also surfaced there, sometimes with the version noted in the title.
5. Engage through comments. Each update post has a comment count and a "Leave Comment" option, so feedback happens directly on the update entry.

Where community activity happens

The Updates page is not the only channel. The navigation points to Forums, a Wiki, and Discord is referenced in announcements. This matters for deadlines: one post about a group photo noted that the forums and Discord were informed ahead of time while mainsite-only visitors got shorter notice. If you want early warning on events and deadlines, the forums and Discord are the faster channels; the Updates page is the public record.

Common sticking points

• Short-notice events. Announcements can carry tight deadlines — one group photo call gave less than two days' notice on the mainsite. Check the linked forum thread for details rather than relying on the update post alone.
• Account required for participation. Browsing is open, but submitting and commenting are tied to a logged-in account.
• Category choice affects visibility. A game filed under Games shows up differently from an asset filed under Graphics, so file under the section that matches the content type.
• Version labels matter. When updating an existing submission, note the version or release in the title, as seen with the SAGE2025/SAGE2026 releases, so readers can tell which build they are getting.

Quick reference

• To browse: open the Updates page and read Recent Additions by category.
• To submit: log in, pick the correct content category, and provide title, author, and description.
• To follow events: watch the Updates page, but join the forums or Discord for advance notice.
• To give feedback: use the comment section on the relevant update post.