Mini-Mushroom goes through 1/2 tile high and/or wide gaps:

Buzzy Beetles and (Roof) Spinies can't pass through 1/2 tile high gaps:


Let me see if I got that straight, you basically want to force the player to get on the platform before said platform begin its expansion phase for the player to actually get launched upwards?
Not only that but the player will get launched only when the expansion reaches its maximal value?
And if one of the conditions fails the player must wait a "turn", or in other words for the next expansion phase?

Basically you want me to implement a check to see if Mario was standing on the platform before the expansion phase begins and also a check to see if Mario stayed on the platform for the whole duration of the expansion?
If both checks succeeded, Mario gets launched, if one of the checks fails, make the platform act as a normal platform for the remaining of the "turn", correct?

And I dare say I was right in being stubborn and…

Oh, hi! It's me again! Another ASM Hack?
Yes, yes, another ASM Hack, but this time this was something that was captivating me for a while:
_Could you make the game load custom graphics for each View in a given Area?
And now I can say that the answer is YES!

Views have their own parameters for ASM-template:


Now onto the second part.
To take full advantage of this hack, you will need to mess with the files in the course folder (the ones with 14 blocks of data, not the bgdat ones)

First, I'll remind you of how those files are laid out:
_info data
_block 1
_block 2
_block 3
_…
_block 13
_block 14

The info data is where are stored the offsets and the sizes for all 14 blocks (8 bytes per block)
So for example if I wanted to know where to read block 5, I first need the info data for block 5.
To calculate it, I need this formula:
(B-1)*8
Where B is the Block Number, so:
(5-1)*8 = 4*8 = 32

To read the info data for block 5, I need to go to offset 32 (0x20), and I read this:
00 01 00 00 14 00 00 00

??

So the offset is 4 bytes in size, the same goes for the block size:
Offset: 00 01 00 00
Size: 14 00 00 00

??

Let's invert the reading:
Offset: 00 00 01 00
Size: 00 00 00 14

Much better, so this means that block 5 begins at offset 0x100 and is 20 (0x14) bytes long!



But what does this have to do with this ASM Hack?
This is where I spice up the difficulty!
Remember the original layout? This is what you'll need to do:
_Info Data for View 0
_Block 1
_Block 2
_…
_Block 14
_Info Data for View 1
_Block 1
_Blocks 3 to 5
_Block 14
_Info Data for View 2
_Block 1
_Blocks 3 to 5
_Block 14
etc.

Basically for each additional View, the layout is:
_Info Data for View non 0
_Block 1
_Block 3
_Block 4
_Block 5
_Block 14

But why only those 5 Blocks?
_Block 1 allows you to change the Tileset, FG and BG .ncg as well as the Sounds Set
_Block 3 allows you to change the BG .nsc and .ncl respectively
_Block 4 allows you to change the Tileset .ncl
_Block 5 allows you to change the FG .nsc and .ncl respectively
_Block 14 allows you to change the Actors Sets

As an example you can download this level: Level 2-3 Area 1.nml
If you go look at the file B03_1.bin in the course folder, what I said earlier will start to make more sense, especially how the Info Data for additional Blocks is set.


Q: What if I only have 1 Block Set for all Views?
A: No problem, the game will work as it normally would, no graphical glitch or anything.

Q: Can you run this ASM Hack alongside the Dedicated graphics per Area Hack?
A: Yes you can, but keep in mind that only Sound Sets and Actor Sets will truly have an effect since the Tileset, FG and BG will get superseded anyways by the Dedicated graphics code!

Q: Does this work on the real deal?
A: Of course it works on a NDS!

Map icons with 256 colors each:



You will need the 3 files below (more so the 3^rd one) to put in the uiStudio folder:
UI_O_1P_course_select_o_ud_ncl.bin
UI_O_1P_course_select_u_ncg.bin
UI_O_1P_course_select_d.nce.bncd


The first is the 4096 colors-palette that will replace UI_O_1P_course_select_o_ud_ncl.bin
The second is the worldmap graphics used for the top screen that will replace UI_O_1P_course_select_u_ncg.bin
The third is the bncd file with all of its images upgaded to 8bpp mode that will replace UI_O_1P_course_select_d.nce.bncd

Palette 0 normally should have only 90 colors, but due to an earlier fail of mine, well it has 255 colors instead, but the basic idea stays the same:
_Palette 0 is for UI_O_1P_course_select_u.ncg.bin as well as the vast majority of the icons contained in the bncd.
_Palette 1 to 8 is for the World-map icons, in the same order
_Palette 9 is for the roads that are not unlocked yet, as well as for nodes/levels ignoring Challenge Mode
_Palette 10 is for all the worlds that are not unlocked yet
_Palette 11 to 15 are copies of the 4 main palettes

The bncd is a must! Especially considering that not only were the OAM properties changed, but also all the textures were doubled in size!

Download this modified version of NSMBe to easily import your 8bpp icons:
nsmb-editor-380b.zip

Now you can enjoy your new map-icons with 256 colors


Works on a NDS!

With this ASM Hack, not only can you use Sprite 93 regardless of the Sprite Set, but now you can also use Pipes and Signboards in front of tiles, in other words give them a higher layer priority.

Since this hack need a NSMB ROM with new files, you have to go there to download the hack:
http://nsmbhd.net/post/49237/



If you still want to get this on a already modified ROM, then you will need to patch a NSMB (U) ROM with one of the 2 patches in the archive and then extract the whole folder called yajirusi, the last one in the enemy folder.

