Warning: You are using TidyHTML mode! Pages MAY and probably WILL break. To disable, click here or append 'xxx-off=1' to the URL!

Register - Login
Views: 57923030
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - JCS - Stats - Latest Posts - Color Chart - Smilies
10-17-14 01:01:12 PM

Jul - Posts by Sinsmalice
Pages: 1 2
Sinsmalice

Level: 12


Posts: 24/27
EXP: 6078
For next: 1843

Since: 08-27-09


Since last post: 1854 days
Last activity: 1867 days

Posted on 09-03-09 04:16:50 AM, in A Level... (last edited by Sinsmalice at 09-03-09 04:17 AM) Link
Originally posted by Garmichael
Originally posted by Sinsmalice
Originally posted by dirbaio
thanks. but you should learn to edit things by yourself. In the archived thread you have info about all the blocks.

I dont get info thats straight cut like that. :/

Its usually this "xxxx xxxx xxxx xxxx yyyy yyyy yyyy yyyy x Over 9000" shit that seems like they're purposely trying to confuse newbies. I'm a designer, not a developer.


No one is purposefully trying to confuse anyone. There just isn't an easier way to explain what all the info in the hex blocks do. If you're confused, you could always try re-reading the information.

And sooner or later, you're going to have to admit to yourself that technical stuff is always part of a designers path. A designer that doesn't understand the technical aspects of a project are more of a burden than anything when working with a team. Go screw around with Hyrule Magic or the SMW editor, then come back to this editor and you'll see just how easy it is to make levels in NSMB.

Yes they are...

Months ago yall KNEW I'd be gracing everyone with my presence and everyone got together and said "Gee, Njrg will be here in half a year. Lets make lots of post filled with random numbers just to confuse the hell out of her when she arrives."

This is fact. This isn't open for debate.
Sinsmalice

Level: 12


Posts: 25/27
EXP: 6078
For next: 1843

Since: 08-27-09


Since last post: 1854 days
Last activity: 1867 days

Posted on 09-13-09 03:08:03 AM, in A Level... Link
Originally posted by dirbaio
Well, after trying again and again to get the 3 star coins, i gave up!

It is too hard. DESESPERATINGLY Hard!!!!
Seriously. I think this level is too hard, because it is too frustrating. A level should not be frustrating, because if it is, it's no longer fun. If you plan to make any remake i STRONGLY encourage you to not make it this hard...

But the level is well designed. I never got stuck, because you took care it doesn't happen, for example, with the starting mega mario, there is another vine if you break the original one...

Good, but frustrating, level!
Have you even been able to finish the level without the coins?
What about challenge 2? Any luck?

Anyways, Its been over a week. So I'll post the solutions...(Note: That the level has gone through moderations since I uploaded incomplete level, but they dont affect the challenge.)

Because the Starcoins is a puzzle in itself, its undoubtly going to be as hard as you think it is if you try to collect them head on. It requires a specific order thats actually moderately easy. PLEASE NOTE: That everything I describe is possible. I've done it myself to confirm. I'm not a mario-playing expert but even I can finish Challenge 1 and 2 with relative ease because I designed, but more importantly know the specific orders to the puzzle. I've also designed the challenges to be completed starting as any un-powered or powered up mario. And don't like to brag, but I think my design is pretty genius. As complex as it is theres only one possible way (and its listed below) to be stuck that requires a restart or letting the clock run out, and I think thats a pretty great accomplishment seeing as most people who design a crazy level often have many places where you can get stuck and cant even kill yourself.

Challenge 1: tinyshit/14iq5pt.png

Step 1: Obvious... Get to Step 1.
Step 2: Get coin and get to step 3 without dyeing.
Step 3: Ignore ANY POWERUP except Minimushrooms until Step 6. Hit the vine.
Step 4: Get to Step 4 by jumping accross the gap. Only possible as mini Mario, then hit the vine. WATCH OUT for falling enemies and makesure the Green Koopa doesnt fall.
Step 5: Groundpound the turtle forcing it to go right to crash the blocks. Follow the turtle by using the vine from step 4. Grab the 2nd star coin and backtrack to where you found the 1st coin.
Step 6: Get the mushroom and head to step 7.
Step 7: As big mario, get on the falling platform.
Step 8&9: Jump towards the 3rd starcoin at the right moment.
Final Step: Finish the level without dieing.

Challenge 2: tinyshit/2prs8ew.png

