I didn't do it nobody saw it you can't prove nothing she said she was 18 I LEARNED IT FROM YOU OKAY *runs out of the room sobbing*

(context: this was posted just after the board came back up from its "nap")

--------------------

What's this, an untranslated debug menu.

--------------------

I once posted from Telnet, but with all the bot/spammer/idiot checks in place now, I'd probably end up tripping one if I tried that again.

--------------------

So many Windows shots....


and then there's Awesome on Lubuntu.

--------------------

Chance of an English release: 90%
Chance of an official English release: ???

Fan translations, man.

--------------------

2D games have two common types of level format:

Object based: Used in most platformers, including Super Mario Bros 1-3 and SMW. In memory, the level is a grid of (usually 16x16) tiles. When loading a level, the grid is cleared to an "empty" tile, then objects are "drawn" into it. The data specifies e.g. "3x1 block of coins at position 12,34", "16x3 floor at position 0,28", etc.
Usually the grid is divided into 16x16 "screens" or "pages", and object coordinates are local to a page, with a special object ID signalling to move to the next page.
Object format is typically something like TT XY WH, with object type 0 or FF signalling the end of the list, potentially some additional parameter bytes, and some special "pseudo-object" types which don't draw objects at all, but use their position/size values to set parameters such as warps. (Lunar Magic uses such pseudo-objects to do all sorts of interesting things such as load ExGFX and override time limits and starting positions.)
In SMW, object type 0 is a special type, used for most fixed-size objects; in place of the size byte is the "real" object type. (i.e. 00 XY TT) In some games, certain objects just don't have a size byte at all.
Super Mario Bros 2 has a couple of interesting variations: you can specify what tile to fill the grid with (so a cave might be filled with rock tiles and then carved out with "air" objects, rather than built from "rock" objects around an empty space) and object positions are relative to eachother.

Tile based: Simpler, but generally less efficient for games with large maps. The grid is simply stored in ROM and copied directly into RAM. Usually compressed in some manner. Used in most top-down games, such as Pokémon.

3D games are another can barrel of worms entirely, and much more complex. You'll want to learn about OpenGL and be capable of programming a simple 3D scene before you look at those...

--------------------

That appears to be a variation of the broken moon jump code. It'll trigger unexpectedly (when Mario's Y speed hits certain values) and break some sequences; notably, you can't get the star in the wing cap course because it'll interrupt the animation.

To fix these, replace all D033B1BD 0020 lines with D033AFA1 0020. For reference, the fixed moon jump code:
D033AFA1 0020
8133B1BC 4220
D033AFA1 0020
8133B17C 0300
D033AFA1 0020
8133B17E 0880
note the third and fifth lines are identical to the first, to trigger on L button press instead of Mario speed.

--------------------

...one of many reasons.

Super Mario Bros might be one that converts on the fly? I don't know of any, but I haven't looked at it.

Originally posted by Lunaria

---

While one could argue that tile based is not as effective

---

Less efficient. It takes up more space. That's all.

--------------------

Ew, Samsung? Cheap trash...

--------------------

That's often the case... sometimes because the official translation is a censored dumbed-down version with unnecessary non-language-related changes, and sometimes because they're just terrible.

--------------------

Well I tend to drift more toward IRC than forums, I never really have much to say anyway, and I didn't have a working computer for a few months.

--------------------