After you've done the above, follow this tutorial to add files in your hacked ROM:
http://nsmbhd.net/thread/3253-adding-files-to-the-rom-tutorial/

Then go in the ASMTemplate folder, and open the folder bak (if it exists).
If it exists, then look for the file main.bin, and if it exists open it with an Hex editor and paste this at offset 0x19C0:


and at offset 0x39AB0 change EC 21 13 02 into 1C 20 00 02.

If either of the bak folder or the main.bin file doesn't exist, then in NSMBeditor Decompress arm9, extract it, open it with a Hex editor and do the 2 replacements at the offsets mentioned above, after you're done import back the arm9.


Again in the bak folder (assuming it exists) look for the file 0.bin, and if it exists open it with an Hex editor and at offset 0x2C9EA replace 0F 01 into 00 00.
If either of the bak folder or the 0.bin file doesn't exist, then in NSMBeditor Decompress overlay 9_0, open it with the NSMBe Hex editor and do the replacements at the offset mentioned above.


Now you can insert the 2 following ASM Hacks.


Signboard upgrade:

You will also need this Hack to prevent Actor 77 from dying upon level completion:
http://nsmbhd.net/post/51328/


The editor was optimized specifically to help level designers handle Sprite 93:

Be careful about Shift X and Shift Y, those are the values you want to use:
Normal size:

Nybble9: D => 8 pixels left

Nybble10: E => 8 pixels down



Small size:

Nybble9: 1 => 4 pixels left
Nybble9: 2 => 4 pixels right
Nybble9: 3 => 8 pixels left

Nybble10: 1 => 4 pixels down
Nybble10: 2 => 8 pixels down
Nybble10: 3 => 12 pixels down

All those specific cases will move the sprite in the Level Editor so you know what to expect.



Last but not least know that Sprite 93 has no collision, so if you want to enter the Pipes, you will have to create new objects in the Tileset 1 you're using that match the behavior of the Pipes' directions and place said objects directly behind the Pipes.

Most constructive post ever, no really I mean it, this is the single best post in NSMBHD hands down.
So good that I could tell just by looking at that single dot what rubbed you the wrong way with my arguably miserable attempt at helping you.

    

Dark vertical lines were lightened.
Suddenly I wanted to see how the tileset would look with brownish/autumnal grass instead.

In-game
    

Which version is the most visually appealing ?
Personally I prefer the brown grass variant.

How to edit/add tiles to the Jyotyu tileset without breaking the colors.

Step 1:
As an example we're going to add the NSMBWii Arrows.

You should make the picture 256×48 pixels from the get-go.


Step 2:
We're going to replace one of the 4 jyotyu ncl.
You should choose the ncl that has the least chance of giving an error because of repeated colors.
This time we're going to use the jyotyu_B.


