Home Artists Posts Import Register

Downloads

Content

Hi, Alder here in these dark and spooky times, with a new update for Fall of Eden!

This one took me a bit longer than I’d wish for, but there were some important behind the scenes coding that’s going to benefit the game in the long run. I’ll try to get the next one out more expediently, continuing with refamiliarizing myself with the characters and fleshing out placeholder content.

Without further ado, the changelog:

Version 0.5.3

  • Hotfix: Halloween event no longer steals your items.
  • Fixed numerous minor logic errors in scenes discovered by applying strict typing.
  • Fixed some race detection errors in scenes, also discovered by applying strict typing.
  • Added some debug functionality. If you are in to hacking through the console, a bunch of game variables can now be accessed through the console on the object 'game'.
  • Added a new parser methodology that should make implementing scenes quicker and less prone to errors. It uses template literals from ES6 and some helper objects to allow for a simple parser syntax.

Adding roughly 8k words of new content:

  • Gwendy has new talk scenes for various topics (chat, childhood, parents). The farm description placeholders have been removed.
  • Gwendy has a new loss scene for her challenge (eat her out).
  • Replaced some awkward placeholders for Jeanne, Roa, Twin's Penthouse (content for the twins themselves to come).

Files

Comments

Belly97

Yeah, but where/what is the console and how do I "get the GAME() object"? Once I know steps 1, 2, 3 I can probably workout 4, 5, and 6 myself.

foe

I got this slightly wrong, so I've edited the original post. (Instructions for Chrome): 1. Open dev console (F12) 2. game.player. (a list should open at this point) 3. If you want to edit a stat, like for example strength, you'd do: game.player.strength.base = 10000;

Belly97

Nope, no matter what I type or do it doesn't start autocompleting. :(

foe

Either you didn't start a game yet (it won't work from the menu screen), or it's something with your browser. I've verified this locally on Chrome build 78.