Step 1: Get to Step 1. If you somehow miss the mushroom and it escapes off screen, prepare to backtrack against the current of spiked blocks. (Yes, Its Possible)
Step 2: Use the Spiked block to get to small mario. Head to step 3. (Hint: Holding down while jumping often helps)
Step 3: If you managed to get to step 3 as big mario (Yes its possible), congratulations, you are stuck. As small mario, pound the block to reveal a minimushroom and chase it down.
Step 4: Every area you touch will reveal a coin. Make sure you collect every silhouette you turn into a coin. If you leave and coin, Step 6-7 will NOT work. You may ignore the other silhouettes if they have NOT turned into coins yet. Once you've collected every coin thats in your way, proceed to step 5.
Step 5: Hit the P switch and IMMEDIATELY head to step 6.
Step 6: Get into the Pip cannon AS MINI MARIO and get in while the P-switch is still active. You must be aware that Mini Mario defies the game's physics. This is true even for the pipe cannon.
Step 7: If you've managed to complete steps 1-6 flawlessly, you will fly halfway accross the level and even through and between the decorative boxes sliding withing the range of the secret pipe. Which will move you to the 2nd area for an alternate finish.
______________________________________________________

I'm somewhat putting the construction of the unfinished Area on hold. Its about half done, and in truth, I stopped working on it 2 days after I made this thread. You can blame my girlfriend as she got playing an MMO, and then Scribblenauts came out...
I can say that the "main" part of area 2 thats 85%completed is straight-forward classic mario where no thinking is required. Just run, jump, and pray that you dont fall in a pit. But its only using up the bottom half of the area, and I have plans to make the top half (incomplete) a puzzle challenge for starcoins. I did have plans to make a giant, epic level that was supposedly 6-7 times greater in size than Bowser's castle, but the editor is exhausting so I've given up that idea. I may re-consider if someone dethrones my level. I pretty much crowned my concept level the hardest NSMB level that ever existed to this date.
Sinsmalice

Level: 12


Posts: 26/27
EXP: 6078
For next: 1843

Since: 08-27-09


Since last post: 1854 days
Last activity: 1867 days

Posted on 09-13-09 04:45:20 PM, in A Level... Link
Originally posted by dirbaio
Yes. I think this IS the hardest NSMB level ever existed.

To your questions: I couldn't beat the level even without star coins And I couldn't get them even with the solutions you posted
My only advice is practice.

Challenge 2 is pretty easy. I'd post a video, but I dont know how to record a high-quality video. I'm positive that once you saw it in action, you'd think that it was almost child's play.

Here are two tips...

Tip 1 for challenge 1: bring a giant mushroom and use it just before the road of Bullet Bills and Bombombs. I designed that are not only to be difficult in evasion, but to give you 5 1UPs if you destroy everything in giant mode. This will make the begginning of challenge 1 much easier.

Tip 2 for challenge 2: The area just before the spiked block area for minimario is often out of sync due to camera issues. I find that if you backtrack to just before the vine, get a running start, and jump through the minimario passage, you will pan the camera fast enough to sync up the spiked blocks, making a much more easier and predictable current of blocks.

Thats about the last bit of help I can think about.

But I agree that the level isnt that fun (for me) because since I made it, I'm not challenged by it. :[
Sinsmalice

Level: 12


Posts: 27/27
EXP: 6078
For next: 1843

Since: 08-27-09


Since last post: 1854 days
Last activity: 1867 days

Posted on 09-18-09 08:48:43 PM, in A Level... Link
Originally posted by dirbaio
I feel good! I've got to the incomplete area!!!
Good job

You're probably the only one who ever will.
Pages: 1 2
Jul - Posts by Sinsmalice






Rusted Logic