Step 3:
Extract the ncl, you'll need the backup because we're going to re-insert it later.
Replace the ncl with this one:
d_2d_A_J_jyotyu_B_ncl(1121).bin
What is this ?
Basically it gives the second palette 256 unique colors (we're going to name it the Super Palette ), this is going to be the key to prevent any mistake when you want to import your image.

Step 4:
Extract the image colored with the Super Palette by clicking "Export this bitmap", again you're going to need it.


Step 5:
Now choose which palette to use with the NSMBWii Arrows, for this tutorial we're going to use the palette 0 (if you want to import on palette 1, Super Palette should be palette 0 then).

Step 6:
Switch to your Super Palette and click "Export this bitmap".


Step 7:
From there open both images you extracted with Photoshop, Gimp, etc.

Step 8:
Take care of the crossed parts and the flagpole base first and then copy the layer and save.


Step 9:
Import you fresh new image with the Super Palette by clicking "Import this bitmap with existing palette".


Step 10:
Click "Save All" and close the window.

Step 11:
Remember the ncl you extracted in Step 3 ? Now it is the time to reinsert it.
Look at the results:


If there is a mistake on the coloring, it will be only on the new tiles, in that case you can either:
_fix the few faulty pixels
_or try the same operation but with another jyotyu ncl instead.

Now enjoy your "flawless" Jyotyu tileset



Notes:
Q: Now what if I want to use the Super Palette with other jyotyu ncl?
A: I won't give the full answer, what I will tell is that LZ Decompress is going to come handy.

Also, don't ever extend Jyotyu available space.
While original tiles work fine, supernumerary tiles will look like a scrambled mess in-game.
Sorry Thierry but your Extended Jyotyu, while well thought, ultimately fell short

A simple tutorial about how to animate any background you want.



First decompress overlay 0 if it's not decompressed already.


Foreground animation table offset:


Background animation table offset:



Each table is 152 bytes long, and contains 2 bytes long data for each of the 76 background slots (1st table) / 76 foreground slots (2nd table).
If the data for a given background is 00 00, then this background won't be animated.

Offset formula for a given foreground slot is:


Offset formula for a given background slot is:




For example let's say you want to animate both FG and BG 59 the same way than FG and BG 4 respectively on the US version.

Retrieve the value used for FG 4:
4×2=8 (0×8);
So 2F734+8=2F73C.
Read the 2 bytes at offset 2F6A4, which are 07 00.

Now go to FG 59 offset:
59×2=118 (0×76);
So 2F734+76=2F7AA.
Read the 2 bytes at offset 2F7AA, which are 00 00.
Now replace them by the value in FG 4, which is 07 00.


Retrieve the value used for BG 4:
4×2=8 (0×8);
So 2F69C+8=2F6A4.
Read the 2 bytes at offset 2F6A4, which are 07 00.

Now go to BG 59 offset:
59×2=118 (0×76);
So 2F69C+76=2F712.
Read the 2 bytes at offset 2F712, which are 00 00.
Now replace them by the value in BG 4, which is 07 00.

Save overlay 0 and test in-game to see the results by yourself.


This tutorial pretty much voids my former tutorial about animating backgrounds.
Thanks to  Dirbaio for being the one who discovered the code in the first place, have a look at his thread.

This thread is somewhat out of left field considering my latest track record about ASM mods, but this read will be truly worth your time I hope.




Prelude:

First of all I would like to bring your attention about 2 oddities in canon NSMB games: have you ever noticed that there is a chunk of Foreground 5 seemingly missing from its graphics (.ncg)?


And again for Foreground 60?


Then look again, those missing chunks of graphics can be found in the .ncg of Tileset 5 and Background 60 respectively, don't believe me? Have a look by yourselves:
    

It seems that Nintendo devs used a trick to somehow make the graphics able to be shared amongst one same design, which for the Foregrounds (FG) and the Backgrounds (BG) is stored in a .nsc file.
And I would like to call this method the Tile-Share!

I will explain you in detail the core mechanics to use this tactic to its fullest potential!




1: Explanation:

If you decompress a .nsc file in the BG_nsc folder, the filesize will be 8192 bytes.
Now if you remember how FG and BG are designed, you should know that you can choose a 8×8 tile from the graphics with one of 2 palettes, and apply it to a 512×512 template.
How many tiles can you fit then in that template?

Let's do some fancy mathematics:
512²/8² = (512/8)² = 64² = 4096

4096 tiles per .nsc! And the decompressed filesize for a FG/BG .nsc is 8192 bytes… Could it be…
8192/4096 = 2

Would this mean that 2 bytes of data make up 1 tile? Seems plausible so far.
Let's see how… Oh! You know what? I'm just going to tell you the exact data.

Each tile takes 2 bytes, which means that each tile's offset begin at an even address and end with an odd address.
Due to the data being little-endian, you must invert the 2 bytes to read them correctly, ergo instead of reading them as AB CD read them as CD BA.
The tile order in the .nsc matches the tiles from the 512×512 template when read from left to right.

If you don't want the binary details, jump to the next sub-section.
Convert the data from hex to binary, upon conversion the data is laid out as follows:
PPPPVHTT TTTTTTTT

In order:
_T is the Tile Number in 10 bits, it can take a value from 0 to 1023 inclusive.
_H is the Horizontal Flipping bit, which will take effect only when set to 1.
_V is the Vertical Flipping bit, which will take effect only when set to 1.
_P is the Palette Number in 4 bits, it can take a value from 0 to 15 inclusive.


It is totally possible to read the tile data in hex, here's how:
_truncate the word (2 bytes) CDBA as C and then DBA.
C is the palette, and there's DBA:
_If D < 4, then you've already got the Tile Number DBA, HFlip=0 and VFlip=0.
_If D >= 4 and D < 8, then HFlip=1 and thus to retrieve the Tile Number you must subtract 4 to D.
_If D >= 8 and D < 12 (0xC), then VFlip=1 and thus to retrieve the Tile Number you must subtract 8 to D.
_If D >= 12 (0xC), then HFlip=1 and VFlip=1, thus to retrieve the Tile Number you must subtract 12 (0xC) to D.

Now we can enter the second part of the tutorial, what the Palette Number and the Tile Number really refer to!




2: Abuse the palettes:

It's nice to know that the Palette can take a number from 0 to 15 and that the Tile Number can be anything from 0 to 1023, but what good does this do if you don't even know how this data is interpreted?
Which is where DeSmuMe comes to the rescue!

If you open your NSMB ROM with the emulator and play through a level, pause the game and then go to Tools -> View Tiles.
This will open the TILE VIEW window.
Select 256 colors.
In the first combobox beginning from the top, select Main screen ExtPAL 3.
In the second combobox, you can toggle between A-BG - 0x6000000 and A-BG - 0x6010000.
For the palette, select something between 8 and 11 inclusive.

Now look what we have there:


Doesn't this look familiar?
    

It sure does. This is because of several factors:
_the FG .ncg is stored in the VRAM at address 0x600A000.
_the BG .ncg is stored in the VRAM at address 0x6011000.
_the palettes for FG and BG are always loaded in Main screen ExtPAL 3.
_Palette Number for FG is 8 or 9 by default.
_Palette Number for BG is 10 (0xA) or 11 (0xB) by default.
Be careful, the BG is written before the FG, which means that you can completely overwrite the BG with the FG due to the former being written in the VRAM at a later address than the latter.

Look at the palette numbers! Those are the exact same numbers than in the .nsc… is this a hint?
The conclusion is really simple, both FG and BG can read from palettes 0 to 15, which automatically includes palettes 8 to 11.
What does it mean? That you can make the FG read the BG palette on top of its own and vice-versa! Pretty neat, isn't it?

But that's not all, what I actually shown you was just the icing on the cake, but where's the main treat?
If you continue to read you can eat that cake at your heart content!




3: Abuse the tiling:

Remember what I told you about the Tile Number, which can take a value between 0 and 1023.
Now have you noticed that in the FG .nsc, most of the time no Tile Number was under 256 (0x100)?
This is where the VRAM read Tile Number 0x100 (pinpoted thanks to the magenta square):

Which matches the address 0x600C000

In the same vein in the BG .nsc, no Tile Number was under 576 (0x240)?
Tile Number 0x240 is read there in the VRAM:

Which matches the address 0x6011000

So where would Tile Number 0 ends up in the VRAM?
An answer that can be answered mathematically once again:
(0x6011000 - 0x600C000) / (0x240 - 0x100)
= 0x5000 / 0x140
= 0x500 / 0x14
= 0x40 or 64 in decimal

So this means that 1 Tile with a vertex of 8 pixels occupies 64 (0x40) bytes in the VRAM.
If we want to demonstrate with a mathematical reasoning where would Tile Number 0 be read, we need to follow this formula:
V-(T*D)
where:
_V is the VRAM address
_T is the Tile Number who is read at address V
_D is the Tile Number data size, which is always 64 (0x40)

Let's see:
0x600C000 - (0x100 * 0x40)
= 0x600C000 - 0x4000
= 0x6008000

Let's calculate again:
0x6011000 - (0x240 * 0x40)
= 0x6011000 - 0x9000
= 0x6008000

Both results match, and indeed it is the case in a real setting too: Tile Number 0 is written in the VRAM at address 0x6008000.

As an additional proof, FG 5 .nsc has some Tile Numbers as low as 64 (0x40) which in the VRAM points to address 0x6009000.
0x6009000 - (0x40 * 0x40)
= 0x6009000 - 0x1000
= 0x6008000

You get it, Tile Number 0 -> address 0x6008000

But what about the highest Tile Number, the 1023rd one (0x3FF)?
0x6008000 + (0x3FF * 0x40)
= 0x6008000 + 0xFFC0
= 0x6017FC0

Tile Number 1023 -> address 0x6017FC0

All in all it means that the .nsc, by virtue of being able to read up to 1024 Tile Numbers, have an effective range of 65536 bytes (0x10000) from 0x6008000 to 0x6017FFF included!

AND this is how Nintendo did to add what would seem to be additional tiles to FG 5 and FG 60!




Additional notes:

Some more information before you go abusing that trick:
_SubNohara is written at offset 0x600A000 and has a native and max range of 0x2000
_Tileset 1 is written at offset 0x6003000 and has a native range of 0x7000, and a max range of 0x9000 (tiles behaviors have a max range of 0xD000 though, use the FG to your advantage)
_BG is written at offset 0x6011000 and has a native range of 0x5000, and a max range of 0x7000
_FG is written at offset 0x600C000 and has a native range of 0x5000, and a max range of 0xC000
The layers are presented in the order they are written in the RAM, which means that if 2 layers overlap, the latter will overwrite the former.
Also be careful about additional animations for some Tilesets and FG!


Some thoughts for NSMBe:
_due to this new information, I think the way NSMBe open the Top and Bottom Backgrounds should be changed, for example after clicking one of the BG, it should open a window from where you can choose a Tileset and then a FG (or BG if you choose to open a FG), once you have confirmed your choices, it will bring you to the Tilemap editor but with the increased range and 4 palettes.


NOTE 1: You can abuse this trick with the SubNohara V2 ASM-Hack, but Tile Numbers above 895 (0x37F) will fall out of range! This is because Tile Numbers above 255 (0xFF) automatically get added the number 128 (0x80).
NOTE 2: No tummy ache after eating this appetizer? Good, because after all it only was a prelude, or a hype tool if you wish for the next ASM Hack of mine, which will be the main dish if you allow the euphemism!

Include setting to freeze Timer per View:

How to use?
_click Hex Edit on the level you want to modify
_go to Block 8
_rearrange the window so that each row (View) contains 16 bytes of data
_go to byte 10 (counting from 0)
_this byte is for the music, since any music equal or above 0x70 is mute (according to the code anyway), this is the byte I chose to change
_to freeze the timer for the selected View, set Music bit 7 at 1, or simply put add 0x80 to the music number.



This is best used in tandem with this mod, who was also updated!


Works on a NDS.

The purpose of sprite 45 is to provide a player an emergency invisible brick in case he inavertedly destroy a platform (Mega-Mario, Bob-Omb, Giant Thwomp) that was needed to complete the level.


This sprite can spawn an unlimited number of times, even if you destroy it.


As you can see in this screen, since the sprite 45 actually detects a solid object 4 tiles left and 3 tiles down, the invisible brick won't spawn until the solid object is destroyed.



1 Usually you can leave Camera X and Y values as 0, but sometimes you need to put values in there :

The entrance 3 doesn't actually have any purpose in-game (in fact it doesn't even exist in that level) but to showcase the coordinates.
The purple rectangle delimits what you can see on the NDS screen.
If at least one of the Camera values is different from 0, then the tile at said coordinates will calibrate the camera and will serve as the top-left tile of said camera.
You usually use them when sprites 198-199 and/or 276 are in the way, or eventually to calibrate the bottom of the camera to the bottom of the zone.
The purpose of this is to show a nice transition when you change areas.

