Loved that accidental edit, I fixed my post with its original contents. As for you being appointed moderator, Well you are one of the projects authors right seems fitting to me!

That being said shops can be done in some kinda open floor layout if we do not want counters and such. That's something we can tinker with as time goes on.

As for items that would work and would give some re exploration reasons to dungeons other then grinding. With that part of the challenge is being able to lose that gear and having to go back and get it, That could get rather boring/worse then grinding though so will have to think of how that can be balanced I guess.

Tilesets. Yeah I am not much of an artist my self. I think my main problem with it is that its not balanced white vs negative space. And it feels rather bland/uninteresting consequently.  The older set that me and iambian started with, while blockish, has a decent balance to me and is appealing to my eyes. SO its just finding a good balance With that yeah someone with expertise with spriting would be nice.

The only issue I have with that tile set is it looks kinda bland/forced  with the dithering, But I think I will like it regardless! That being said I did like how the previous tilemap felt like it had more depth, But that is subject to tweaking I suppose.

As for the screenie iambian posted he just made it jump to the new coordinates. The system supports making it gracfully pan by the half tile. He just did not code it in. >.> quick screenie much

As for animated tiles. I like them but if we dont have them thats fine. But I have always felt they gave the RPG more life visually, And is something i definetily want to feel when I play this.

Ok thats the end of my nitpicking. Back to work on a font editor.

Well currently we have been going by the info in this thread. Which is really just a paraphrase of your "rewrite" of Escheron. Its a little simpler with the same main story AFAIK. You would know better obviously . That being said that seems reasonable enough to me. I as of now have no issues with it. That being said I have been directing iambian in a slightly different direction this time then battle engine first. We are trying to get the main engine,Story,Events,ect done first then worry about the battle system. This way everything fits together nicely instead of us coding around making spaghetti.

This is outdated, Please see the main discussion thread for appropriate into for this project. This information is for an old iteration of the project.

Below is a rough outline of everything from the previous Escheron thread that is currently in planning for the newer "simpler" Escheron: BW. Most of this is paraphrased from Zera so bear with it its a little rough around the edged but the content is there.

I've been messing around with the idea of a monochrome game some more lately. I came up with something a little more "elegant" in its use of memory, and something that will hopefully respect the calculator's memory restraints a lot better.

I toned down the in-game lists and inventories so that there's 16 items per table - i.e. 16 different enemies that can be encountered, 16 different pieces of equipment scattered throughout the world, 16 different character and enemy skills, etc. That should fit neatly into memory without having to cross-reference multiple pages.

Echeron's original design has too much superfluous content, and much of it feels like an afterthought. For instance, you would often have your choice of 4 or 5 different kinds of equipment upgrades at various points in the story, but the stats and abilities of these items really aren't so different from one another. If Sword A and Sword B are almost identical, why give the player a choice in the first place?

Menus have also been grossly simplified. In fact, it's pretty much a clone of Dragon Warrior's menu layout. No more portraits, no more weird scrolling, etc. The whole menu system in grayscale Escheron is a beast that probably eats up most of the program, and all the little bells and whistles that make it that way aren't so spectacular that they would even make it worth the hassle.

The party system is very different. Battles are one-on-one encounters, and Maya is the only character you control. You can take a single guest character with you, but they don't have character stats / equipment of their own. What they do is tag along and occasionally (determined by pure chance) jump in and attack an enemy, or cast a spell. Enemies can't target guest characters, but if Maya is K.O.'d at any point, it's Game Over.

Guest character attack power is actually determined by Maya's own attack power plus a static bonus. This gives the illusion of guest characters being able to "level up" right alongside Maya. Maya's own stats are increased in a fashion similar to the original system I had planned - she'll gain random stat boosts after battles, as determined by probability checks. There's a default probability for any given stat increasing on its own, but wearing certain types of equipment will increase specific stats more often.

Nothing in the actual story had to be toned down. All the changes are mostly cosmetic and technical. Maya still encounters the same characters, has the same allies throughout the story, and the same major events take place. In fact, my script writing is a little more polished this time around. I shifted everything to Early Modern English grammar (i.e. Dragon Warrior) and started elaborating on each scene in much greater detail.


From left to right, descending order:

Chimera / Rhyos, Gremlin, Wasp, Vampire Bat, Lost Soul / Shrieker, (!)Labolas, (!)Shadow Lord, Zombie / Revenant, Skulldier, (!)Sea Serpent, Piranha, Bomb / Destroyer


Current World Map:7


Rosencratz


