It's been a long, hard road, but after a year's work, I've finished the demo of Guardian Cry, a 16-bit Zelda clone. Check it out!

The artstyle rules. It makes me nostalgic for DOS games like Quest for Glory

Congrats on the launch!

The demo was really fun! The music has very Binding of Isaac vibes (good thing!).

As usual I am stuck on the part where it teaches you how to play because I am extremely shit at games. Can someone give me a clue?

how do I get past this screen? I need to press the second button but can't jump across the black area because it's too far. A box popped about diving. How do you do that?

Play the demo y'all.

Nicely done! Some minor suggestions to make it even nicer:

• add a grace jump/coyote jump/ledge forgiveness mechanic (different names for the same thing). This means that when there is a platforming section, you get a few frames of "grace" when walking off a platform to actually perform the jump, making platforming less frustrating. I constantly accidentally ran off platforms before jumping on the way to the "second" emblem haha
• consider adding a boss health bar. This is more of my own personal preference and not a "must", and many games thrive on not showing this kind of information to keep the player guessing, but I personally would have enjoyed the fight more by knowing how well I am doing (my own health loss vs the boss's health loss), and how close I was to beating the boss on my failed attempts.
• on the way to the boss, one of the chambers (4th one if you take the fastest route) requires you to wait for the flames to disappear before you can proceed. While good for teaching the player how the flames work (and in general, the dungeon is nicely built to teach the player the mechanics and enemy types without a tutorial), it stops the flow when you have to rerun from the beginning back to the boss and you need to idly wait to proceed without losing health. No other chamber requires that at that point, and it's only like two seconds, but if you die constantly like I did, it'd be nicer to just keep the flow going.
• transition from the chamber with two arrows and all the blocks that need to be moved out of the way, back to the previous chamber puts you immediately next to a snake enemy, making avoiding getting hit extremely difficult, I think this is a slight oversight.
• consider making the invulnerability window after getting damaged slightly longer, as it's easy to get thrown off the flow and damaged a few times in a row as it is now.

But these are just some suggestion, it was a cool experience reminding me of old DOS games, and congrats on the work!

Looks like an amiga game

Neat! I'll be honest, I'm probably not the target audience for this game (I thought about it and I've never played a game like the traditional top-down Zelda titles for more than an hour or two), so I didn't expect to actually finish it, but I ended up beating it and had fun along the way! I died a fair bit (maybe a half dozen times?) on account of being a scrub, but there wasn't anything that felt unfair.

I'll echo what's already been said about making the platforming a bit more forgiving and adding some kind of indication as to the boss' health--the latter wouldn't necessarily half to be a health bar, but maybe some visual indication when certain thresholds are passed. Here are my additional suggestions:

• If it's feasible and fits the style you're going for, consider making the enemy pathfinding a bit more intelligent (from what I can tell they just head straight for the player ignoring any obstacles). There were a lot of places where I ended up just cheesing the enemies through a wall which didn't feel like the intended strategy. There was one room towards the end where you mitigated this by adding the little wall-shooter guys on the opposite end of the room to make this strategy more difficult than just engaging normally, so that's another way of dealing with it!
• Adding color-coded doors to the map. Seeing an unexplored path is certainly a clue that there's a locked door there, but it doesn't necessarily tell you whether the path is blocked by a standard key door, a boss key door, or a non-keyed door.
• Making the fire for puzzles non damaging, or arranging them/giving them smaller hitboxes such that it's less easy to bump into them. I think I died at least once from clumsily handling the puzzles (probably on the one where there's a complete square fire fence around the four arrow blocks)...maybe that's just on me needed to working on my jumping skills, but it did feel frustrating to die on a puzzle like that. Again, this might also be something intrinsic to the style that I'm not used to. I know the fire in Binding of Isaac damages you when you walk over it, but you're also never required to do that so
  
• Along the same lines, it'd be nice if there were a way to manipulate individual arrow blocks besides swinging your sword, or if their hitboxes were smaller to make accidentally triggers less likely. I never quite got the hang of how far I needed to be to only hit one block, so probably half the time manipulating the blocks was spent going, "[slash] Aw man, I accidentally hit two blocks... [slash x7]. Okay, this time I'll get it for sure! [slash] ...dammit."

Keep up the good work! I'm genuinely in awe of anyone who can follow through on any large project like this because I have trouble doing anything that requires more planning and perseverance than writing a few hundred lines of a Python script (and even then, I definitely don't do enough planning...). I'll have to hone my skills on some top-down adventure games so I'll be ready for the full release and not die quite so often and so pitifully.