With the example earlier if both value were at 0, this is where the camera would spawn by default.

The camera is 1 tile higher than the bottom of the zone, but the biggest offender here is the sprite 276, it is only acknowledged when the player have control of Mario thus only when Mario completely exits the pipe, the camera would recognize sprite 276 and then scroll to the left at high speeds, which results in an ugly transition and you can bet this is a rookie mistake to leave that kind of camera error unchecked.


2 I'm assuming you're talking about bottom and top backgrounds in levels, then yes there's a way to change the palette.

3rd byte (in red) is the .ncg, 5th byte (in green) is the .ncl.
Instead of double-clicking an area or clicking Edit Level, you should click Hex Edit, from there go to block 3 (if you want to work on the bottom background) or block 5 (for the top background).
One trick you can use with palette changing is that since animation is tied to the .ncg and not the .ncl, you can for example put the background 4 (Clouds) with the palette 59 (Yellow clouds) to create Yellow clouds with animation.

3 No you can't, it doesn't work like that.
That being said, there's a way to put more than 2 palettes (this trick works only for tilesets AFAIK).
Each tileset can handle a maximum of 4 palettes, but the only one who natively use 4 palettes is the tileset 9 (Beach), export the .nmt then import it in every slot you want to use 4 palettes, but you'll have to do everything else by yourself (like you would do when creating a new tileset).