Dradmoore Swamp:
The first dungeon in the game, the cave in Dredmoor Swamp. The black tiles with white speckles are sections of swamp. Each time Maya steps in them, she's poisoned. In order to make it to the cave, Maya will have to trek through the swamp leading to the cave. Poison damage will kill Maya outside of battle, so she won't actually have enough HP to walk through the cave while under the poison's effects.

Note that there are no curative items in the game. What the player will have to do is spend a little time grinding for 400 gold and pay the magic guild in Ragnoth to scribe the "Whispering Wind" spell in Maya's spellbook. This will allow her to neutralize her poison status as soon as she makes her way into the cave.

Any chests marked "Gold" will always contain a random amount of GP between 24..48, and will respawn when Maya leaves the dungeon and returns. This is always the case, even for chests found much later in the game. If you don't mind trudging through poisonous swamps and random battles, this is a good way to grind for gold early on.


Indeed. I've made a mental note to place gold-bearing chests into the deeper sections of each dungeon so the player can't make a quick trip in, grab some loot, then exit and repeat. Some of the early dungeons are bound to be on the shorter side, but there will usually be obstacles such as random encounters and swamp tiles to make the trip much more tedious. Even so, gold will need to be somewhat plentiful. If you're K.O.'d at any point, you lose half the gold in your possession.

Here are a few "Features" that are currently being planned:

 - "Trap rooms." Entering the door places you in the center of the room, as opposed to near the entrance / exit where you should be. Every tile in this room is a forced encounter with challenging enemies. It should be noted that you do have an emergency exit spell at your disposal, but it returns you all the way back to the last monolith you used.
 
 - Looping warps. You'll often find yourself walking down endless hallways, which are actually just warp tiles that seamlessly and repeatedly transport you a few steps back.
 
 - Invisible paths, especially into complete darkness, complete with looping warps.
 
 - Warps to inescapable rooms. Just make sure you have your emergency exit spell before entering a dungeon. If not, there will be swamp tiles so you can kill yourself and be resurrected at the last monolith you used.

 - Invisible warps to trap rooms and inescapable rooms; warps that take you back to the entrance of a dungeon, and look deceptively like the exit you spent 30 minutes trying to reach; trick rooms that look like earlier rooms, giving the impression that you just backtracked or went in a circle.
 
 - Enemies are fond of instant K.O. spells. There are a couple of ways to resist instant K.O. - either by grinding your HP past a certain threshold, or finding a rare item. Both methods will likely occur very late into the game. There's one method for Maya to be resurrected during battle, but it can be put into effect only once per battle.
 
 - The best equipment is outrageously expensive. You'll need to have nearly the maximum allowable gold you can carry before you can purchase anything good. On the other hand, most of these items can be found in dungeons, albeit very well hidden.
 
 
Save System:
The save system is a bit complicated, and if not executed carefully, can cause some serious mental stress. I think I'll need a few paragraphs to explain this detail alone.

To save your game, you have to interact with one of the various monoliths found through the world, usually in towns and dungeons. What happens is Maya makes a prayer to the Fates, the three goddesses who govern time and the predestination of all things. The Fates make a record of Maya's exploits up until that point, and should Maya be killed, the Fates will transport Maya's body and spirit to an earlier point in time. In simpler terms, it's just like any typical save game scenario - you pick up where you last saved.

Now, the Fates are very particular about how the player uses this system. The Fates will instruct you to return to them and make an additional save before ending the game and shutting down your calculator. Failure to perform this procedure will screw with the very fabric of time. Suffice it to say, the Fates don't take kindly to this.

What the game does is secretly set a flag in your SRAM file the moment you load a save. This flag remains intact until you use a monolith to save the game and shut down the program from within the game itself. If you do this, then the flag is removed. If you shut down the program without going through this procedure, then the flag remains intact.

The flag lets the Fates know whether or not you followed their instructions and shut down the game within the game, or if you just abruptly turned off your calculator. If you abruptly quit, then prepare for a 10-minute lecture on why you should respect the Fates and take their powers more seriously. If you <i>habitually</i> quit the game without first saving, then the Fates will start to inflict actual punishments on you, such as removing all your items, stranding you in an inescapable room and disabling your escape spell, or wiping your SRAM data entirely.

The purpose of this is to prevent save scumming. If you find yourself in a difficult situation and death seems inevitable, you basically have no choice but to surrender to death and deal with the penalties that follow. If you simply shut down the game and try to reload from your last save file, the game <i>will</i> detect your efforts to circumvent the penalties of dying.

In the event of battery failures or other unforeseeable circumstances, the Fates will give the player a few grace warnings, but after the player screws with them several times, the Fates will no longer accept convenient "battery failures" as an excuse.

