By the way will there be fog of war like in Joltima and the TI-89 Calcrogue?

Sorry for the delayed reply, I've been so insanely busy working that I've had a horribly small amount of free time  

For Chambers, I won't be implementing a fog of war. The only way that it would make sense would be for the "containers" to block one's view, which strikes me as equivalent to a treasure chest doing the same thing in a standard RL, which would be a bit odd. Other than that, since each room is entirely open (except for monsters and containers), I don't feel that a fog of war would lend itself well to this game. I originally considered doing a more full-blown roguelike with scrolling tile maps, etc., but I settled on doing one much closer to what you see here for a few reasons. The main reason is that, to be honest, I felt that it would be easier to pull off. This kind of allows me to set my sights on something realistic that I have high confidence that I'll finish. The second reason is that, considering the display, I wanted something where you could see everything that's going on at once. It is my hopes that this will place more emphasis on players thinking about their movements and item management. I know that I'm not the only one who falls into a trap of exploring too much rather than carefully planning my movements, leading to lots of YASD moments. I also felt that, considering this is my first RL engine, I wanted to keep it simple so that I wouldn't have to worry about implementing tons of stats until I get my footing a bit more. If I had larger maps for each floor, I would likely have to implement some kind of impetus for progression, such as the standard hunger system, "warmth" system in Frozen Depth, or sanity system in Infra Arcana.

Once done with Chambers, I'm not sure what my next project will be. However, at some point down the road I intend to try my hand at a more traditional roguelike, depending on how slim I can make an engine. I'll be the first to admit that I'm extremely old-fashioned and inefficient in a lot of my coding practices, so I feel like I have a lot to learn before I get to that point. When I see some of the amazing games that people put out and how small the files are, I get super envious  

So can anyone elaborate on what a rogue like game is?
***feels dumb now***

Don't feel dumb! Roguelikes are a (somewhat) obscure subgenre of RPG. The keystone of these games is the randomness. Levels are randomly generated, monsters are randomly generated and placed, as are items. A lot of times, even the items do different things on each playthrough (e.g., a blue potion this time might be a heal potion, next time it might be a fire potion, etc.). Another main thing to roguelikes is permadeath. Basically, each play is completely unique and you can't backtrack. If you have a bad playthrough this time, it's okay, because you just start fresh again. Sometimes the randomness comes together in your favor, most of the time it doesn't

Another key to roguelikes is that they are typically very strategic. You have to sometimes really stop and think about whether you should use an item, what your chances are of attacking a monster or trying to plan a route of escape, etc. They're a lot of fun, although some of the greatest ones have a really steep learning curve.

I think that some of the most popular ones of alltime are DoomRL, Nethack, and Angband. I'm partial to Nethack myself, but there are really a lot of incredibly innovative and awesome ones out there.

Also I like Rogue-like games and I wish there was one that got finished for z80 calcs. This one looks very nice so far.

Thanks! Roguelikes are definitely my favorite genre, and I've been playing a ton of Cataclysm and Brogue lately, both of which are really interesting and progressive games in their own way. I've hoped for years that someone would do a 7DRL competition for the z80 calcs. Unfortunately, that kind of seems unlikely, as anyone who creates one would have to meet multiple criteria (enjoy roguelikes, know how to code, know how to code calcs, have the time to do it, etc.).

I suppose that I should post before the discussion gets too far away (not that I mind )
I'm not doing physics-based collision detection for this, as the game is essentially a tileset. Basically, once you press a key to move in a direction, the process goes as follows:

if nothing is there, move there
if it's a door, new room (this is ostensibly the fastest and least-noticeable laggy part)
if it's a wall, do that stuff
if it's an object, see if you can pick it up, then pick it up, etc.
if it's a monster, determine attack power, attack, determine if it is dead, do things involving experience points, level-up, clear the space, etc.

then the mosters move
determine how what direction to try to move towards you
similar processes all happen here as when you move (e.g., check if an object is in that space, do attack subroutines, etc.)

Basically, all of these things happen (and some more stuff that I probably spaced on just now) between each screen refresh when you press a key. Like I said, I've tried sprinkling screen refreshes into this process, but it makes the time between when you press a key and when it will become responsive to input again extremely lagged after they start adding up.

When I get to a project that involves active movement, this will obviously be a much larger problem. For now, at least, I'm okay with it. I might get more bothered by it when the game itself is completed, but that's still a ways away. I very much want to add an into screen/menu/something as well, but the amount of space this game is taking up continues to grow and might preclude anything fancy on that end.

A screenshot of my current state.

Mostly, there's far more event text. I was hoping for more chances to show off the flare and the teleporter and their utility, but it really depends so much on the random generation whether or not you're going to get stuck in a tight spot and need them. I had added a really cool effect (or, I thought so) for the flare so that you would kind of have a spotlight around you still in the darkness, and it kind of flickered with light (used a for loop to define circle radius, used character position, drew a series of spotted circles with "flickering" areas around the edge during the getkey routine), etc. I ended up cutting it because it added to the response latency by about 1-2 seconds whenever you'd press a key. It was pretty, but, ultimately I want it to be responsive more than anything. I would be more than willing to guess there's a much better way to get a similar effect that I wanted, but, whatever.

Added an item that randomly teleports you to an open spot, along with an animation for it that any fan of TI-83 manuals will love
This will have a good chance of helping out when stuck in a really tight spot in a tough room. Like the holybomb, could randomly help you. Unlike the holybomb, could randomly make your situation worse, depending on the room. Oh, emergent gameplay...

Also, set up the inventory screen so that you can wrap top to bottom and vice versa. I was getting sick of having to scroll all of the way to the bottom instead of just hitting "Up" once.

See attached image for both of these additions.

I also remapped some keys for usability and intuitiveness. A lot of work tonight, very few visible results. My next step: back to designing monsters and tweaking a ton of stats.

As a bit of added history to my development process, for anyone who's even slightly curious:

I don't remember a lick of ASM, so I decided, hey, let's start this off in TI-BASIC. I created the general map generation engine and the player-movement engine in about an hour on a Thursday. Generating an all-wall map was fast and easy. Already, it was taking about 2-seconds per turn to detect input, do wall detection, overwrite the character, redraw the character in a new place, etc., on the graph screen (I wanted to branch out from solely ASCII). I remembered quickly that this is why I never undertook an RPG in TI-BASIC. Just to draw a nice, pretty map with sprites, it would often take between 30 and 60 seconds on my old 83. Obviously, I was going to have to try to relearn ASM in order to do this in any manner that I could be satisfied with. Or was I? 

If you are ever questioning the morals of writing a piece about your own game, run a poll on some of the sites asking if members want you to or not. I am sure we'd all agree that it is necessary, especially if you finish Chamber

Thanks

I haven't thought about that at all yet, but I think that I'd feel kind of like a jerk to feature one of my own pieces of software on the site. I tend to be rather shy