Thanks.

Here's something I did and I will share, I'm going to list all the tilesets who don't have randomized tiles:


Also, there are 4 oddities when it comes to randomization, the four underground tilesets (3, 35, 36 and 73) actually have 2 rows of randomized tiles !
The first one for tiles 0 to 5, as always, and the second one for tiles 48 to 53.

Not a level per say, but I thought it would be nice to showcase some cool things Bowser Jr. can do.
Everyone is free to borrow the idea.

Also if "Impossible to stomp on" is enabled, Bowser Jr. will try to flee during the 3^rd phase ; if he manages to do so, you will have to throw yourself into a pit and lose a life.

So what is this?

Not only he left the place, not once but twice, because he was butthurt and couldn't take advice without throwing a hissy fit but on top of that he thinks he can come back and waltz in like nothing ever happened?

NO!

After his poor behavior, hamza better do a thorough apology.
And I personally won't approve nor acknowledge his posts until he does.

What I'm going to say is not nice but it has to be said, we're better off without someone who can't pay due respect to his superiors.
Really mods and admins are supposed to be respected, what do you think will happen when they let someone who can't control his "mental breakdowns" back without sternly lecturing him, hmm?
I'll tell you, mods/admins will lose their "dignity" so to speak and their reputation will be tainted.
A community whose leaders let their members do as they please will surely collapse!

Maybe I'm taking this to much at heart. But really after hamza "threatened" to leave the place twice, one can only reach the conclusion that some mistakes are NOT to be allowed.

Is leaving a forum and coming back so much of a simple thing?

WHAT DO YOU THINK POSTING OR MODERATING A FORUM IS, A KID'S GAME?!!

I'm willing to let bygones be bygones and give hamza a chance at redemption, BUT, if hamza has no intention of asking for forgiveness and tries to pass under the radar, then the next one to go is ME!
And unlike hamza I will keep my word. I would rather stay at the station watching the train wreck happening from afar rather than being in said train when that happens.



This is not in the moderator section because you know, I'm not a mod. But I think it's better that way because it allows for anyone who wants to to give their opinion on this, even you hamza.

To the mods: If you consider to delete my post and the thread, I want you to at least know that the purpose of this thread is not to cause drama but rather I think it's necessary to straighten things out.

Sprite database methodology

I Semantics
    1 Trigger IDs
    2 Target IDs
    3 Comparatives
    4 Upper cases
    5 Common parameters
    6 Official names

II Sprite Data

III Eventual changes


I Semantics

1 Trigger ID:
Trigger ID: A Trigger ID, like its name implies, is a trigger that allows a sprite to take action.
Trigger IDs often acts themselves as checks, that is if the Trigger ID is null, the sprite will simply ignore it.
More often than not sprites happen to have a second Trigger ID, in that case it must also be null for the sprite to ignore it.
In that case Trigger ID on bytes 2-3 is the first one, while Trigger ID on bytes 0-1 is the second one.
Rarely, in cases were the sprite have 2 Trigger IDs, you must call at least Trigger ID 1 to pass the check.
Some sprites have a bit whose sole purpose is to act as the Trigger ID check instead(called Use Trigger ID in the sprite DB); if this bit is active then the sprite will take action only after the Trigger ID has been called, otherwise the Trigger ID is ignored.

There are several categories of Trigger ID besides itself:

Bridge ID: This is a Trigger ID used by Bowser, Dry Bowser and Giant Bowser.
This is the ID the Skull Switch targets to, it triggers the falling animation of the aforementioned bosses.

Starter ID: This is the first Trigger ID called by the Multi-chainer controller.

Finisher ID: This is the last Trigger ID called by the Multi-chainer controller.
Note that Finisher ID must be superior to Starter ID since the Multi-chainer controller increments by +1 each time a Trigger ID is called.

Destroyer ID: A special case of Trigger ID.
While a Trigger ID usually spawn a sprite, a Destroyer ID, as its name implies, will despawn the sprite upon being called.

No matter the category of the Trigger ID, its effects can be reversed by disabling it.


2 Target ID:
Target ID: The Trigger ID's counterpart. A Target ID is a Trigger ID the sprite will set On once it takes action.

Random ID: A special case of Target ID called by the Random output controller to determine which of the 4 Random ID is going to be called.


