It's not possible to have sufficient detail at a smaller resolution, though. Once you go smaller, you start to lose details such as the white daggers inside of the Z. It was actually pretty difficult to get it to that small of a resolution without too much bleeding.

I figured this was going to be more of a title card logo, like how the GBA games handle the title. Pressing a button would then take you to the character screen where you would see the traditional-style character-selection.

uhuh so that one is noting the swords level right ?

Right. Now that you mention it, though, I can see where it might be confusing. I might think about moving it down, like how the rest of the items have it positioned. That, and I may move the bow away from the sword so it doesn't cause any confusion.

EDIT: Here is an updated version, with a second inventory full of upgraded items for further comparison:

kk, and what do the "(L1)"/"(L2)" things mean?

Level. This is fairly common in some Zelda games, where items have multiple levels. i.e., a L2 sword is better than an L1 sword.

I've redone the quest screen a bit:



The very bottom row is your status HUD, which is displayed both on this screen, and while exploring. I wanted to keep the height at 8 px so it doesn't intrude too much on the action screen.

I had a few ideas for an enhanced remake of the original Legend of Zelda on 15 MHz calculators. Maybe "remake" is not the appropriate word, so much as a rendition, or watered-down port with a few enhancements.

The plot and flow of gameplay will be slightly different. As opposed to Princess Zelda separating the Triforce of Wisdom into 8 sections and dividing them across several dungeons, Link's task is to find each whole piece of the Triforce in order to break the seal on Princess Zelda's prison within Ganon's Citadel. This doesn't necessarily limit the game to three dungeons - there will be dungeons where important items are guarded by bosses. It it necessary to procure these items so Link can reach other sections of Hyrule and ultimately uncover the Triforce. Some dungeons will also have seals that require to specific Triforce pieces to be in your inventory.

I've cut down on the number of items present in the game. It's rounded down to four equippable items, (Link may only equip a single item at a time) four "quest" items - or items that have passive effects - and of course Link's tunic and shield. The complete inventory is:

Wooden Sword (L1) - inflicts 1 point of damage against enemies; some enemies are immune to this sword
Magical Sword (L2) - inflicts 2 points of damage against enemies
Wooden Shield (L1) - blocks very few projectile attacks (but cannot be eaten by a Like-Like)
Magical Shield (L2) - blocks most projectile attacks (but can be eaten by a Like-Like)
Hylian Tunic (L1) - does nothing (it's simply your default tunic)
Hero's Clothes (L2) - halves all damage inflicted against Link
Magical Bow - fires arrows that allow Link to penetrate some enemy defenses (each arrow subtracts 1 rupee)
Bombs - can damage multiple, adjacent enemies, or destroy weak objects; (walls, blocks, etc.) Link's initial bomb capacity is 8, but it is possible to purchase an upgrade to 16
Switch-Hook - when fired at an object, Link switches places with it; (this is effective against enemies or movable pots) stuns enemies that are too heavy to switch places with Link; will grab objects such as keys or rupees and add them to Link's inventory, as opposed to switching places with them
Giant's Ring - allows Link to push certain types of blocks
Fire Arrow - allows arrows to light torches
Flippers - allows Link to swim in watery areas
Water of Life - when Link loses all hearts, this will automatically restore 3 of them (and then vanishes from his inventory)



I haven't designed any maps yet. Since the sprites will be 16x16, I was thinking of doing 8x8 map tiles. Each of the boundaries around each action screen could be composed of 8x8 sprites that only show halves of trees and mountains, which should help prevent any given screen from becoming too cramped with large objects. Tiles within the boundaries would still make 16x16 px objects. Each action screen would only be 96x64 pixels.

Link's status is also a bit different. I thought only 8 total hearts would be sufficient. (3 to boot) There may be more than 5 Heart Containers to be found, and I say this for two reasons: 1.) Games like Metroid did this with Energy Tanks, in case the player did not discover them all; and 2.) There will occasionally be situations where you will lose a Heart Container. (i.e., the "Leave your money or leave your life" choice in some rooms)

His name was originally Fenris. (which was derived from Fenrisúlfr / Fenrir / Fenris wolf) I added (-son) as a patronym.

There were also two other playable characters in the game. I removed them for a couple of reasons: 1.) Their roles weren't important to the game at all. I would have to develop on these characters who really didn't have any significance to the story; and 2.) I wanted this to be more of an RPG that draws the player directly into the character's role; like Arc the Lad, Zelda, etc.

This is a reboot of a project I started a few years back. Although it was never completed, it was still a very influential project for future works. I figured I owe it to myself to give this game (my first game) the detail and depth it deserves.





Comparison of the original designs:





The game centers around an apprentice knight named Fenrisson, who serves under the leadership of Captain Darius of the Knights Glendale. Prior to the game's events, Darius betrayed the King of Glendale and set out in search of a relic rumored to grant its holder the power of dragons. Although many of the king's men attempted to stop him, none were successful. One particular knight was Fenrisson's own brother, who never returned from his journey to Darius' citadel. Although a lowly apprentice, Fenrisson is determined to find his brother and put a stop to Darius' evil plans.

The story really isn't very robust. The game emphasizes questing and exploration over the finer details of what's going on, or why. The general flow of the game is that Fenrisson will explore new areas, learn details of the whereabouts of Darius' citadel, or learn about requirements he must meet to travel to the next area. (such as keys or relics that need to be discovered before proceeding) The maps are all presented in a 1:1 scale, and each area leads to the next. There is no general overworld with small icons representing towns and dungeons. For instance: Every time you need to reach a particular village, you actually need to roam through the wilderness between point A and point B to get there.

Enemies are placed directly on the maps. (no random encounters) You can selectively choose when you want to fight an enemy. In some cases, an enemy may be blocking your only available path. Battles take place on the same maps by transitioning into a turn-based input sequence. The player registers commands by simply selecting which item in Fenrisson's personal inventory to use. These can be weapons, shields, potions, etc. Each of these items has a quantity, or durability level, that defines how many times it can be used before it needs to be replaced.

Fenrisson's statistics randomly increase after battles depending on several conditions: Which items he put into application, how much damage he suffered, how many attacks he managed to evade, and so forth. There's no real disparity between how statistics between the player and the enemy function - these are within relatively similar ranges.

Overall, it's probably a 45-minute game. I hope to make exploration the largest emphasis, with robust dungeons, traps, pitfalls, puzzles and other interesting details to give the game more of an adventurous flair than some of my other projects.

Iambian should post his coding environment. It's nothing but wall-to-wall icons and task buttons at all times. I think he has some 30 quicklaunch items alone.