Hm.. okay. I was wondering:

- With the 'unlimited MvsL spriteset' ASM Hack you can use all sprites in MvsL, but some Mario animations won't work.

- With this ASM Hack all Mario animations work and you can use all sprites... except Battle Stars.

Is there something I can do so that all sprites* (including the Battle Stars) and all animations work?

(*It doesn't matter if I won't be able to use the sprites from sprite sets 16:0 to 16:8)

That's interesting, 'cause one of the unused multiplayer levels (the unused level 3, I think) has vines in it. That's why it went unused, perhaps…

---

I could not…

Okay, but..



This is the ASM Hack. According to your first post, the first part of the code causes sprite set 16-9 to be unavailable, and some of the other parts remove the code that spawns the Battle Stars. I assume that one of the remaining parts causes all Mario animations to work. (And I guess that the other remaining parts cause all tilesets/backgrounds to work)

Do you remember the meaning of each part of the code? Because then, I can use the 'unlimited MvsL spriteset' ASM Hack and this ASM Hack, without the parts that cause sprite set 16-9 to be unavailable and the Battle Stars not to spawn.

Sorry for being impatient, but is anyone going to reply?

You know, the "race" idea could still work, such as long as the players don't de-sync (both would have to end the level somehow).

Would you mind if I used this code sometime??
_________________________
Kuribo64 / NSMBHD / MMM / IBC / EventHubs

NNID: GreenThunder1337
3DS FC: 1521 - 5979 - 1511

I don't think  GreenThunder1337 is going to reply on this. He hasn't been active on NSMBHD since he asked if he could use the code.

About my last post on this thread:
It's a shame that those ASM hacks aren't like Lego bricks. That would make things much easier xD. But still.. each part of the ASM Hack does do something else. If you could edit the first post so that there's a short description at each part of the ASM Hack, which tells what that part does, than it would be (I guess) easier for other ASM Hackers on NSMBHD to find out something to make I was talking about here:



Of course, I understand that there's the possibility noone here wants to spent so much time to find this out for me, but maybe there's many other people too who'd like to be able to make MvsL levels with all of Mario's animations.

To make a race-like multiplayer game mode.

I've been trying to figure the code out, figure out what I would even do to prevent de-syncing and so on.

But yeah, if I ever do figure this out, would you mind me using it? With all due credit, of course.
_________________________
Kuribo64 / NSMBHD / MMM / IBC / EventHubs

NNID: GreenThunder1337
3DS FC: 1521 - 5979 - 1511

I guess you're allowed to use it. If you weren't, the code wouldn't be in this thread's first post.

I finally have the access to two DSs, so I wanted to try this ASM Hack. But unfortunately I don't really get it to work.

I've set the ASM Hack in NSMB, and put it on my two flashcards. I replaced the Ice stage with an area of a Ghost House level (without the Star Coins). But when I tested it, I still got the original Ice stage. There weren't Battle Stars btw, so the ASM Hack does (sort of) work. After that I replaced the Ice stage with the same Ghost House area, but then in 'FS\root\archive\Dat_Ice.narc' instead of in the Level list. When I tested it, I got this screen on both DSs.

What did I do wrong?

Sorry for being impatient, but is anyone going to reply?

That's a crash

This would normally be a "freeze", and then you can see the crash screen by pressing a secret key combination.
The ASM hack template forces the crash screen to show without the key combination, and adds a RAM viewer. You can toggle between the crash dump and the ram viewer by using Start/Select.

The crash screen gives more info about why the crash screen happened. You can see the registers when the crash happened on the right of the top screen, this can give you info of what function crashed if you look at the PC (Program counter) register, if you look it up on IDA it can give you clues. Bottom screen contains the stack, from it you can kind of see the chain of function calls that led to the crash.

Good luck