3 Comparatives:
Bigger, smaller, longer, shorter, slower, faster: those are the likeliest comparatives you'll run into when browsing into the database.
Comparatives are special in that they should be one of the few cases you should use the check box at all.
Example: You see a check box saying: "Load from checkpoint".
At this point you should think: "But wait, what if I don't tick the check box? What'll happen? Where this sprite will load? Will it load at all?"
Whereas if you see a check box saying: "Faster", you'll logically think: "So if I don't tick the check box, I know that this sprite won't be as fast as it could be."


4 Upper cases:
Multiple words beginning with upper cases should be allowed only on sprites that have an official name AND are labeled as such (for example Banzai Bill Blaster where all the words begin with an upper case letter).
Else please… please people, don't abuse upper cases letters for the sprites' names, thank you.


5 Common parameters:
We want consistency, so we want to use these whenever possible:

Loads from: usually as a 'Level start' and 'Midway point' list
Height: if it has more than 2 settings; use a comparative + check box otherwise
Length: if it has more than 2 settings; use a comparative + check box otherwise
Size: if it has more than 2 settings; use a comparative + check box otherwise
Speed: if it has more than 2 settings; use a comparative + check box otherwise
Starting direction:
Starting position:
Direction:
Rotation:
Shift position:
Sticks to a line: as a Yes-No list
Trigger ID:
Target ID:
Zone ID:
Path ID:
Starting node:
Last node behavior:
Use Trigger ID: as a Yes-No list
Use Zone ID: as a Yes-No list
Timer:
Tiles to move:


6 Official names:
Several objects from NSMB got an official name, use them whenever possible.





II Sprite data formulas and calculations

For each Class ID, parameters are listed from the likeliest used parameter to the unlikeliest used parameter.
For the Speed parameter: default speed is often 60 pixels per second.

Sprite 28 (Class ID 35): Self-destruction, if set, happens in 240 frames, or 4 seconds.

Sprite 33 (Class ID 237): Small version bounce up by 6 tiles (11 if Mini). Big version bounce up by 18 tiles (29 if Mini).

Sprite 34 (Class ID 151): The shift position bit, if set, also make the Red Ring respawn if its Area is reloaded.

Sprite 68 (Class ID 161): Length formula is 1+(N₁₁ mod 8).

Sprite 71 (Class ID 165): Length formula is 1+(N₁₁ mod 8). Height formula is 2^{N₈ mod 4}.

Sprite 72 (Class ID 166): Height formula is 2^{N₈ mod 4}.

Sprite 73 (Class ID 169): Max tilting formula is 60/2^{N₈ mod 4}.

Sprite 77 (Class ID 173): Length formula is 2+2×(N₁₁ mod 4).

Sprite 103 (Class ID 79): Size formula is 1+(N₆ mod 4).

Sprite 119 (Class ID 228): Amplitude formula is 11.25×N₅. Oscillation period formula is 1024/N₆.
Starting position formula is:


Sprite 126 (Class ID 230): Maximum angle formula is 11.25×N₇.

Sprite 136 (Class ID 98): Height formula is 2+(N₁₁ mod 8).

Sprite 233 (Class ID 184): Height formula is 4+(N₁₁ mod 8).

Sprite 239 (Class ID 191): Actual movement is N₉-N₁₀. + will go up. - will go down.

Sprite 249 (Class ID 209): Length formula is 4+(N₁₁ mod 4). Height formula is 4+(N₈ mod 4).

Sprite 268 (Class ID 124): Horizontal shifting formula is 2×N₁₀.

Sprite 297 (Class ID 167): Height formula is 2^{N₈ mod 4}.





III Changes proposals

Due to new discoveries, standard goes up and what used to be breathtaking yesterday could be considered sub-par today, such is the side-effect of progress.
With that I mean that it would be nice if the Sprite database was switched to a Class ID database instead.
Since the Sprite is merely a link to the Class ID, the one who holds the real data is the Class ID.
This would allow us to put the data found in this thread most notably.
NSMBeditor would still have to read the Class ID via the Sprite, which can be done by decompressing overlay 0 and reading the 652 bytes (rather 326 words) from:

On the same vein, Sprite sets really are Class ID sets.





IV Notes

The sprite database overhaul was an issue brought up Sep. 6th 2014, and I only put it in motion May 3rd 2015.
I sure took my sweet time, oops…


I already changed most of the data as to satisfy the methodology.
There's still much left, but the DB is getting there.


Data that make the game crash on a real NDS have NO business in the database (with the notable exception of Sprite 274), the reasoning being what point would be achieved to know that putting nybble 11 at 2 on sprite 43 will crash the game for example?

Lel I'm going to set it on 2 anyways *plays on real NDS, play, play, play, playity, play, oh encounters Chain Chomp**crashes the game*. Wow! Amazing! Except for crashing the game, I've made no advancement, geez I wonder why?

See for all intents and purposes data like that should be wiped out the database, it does absolutely nothing for the average players except maybe confusing them.



If anyone as something to say, feel free to do so.

I'm glad to present you Pokémon MindCrystal, a mod of Pokémon SoulSilver.

I warn you though, this hack is available only in French.

The crux of this hack is obviously the inclusion of the Fairy-type at 100%.

Most of the changes were done from a technical standpoint.
These are the few parts of the storyline that were changed as of now:

• the girl in Ilex Forest gate that gave you the TM12 now gives you instead the Eviolite,
• all 16 Gym Leaders first teams got revamped, as well as those of the Elite 4, Lance and Red.
• all 16 Gym Leaders second teams got revamped, as well as those of the Elite 4, Lance.
• the inclusion of Lv.100 battles against Gym Leaders, Elite 4 and Red after defeating the latter for the first time.

