Hack Name: Mario my 1st
Author: Technopommes
Reasons for Removal:

I'm going to take a preemptive motion here.

Welcome to SMWC, Technopommes!

So, this is your first hack? Okay. The number one rule to hacking here is to never submit your first hack for moderation without getting some opinions/feedback on it. You can get that here or in the Works in Progress subforum in Hack Discussion (if your hack isn't finished). Remember to include screenshots and maybe an IPS Patch so people can playtest your hack.

Your screenshot (which isn't exactly proper--take one of you playing the game rather than sitting on the Overworld) is rife with cutoff. As well, unless your one level is really long (at least fifteen minutes' worth of gameplay), then a one-level hack isn't long enough to be accepted here.

In Hack Discussion, there is a stickied Hack Submission Guidelines thread. Please become more familiar with it before uploading another hack.

Thanks, and enjoy your stay here!

To continue with Kadyastar's removal log, here's some serious problem areas you need to look at in your hack before submitting it.
_{Also because Kadyastar sniped me}

First off, you should proofread your text. If you can't do it yourself, ask someone who can. Even if it is your mother or father!

This overworld is not a very good overworld. You should try building something like Super Mario World has, or just not editing the overworld at all.

Don't edit level 104! It is used in the ending, and can mess things up pretty badly if changed. Also, the blue bird is bouncing across the screen for some reason, falling below the screen and bouncing back up after wrapping vertically to the top of Yoshi's house. Very odd!

As soon as you go down the pipe, you are greeted to this area, with a yellow shell immediately flying at you. "Think quick" moments like this are highly frowned upon here. Also, what is up with the background?

"Cutoff" is a term where ground or other parts of the terrain suddenly stop, creating a cut out look, which is very displeasing to the eye. Like the small chunk of land in the upper left corner, the turn block going into the ground, the chunk of bush to the right, and the entire background. Also, having a note block positioned like this makes triangle blocks behave in an erratic fashion. It also makes it very difficult to go up the wall to continue with the level.

Floating stacked munchers are the biggest taboo here, as it is very nonsensical and lazy. If you need a wall of blocks that hurt Mario, edit the graphics to look more video game obstacle-ish, like a spike ball!

This hack violates the following:

Quote

1b) Your submitted hack must have at least one screenshot!
When you submit your hack, you should also upload at least one screenshot, if not several. An acceptable screenshot should feature an example of actual gameplay from the game (e.g. a screenshot that features the player, typical graphics and level design, choices of sprites, etc.). Unacceptable screenshots include unrelated images, as well as screenshots of simple, unrepresentative things (e.g. the Nintendo Presents screen or a very bland beta title screen). If you use the title screen as a screenshot, please include another screenshot of actual gameplay.

3) No graphical glitches!
Errors such as garbled sprites/FGs/BGs, message box text screwing up layer 3 items, floating/stacked/cutoff tiles, and general graphical ugliness are frowned upon. Also, don't forget about glitches such as sprite memory issues - the graphics of the sprite will 'disappear', but the sprite will still be there, and can unfairly hurt Mario.

4) Your hack should be of a reasonable length!
Unless you intend to make your hack contain very long and very high quality levels, demos which are too short to provide any feedback on or be enjoyable will be subject to removal. A general rule of thumb is that the hack should feature at least one complete world with about five levels, or should feature around at least 15 minutes of game time.

7a) Keep it fair, and keep the hack at a legitimate difficulty!
i.e. Avoid things like death after the goal, blind jumps, forced damage, excessive enemies, places where you can get permanently stuck, excessive 3-UP moons, glitch abuse, projectile sprites (like Bullet Bill) placed directly into a level instead of using the correct shooter/generator sprite, etc.

8b) Have fellow users beta test your hack before submitting it!
Your hack should be as good as you can make it before you submit it to be featured in the hack database. A good way to make sure you have a quality hack is have it beta tested. Have your friends play it and give you feedback, or recruit some beta testers here. The site's hack moderators are not beta testers; we are demo testers.

9) Quality level design
Your hack has a much higher chance of being accepted if the level design is fun. Conversely, if the level design is found to be lacking then a little cutoffness may be enough to push the hack into deletion.

Please read the Hack Submission Guidelines.

Mario my 1st--Technopommes

HoleNet.info