That said, be sure to follow their instructions exactly.


No worries about experience grinding, though. The growth system is similar to FF2j for the Famicom. Instead of gaining experience points, there's something like a 16/256 probability that any of Maya's ability scores will increase by 1 point after a battle. The probability for certain score increases goes up when Maya is equipped with certain items. e.g. Outfitting her with clothing or robes will help her boost her Agility score more quickly, while giving her much heavier armor will boost her HP instead.

To keep the player from getting perpetual increases from weak enemies like Gremlins and Wasps, there's an enemy ranking system in place. Each enemy has a rank from 1 to 8. What this does is determine exactly how many increases Maya can receive from fighting particular enemies. For instance, once all of Maya's ability scores reach a value of 32 or higher, she won't gain any more increases when fighting enemies below rank 3. Gremlins and Wasps are both rank 2. By the end of the game, the only way Maya will be able to gain any additional score increases is by fighting very tough rank 7 and 8 enemies, such as Chimeras.

The best comparison I can think of is the NES version of Dragon Warrior II + Final Fantasy II (the original Famicom game previously not released outside Japan) + some rougelike-lite elements.

FF4 Hard Type should be easier than Escheron. You can always grind your way to victory at any point in that game, whereas Escheron has a cut off point determined by so-called "safe zones."

You're not safe to leave the current area you're in until you've reached the highest stats the game will allow you to attain by fighting the enemies encountered in that area. At that point, you can move into a new area with tougher enemies, and these new enemies will allow you to resume grinding your stats to higher values. All of this is controlled by the rank system mentioned earlier.

If you try to venture into a different zone too early, not only will you not even be able to damage any of the enemies there, but they'll probably kill you with a single attack.

There are a few other things worth mentioning that really kick the difficulty up a notch:

 - A lot of enemies at different stages in the game have access to instant K.O. spells. Resistance to this effect is determined the target's maximum HP. The weaker K.O. spell is no longer effect against a target when it's maximum HP is above 40, and the strongest K.O. spell won't affect targets with over 128 HP.
 
 The early to mid-game sequences will be pretty daunting for this reason. Maya should have over 128 HP by the time she reaches the final dungeon, but due to cut offs and safe zones, she definitely won't be able to attain that much HP before then. Just hope you don't get ambushed by any spell-casters half-way into a long dungeon.

 - Armor has a weight factor that penalizes reaction speed. Reaction speed determines battle turn order, preemptive strike rate and probability of fleeing an encounter. If you aren't careful, you will not only ensure that Maya is consistently ambushed by every enemy she encounters, but that she also can't flee from them.

 - If Maya tries to attack fire-based enemies directly, she'll be burned. This is a pretty straightforward counterattack mechanism. To make things tricky, there are a few enemies that are not only fire-based, but have ridiculously high defense power.
 
 This counterattack formula is based <i>only</i> on Maya's raw attack power, not a percentage of how much damage she actually dealt to the enemy after its defense power had been factored into the equation. In other words, Maya may be able to inflict maybe 1 or 2 points of damage with an attack, but she'll suffer an upward of 120+ damage as a result of coming in contact with the enemy's flames. Thankfully, critical hits don't return additional damage against Maya.
 
 Magic spells ignore defense power since there's no special type of defense against magic, so these enemies aren't extremely challenging as long as you have plenty of MP to get you through hoards of random encounters with them. Alternatively, you can just run. You'll be doing a lot of that anyway.

 - The attack formula used by undead enemies is different from the standard attack formula used by both Maya and most typical enemies. Undead attacks shave off a direct percentage of Maya's maximum HP, ignore her defense power, and heal the enemy in return. This means undead enemies encountered in the very first areas of the game are still just as deadly even after you've been to the final dungeon and back.
 
 On the other hand, undead enemies have frail bodies, little HP and the lowest defense power in the game. As long as Maya is fast enough to get the first attack, she doesn't have to worry. Undead enemies are mostly a problem early on when they appear in large groups, because Maya won't have access to a multi-target spell until the middle of the game. But...
 
 - There are (rare) enemies that are both fire-based and undead. The counterattack damage will render your HP critical, then the enemy's actual attack will probably finish you off. If that doesn't do the trick, then their instant K.O. spells will.

Whooops lol fixed and added to the OP.

Meh not feeling like writing a linked list handler in Z80 So naaaaa. Lets have some people use it first

Anytime! Hopefully you will stick around!

Just something to consider. The Millis() function on the arduino platform resets after around 50 days or so. Make sure you have a case for that so the clock doesn't randomly barf