Working on an idea for descriptor text. This is just a rough mock-up - it wouldn't actually move at that speed, or style. I would aim for text that scrolls all the way across, and then loops. (like in the Oracle games)

If you did not have an item highlighted, you would only see the menu border in that area.

Let me also say that I am really aiming for something flexible, here. If I find a coder, maybe the game can be coded in such a way to allow modifications to its assets. (map layouts, events, text, etc.) This could be used to allow other community members to produce their own Zelda games using assets provided here. We could also include dummied items for potential future games; such as the Roc's Feather, Ocarina, et al. (none of which will have a function in this game, but their code will no less be there for future games)

I think this could be a great community project, overall.

Hmm, I like it, although I'm thinking that if you put the name of the item on the top and have the description at the bottom then it will be a little less cluttered for the description.

Nice layout btw.

I'm making a pass at dungeons now. This is a working idea for level 1. Frankly, it is ridiculously difficult to design dungeon rooms in the alloted space. Practically no room for puzzles, no room for bosses, no room for more than a couple of enemies at a time, etc. I tried to improvise as much as I could.

This is only the first floor. There is a lower floor that represents the boss room. That's the biggest nightmare. The boss takes up 32x32 px, and it or Link will barely have enough room to breathe.

I'm pretty stressed after trying to mess with this. I can't emphasize how much time I've spent just trying to improvise solutions to the design. I would certainly be open to suggestions; but they have to work within current limitations.

Boss are 32x32 at the most. A couple are 16x16. (which is a relief to work with)

The only problem is how I've planned things, versus what I'm capable of. For instance: The first boss is a giant octorok. It can't be giant if its sprite is only 16x16 px.

Now I'm tempted to throw out that octorok and do a 16x16 dodongo, like you said.

Mhmm, I doubt the calc limits the amount of tiles at 191. 191 16x16 4 lv gs sprites are like 12224 bytes large total (You can fit like 256 in one Flash page, if I am right, since a flash page got 16384 bytes and each sprite takes 64 bytes of RAM). You can It seems more like a CalcGS limitation to me

Is there any alternative to CalcGS? CalcGS is like 10 years old.

EDIT: WOW Nice dungeon layout! I sure hope this won't get cancelled. I would like to see someone put this into code.

I'd agree with DJ, this sounds like a Calc GS issue to me. I'm not sure what to suggest as an alternative. Could you break the project into seprate Calc GS files(I've never used it so I am unsure how it is setup)? As far as dungeon space feeling cramped the only thing I can suggest (which would require reworking) is the same I did before. Allow scrolling and ditch the side HUD.

True, I get errors when opening some chipsets in Windows 7 64 bit. You could maybe ask for help in the help section, preferably the ASM section, as the format you need for sprites being edited is hex or binary (preferably hex, though, so it's easier if someone decides to use Axe Parser for such project). You could also maybe ask on Revsoft, if your account there is still active, as I believe some other people still lurk there, waiting to answer questions.