Acmlmboard - 07/23/2013 b378.03
©2000-2013 Acmlm, Xkeeper, Inuyasha, et al.
bargaining-tycoon
19 database queries, 6 query cache hits.
Query execution time:  0.246446 seconds
Script execution time:  0.033332 seconds
Total render time:  0.279778 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 94 column 11 - Warning: <form> isn't allowed in <table> elements
line 93 column 10 - Info: <table> previously mentioned
line 95 column 11 - Warning: missing <tr>
line 95 column 124 - Warning: missing </font> before </td>
line 99 column 16 - Warning: plain text isn't allowed in <tr> elements
line 95 column 11 - Info: <tr> previously mentioned
line 100 column 68 - Warning: <nobr> is not approved by W3C
line 100 column 68 - Warning: missing </nobr> before </td>
line 117 column 68 - Warning: <nobr> is not approved by W3C
line 117 column 68 - Warning: missing </nobr> before <tr>
line 141 column 35 - Warning: missing <tr>
line 141 column 50 - Warning: missing </font> before </td>
line 141 column 137 - Warning: missing </font> before </table>
line 143 column 35 - Warning: missing <tr>
line 143 column 96 - Warning: unescaped & or unknown entity "&page"
line 143 column 50 - Warning: missing </font> before </td>
line 143 column 133 - Warning: missing </font> before </table>
line 150 column 9 - Warning: <div> isn't allowed in <tr> elements
line 149 column 9 - Info: <tr> previously mentioned
line 152 column 9 - Warning: missing <tr>
line 166 column 13 - Warning: missing <tr>
line 167 column 27 - Warning: <nobr> is not approved by W3C
line 183 column 15 - Warning: missing <td>
line 184 column 9 - Warning: <div> isn't allowed in <tr> elements
line 183 column 15 - Info: <tr> previously mentioned
line 186 column 9 - Warning: missing <tr>
line 200 column 13 - Warning: missing <tr>
line 201 column 27 - Warning: <nobr> is not approved by W3C
line 226 column 2720 - Warning: unescaped & or unknown entity "&9:"
line 243 column 15 - Warning: missing <td>
line 244 column 9 - Warning: <div> isn't allowed in <tr> elements
line 243 column 15 - Info: <tr> previously mentioned
line 246 column 9 - Warning: missing <tr>
line 260 column 13 - Warning: missing <tr>
line 261 column 27 - Warning: <nobr> is not approved by W3C
line 279 column 15 - Warning: missing <td>
line 280 column 9 - Warning: <div> isn't allowed in <tr> elements
line 279 column 15 - Info: <tr> previously mentioned
line 282 column 9 - Warning: missing <tr>
line 296 column 13 - Warning: missing <tr>
line 297 column 27 - Warning: <nobr> is not approved by W3C
line 304 column 17 - Warning: discarding unexpected <table>
line 307 column 35 - Warning: missing <tr>
line 307 column 96 - Warning: unescaped & or unknown entity "&page"
line 307 column 50 - Warning: missing </font> before </td>
line 307 column 133 - Warning: missing </font> before </table>
line 309 column 35 - Warning: missing <tr>
line 309 column 50 - Warning: missing </font> before </td>
line 309 column 137 - Warning: missing </font> before </table>
line 311 column 17 - Warning: discarding unexpected </textarea>
line 311 column 28 - Warning: discarding unexpected </form>
line 311 column 35 - Warning: discarding unexpected </embed>
line 311 column 43 - Warning: discarding unexpected </noembed>
line 311 column 53 - Warning: discarding unexpected </noscript>
line 311 column 64 - Warning: discarding unexpected </noembed>
line 311 column 74 - Warning: discarding unexpected </embed>
line 311 column 82 - Warning: discarding unexpected </table>
line 311 column 90 - Warning: discarding unexpected </table>
line 320 column 9 - Warning: missing </font> before <table>
line 336 column 9 - Warning: inserting implicit <font>
line 348 column 23 - Warning: inserting implicit <font>
line 355 column 57 - Warning: discarding unexpected </font>
line 313 column 1 - Warning: missing </center>
line 91 column 9 - Warning: <img> lacks "alt" attribute
line 93 column 10 - Warning: <table> lacks "summary" attribute
line 95 column 63 - Warning: <img> lacks "alt" attribute
line 100 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 100 column 93 - Warning: <img> lacks "alt" attribute
line 117 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 117 column 98 - Warning: <img> lacks "alt" attribute
line 136 column 1 - Warning: <table> lacks "summary" attribute
line 136 column 240 - Warning: <td> attribute "bgcolor" lacks value
line 141 column 17 - Warning: <table> lacks "summary" attribute
line 143 column 17 - Warning: <table> lacks "summary" attribute
line 151 column 9 - Warning: <table> lacks "summary" attribute
line 155 column 22 - Warning: <img> lacks "alt" attribute
line 155 column 63 - Warning: <img> lacks "alt" attribute
line 155 column 111 - Warning: <img> lacks "alt" attribute
line 155 column 161 - Warning: <img> lacks "alt" attribute
line 156 column 11 - Warning: <img> lacks "alt" attribute
line 162 column 15 - Warning: <img> lacks "alt" attribute
line 165 column 11 - Warning: <table> lacks "summary" attribute
line 169 column 308 - Warning: <img> proprietary attribute value "absmiddle"
line 169 column 308 - Warning: <img> lacks "alt" attribute
line 185 column 9 - Warning: <table> lacks "summary" attribute
line 189 column 22 - Warning: <img> lacks "alt" attribute
line 189 column 63 - Warning: <img> lacks "alt" attribute
line 189 column 111 - Warning: <img> lacks "alt" attribute
line 189 column 161 - Warning: <img> lacks "alt" attribute
line 190 column 11 - Warning: <img> lacks "alt" attribute
line 196 column 15 - Warning: <img> lacks "alt" attribute
line 199 column 11 - Warning: <table> lacks "summary" attribute
line 205 column 269 - Warning: <img> proprietary attribute value "absmiddle"
line 205 column 269 - Warning: <img> lacks "alt" attribute
line 245 column 9 - Warning: <table> lacks "summary" attribute
line 249 column 22 - Warning: <img> lacks "alt" attribute
line 249 column 63 - Warning: <img> lacks "alt" attribute
line 249 column 111 - Warning: <img> lacks "alt" attribute
line 249 column 161 - Warning: <img> lacks "alt" attribute
line 250 column 11 - Warning: <img> lacks "alt" attribute
line 256 column 15 - Warning: <img> lacks "alt" attribute
line 259 column 11 - Warning: <table> lacks "summary" attribute
line 265 column 284 - Warning: <img> proprietary attribute value "absmiddle"
line 265 column 284 - Warning: <img> lacks "alt" attribute
line 265 column 394 - Warning: <img> proprietary attribute value "absmiddle"
line 265 column 394 - Warning: <img> lacks "alt" attribute
line 281 column 9 - Warning: <table> lacks "summary" attribute
line 285 column 22 - Warning: <img> lacks "alt" attribute
line 285 column 63 - Warning: <img> lacks "alt" attribute
line 285 column 111 - Warning: <img> lacks "alt" attribute
line 285 column 161 - Warning: <img> lacks "alt" attribute
line 286 column 11 - Warning: <img> lacks "alt" attribute
line 292 column 15 - Warning: <img> lacks "alt" attribute
line 295 column 11 - Warning: <table> lacks "summary" attribute
line 299 column 224 - Warning: <img> lacks "alt" attribute
line 146 column 17 - Warning: <table> lacks "summary" attribute
line 307 column 17 - Warning: <table> lacks "summary" attribute
line 309 column 17 - Warning: <table> lacks "summary" attribute
line 315 column 1 - Warning: <img> lacks "alt" attribute
line 316 column 1 - Warning: <img> lacks "alt" attribute
line 317 column 1 - Warning: <img> lacks "alt" attribute
line 324 column 9 - Warning: <table> lacks "summary" attribute
line 326 column 25 - Warning: <img> lacks "alt" attribute
line 356 column 17 - Warning: <table> lacks "summary" attribute
line 141 column 137 - Warning: trimming empty <font>
line 143 column 133 - Warning: trimming empty <font>
line 279 column 15 - Warning: trimming empty <tr>
line 307 column 133 - Warning: trimming empty <font>
line 309 column 137 - Warning: trimming empty <font>
line 153 column 11 - Warning: <a> cannot copy name attribute to id
line 187 column 11 - Warning: <a> cannot copy name attribute to id
line 247 column 11 - Warning: <a> cannot copy name attribute to id
line 283 column 11 - Warning: <a> cannot copy name attribute to id
Info: Document content looks like HTML Proprietary
Info: No system identifier in emitted doctype
128 warnings, 0 errors were found!


The table summary attribute should be used to describe
the table structure. It is very helpful for people using
non-visual browsers. The scope and headers attributes for
table cells are useful for specifying which headers apply
to each table cell, enabling non-visual browsers to provide
a meaningful context for each cell.

The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
. You may also want to try
"http://www.cast.org/bobby/" which is a free Web-based
service for checking URLs for accessibility.

You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

To learn more about HTML Tidy see http://tidy.sourceforge.net
Please fill bug reports and queries using the "tracker" on the Tidy web site.
Additionally, questions can be sent to html-tidy@w3.org
HTML and CSS specifications are available from http://www.w3.org/
Lobby your company to join W3C, see http://www.w3.org/Consortium