Grab the xDelta patch at the bottom of this post and patch it with a French version of Pokémon SoulSilver.

• Revamped type-chart to include the Fairy-type matchup as well as all the neutral match-ups.
• Pixie Plate implemented.
• Roseli Berry implemented.
• Fairy-type Arceus in place of ???-type Arceus.
• Updated Judgment to take into account the Pixie Plate.
• Pokédex fully updated to take into account the Fairy-type in Research mode.
• Conversion updated to take into account the Fairy-type.
• Conversion 2 updated to take into account all 324 types match-ups.
• Battle Hall includes the Fairy-type row.
• Fairy-type icon.
• Pokédex Fairy-type icon.

Fairy-type moves:







Battle Frontier:

• Shiny lock removed for opponents Pokémon in all 5 facilities.
• New items available for purchase.
• Battle Frontier Pokémon will always have an IV of 31 in all 6 stats.

Battle Tower:

• Shiny lock removed as well for the NPC partners in Multi Battle mode.

Battle Hall:

• As said earlier, Battle Hall includes the Fairy-type row.
• You still fight in rounds of 10 battles.
• The Silver Print is now obtained by challenging and defeating Argenta on the 80th battle.
• The Gold Print is now obtained by challenging and defeating Argenta on the 180th battle.
• Other mechanics inherent to the Battle Hall were updated to grant a flawless experience of the facility.

• Shiny chance is now 1/4096.
• Having a Pokémon with the Ability Super Luck leading the party increases the likelihood of encountering a wild Shiny Pokémon.
• Shiny generation from "forced shiny encounters" method was slightly altered to take into account the modified Shiny Rate.
• +50% Physical Defense boost for Ice-types under Hail.
• Soundproof check against Heal Bell removed.
• Stealth Rock damage is decreased by half.
• Fixed the move Hail, basically in gen IV the way Hail is coded allows you to use Hail despite Snow Warning.
• Fixed the move Fire Fang so that it doesn't hit through Wonder Guard anymore unless it happens to be super-effective.
• Hidden Power can be Normal or Fairy type now as well, the Hidden Power NPC will notice this too.
• Hidden Power no longer takes into account Speed to calculate the type.
• Some Base Stats were upgraded to help some Pokémon perform better (for example Persian or Probopass).
• Castform and Cherrim alternate forms now display their respective icon during battles.
• Castform's alternate forms now display their respective type when checked through the menu during battles.
• Fixed Strength graphical glitch that also occurs in the original versions.
• Fixed Facade graphical glitch that also occurs in the original versions.

• Battle Style is now permanently locked on Set.
• You can't use items from your bag against a Trainer, very much like against Battle Frontier Trainers!
• All Trainers' Pokémon have now 31 IVs in all 6 stats.
• All Trainers' Pokémon have now 255 EVs in all 6 stats.
• All Trainers' Pokémon have now the possibility to easily get beneficial natures.
• All Trainers' Pokémon have now the possibility to be shiny.
• IVs for opponents' Pokémon can be chosen from a pool of 64 combinations, most notably to capitalize on Hidden Power, Gyro Ball and Trick Room.
• All Trainers' Pokémon can now be contained in Balls other than Poké Balls.
• The number of possible seals combinations for opponents' Pokémon went up from 28 to 216.
• Ace Trainer Lois replaces Juggler Irwin in the Pokégear, you can set a rematch with her on Wednesday afternoons (10:00 to 19:59).
• ASM hack to allow more than 737 trainers in-game (complete with text).
• Continuity for opposing Trainers is preserved, by that I mean that the IVs, nature, shininess and gender of opposing Pokémon stay the same (for example Falkner's Pidgeot is canonically the same creature as when he was only a Pidgey).

• A new item was created, the Evolutor, which when applied like an Evolutionary Stone to a Lv 100 Pokémon, allows it to evolve if it can do so!
• Eevee can now evolve into Leafeon if leveled-up at Ilex Forest or Viridian Forest.
• Eevee can now evolve into Glaceon if leveled-up at Ice Path or Seafoam Islands.
• Magneton and Nosepass can now evolve into Magnezone and Probopass respectively if leveled-up at Team Rocket HQ, Route 10 or Power Plant.
• Feebas, on top of requiring a beauty's stat of 170 min, is now required to level-up at least at level 20 to be able to evolve.
• Feebas gains a second failsafe evolution method in case the Sheen is maxed before the Beauty stat reaches 170.
• Female/Male Kirlia evolves into Gardevoir/Gallade at Lv 30.
• Female/Male Snorunt evolves into Froslass/Glalie at Lv 42.
• Female/Male Clamperl evolves into Gorebyss/Huntail with the Dawn Stone.
• Pokémon that require a trade to evolve all gained an alternate method of evolution.

• Incenses babies are now the default base form.
• Miltank and Tauros are now considered the same species for breeding purposes.
• Feebas/Milotic and Magikarp/Gyarados are now considered the same species for breeding purposes.
• A new NPC, called the Egg Move Tutor, makes an appearance; as the name implies he is capable of teaching your Pokémon moves that normally it has to know from birth, but also level-up moves that only pre-evolutions can learn, and for some Pokémon moves that they have no other way to learn, but you'll have to spend a hefty 200 BP to pay for his services!

• Gender ratios are fixed, with that I mean that for example 1 male per female REALLY means 1 male per female (and not 129 males for 127 females).
• Ponyta, Rapidash, Gardevoir, Feebas, Milotic and Gorebyss are now female-only.
• Magikarp, Gyarados, Glalie and Huntail are now male-only.

• EV limit is now 1530, you can max all stats now.
• The new EV limit also applies in the Battle Frontier.
• Vitamins cap at 255 EVs now.
• Lv 100 Pokémon can gain EVs by fighting now, but they still need to be deposited in the PC for the stat gains to take fully effect.

Updated Items:

• Light Ball benefits Pichu and Raichu as well now.
• TM45 and TM78, which contain Attract and Captivate respectively, have been updated with a Fairy-type TM icon.

New Items:

• Pixie Plate
• Roseli Berry
• Eviolite
• Evolutor

• If possible, moves were upgraded to match Gen V+ information.
• Nerfs from Gen VI are NOT applied (this means that for example Surf and Hydro Pump remain at 95 and 120 power respectively).
• Even moves like Tail Glow, which should boost the Special Attack by 3 stages, have been updated successfully (complete with the text).
• Acupressure now works if the user is behind a substitute.
• SFX for some moves were altered to suit them better.

Updated Abilities:

• Stench (Gen V+ behavior)
• Sturdy (Gen V+ behavior)
• LightningRod (Gen V+ behavior)
• Sand Stream (now makes the user immune against sandstorms)
• Simple (Gen V+ behavior)
• Storm Drain (Gen V+ behavior)
• Snow Warning (now makes the user immune against hailstorms)

New Abilities:

• Sheer Force
• Defeatist
• Multiscale
• Poison Boost
• Flare Boost
• Overcoat (Gen V behavior)
• Regenerator
• Sand Rush
• Wonder Skin
• Analytic
• Infiltrator (Gen VI behavior)
• Sap Sipper
• Prankster
• Sand Force
• Fur Coat
• Bulletproof
• Strong Jaw
• Refrigerate
• Gale Wings
• MegaLauncher
• Tough Claws
• Pixilate
• Aerilate

• Text Speed is now permanently locked on Fast.
• Battle Scene is now permanently locked on On.
• National Pokédex is the default mode upon beginning the adventure.
• Player's Mom can now buy batches of 5 Roseli Berries as well.
• Roseli Berries can be occasionally held by wild Absol.
• Game runs now at 60 FPS ! Allowing for much quicker battles.
• Several sprites changed/fixed.
• Some shiny sprites recolored.
• ORAS mini-icons.
• Custom Flygon, Togekiss and Gallade sprites.
• Replaced Sky Attack move tutor with Zap Cannon.
• Roseli Berries can now be planted in Berry Pots, they have the same growth and moisture drain rate as the other damage-reducing berries.
• New movesets and egg moves.
• Routes 26, 27, 28, Tohjo Falls and Victory Road will always play the Johto versions of the Wild Pokémon theme and the VS Trainer theme.
• Lyra was fully replaced by Kris.
• All 7 Fossils are available now at Ruins of Alph.
• The timeframe window to react to a rod bite has been doubled to make up for to the game running at 60 FPS while fishing.
• Fixed the quiet tune on map 108 (Route 45), a glitch that also occurs in the original versions.
• Score calculation for the Bug-Catching Contest was modified to take into account shininess.
• Pokédex entries got upgraded to match those of Pokémon Crystal (001 to 251) and Pokémon B2W2 (past 251 whenever possible).
• Gender will always be displayed, even for both Nidorans.
• Lugia and Ho-Oh Kimonos' cutscenes now co-exist.
• Bugfix: Fixed Kris' frames when riding a bicycle to the left.
• Bugfix: Fixed glitched Trainer names with 8 characters or more.
• Bugfix: Fixed 4 mistakes on overlay 18 that made the game hang upon sending some Pokémon according to their abilities. (thanks Asia81)

Title Screen:



All of those modifications were carefully tested on a NDS, so as to reduce as much as possible the eventual bugs that might occur.

Credits:
_Nintendo
_Game Freak
_Creatures, Inc.
_Sora Ltd. for developing Super Smash Bros. Brawl, from whom Suicune's model on the title screen is taken from
_Gregarlink10 (http://gregarlink10.deviantart.com/) for making Kris' spritesheet
_NyaChan (https://twitter.com/nyachan) for making the Title logo (http://forums.bulbagarden.net/index.php?threads/the-bulbagarden-conversational-chat-thread-vol-2.57572/page-31#post-1504991).

Enjoy

Link to beta 2.0:
http://www.mediafire.com/download/lz83do1q3gc331b

Some cool things you can do with a little knowledge of ASM:























If you want to test yourselves, here's the download link:
http://www.mediafire.com/download/1l2zim2rdjyne6x
To patch with the European version of NSMB.

The only hack not featured is the Horizontal scrolling for Sprite 255.

Go there to fetch the updated code!
While the Blockhopper code is mostly unchanged, the code now takes into account the remaining Jyotyu tiles in the enemy folder.

Star Coins are worth 4000 points:

This is a porting of the code into ASM-Template format, but this is not the main topic behind my post, however:





Tested on a NDS.
Dedicated topic tomorrow, because right now I'm too tired due to the fact that NSMBe doesn't know how to handle .bncd files in 8bpp mode, pretty much forcing to edit the files the old-fashioned way (read: hex-editing).
I warn you, this is not quite what you would expect: while world-map icons no longer are restricted to 15 colors, they have to share the common 255 palette, this will be explained in detail.