Goodbye Eternity
Game Description:
What if you had a new chance in life? What if you could make it better than all those years of misery and harassment?
What if you could get revenge on all the people who wronged you and get what you always desired….
What will you do, with this chance as you wake up in a youthful body, thirty years in the past?
The choice is yours.
- Extract and run.
- Incest Patch PC Installation: Unzip it into the "game" folder.
## Added
* Yasuka friendship path
* Saito chooses to focus on his father's debt, leaving romancing options for Yasuka off the table
* Includes one good path, and one bad ending
* 2 sprites in backgrounds
* 1 new costume for Yasuka
* 1 new skin for Yasuka (only available with the bad ending)
* New saves export/import feature
* You can now export and import all saves files, player preferences, and unlocked content
* Does not work on the web version, or very old Android (9 and below)
* Will offer to save or import a .zip file containing all of the data
* Does not require extra permissions on Android, as it uses the Storage Access Framework## Modified
* Engine updated to Godot 4.6.1
* Hopefully this will solve a long-standing issue with PowerVR-equipped phones, where the game would crash at the second start of the application, due to crappy PowerVR drivers crashing on loading the shaders cache
* Game goes back to using the english version upon starting a brand new version
* This is made so that people will think of checking translations, to make sure they get an up-to-date one## Bugfix
* Game would not behave correctly after downloading a translation
* Background sprites would not follow the correct logic sometimes. There must still be issues, so please tell us if you notice them
* Sprites logic has been rewritten, no more weird behavior when changing sprites attributes
* Game would display wrong glyphs for Chinese/Japanese languages, making a mix of the two fonts
- Dual Core Pentium or equivalent Processor.
- Intel HD 2000 or equivalent Graphics.
- 730.20 MB of free disk space (Recommended to have twice as much free disk space than this).
Goodbye Eternity - Ongoing - v.0.13.6 Links And Mirrors
About The Game: Goodbye Eternity is a porn game made on Others game engine. This game is rated M and meant for adults with explicit contents and strong language. It is advised to read the tags to get an idea about the game. The current available version is v.Goodbye Eternity. THe contents of the game is Uncensored. Goodbye Eternity is developed and distributed by RNGeusEX, Please support RNGeusEX if want the development of Goodbye Eternity game going or want to see more new games from them in future. The download links are crawled and gathered from various public sites. We do not host/modify or alter the contents. The uploader is responsible for the DMCA.
Goodbye Eternity's latest build v.0.13.6 is available in Windows, MacOS, Linux, Android platforms and currently Ongoing. We last updated this game in May 12, 2026.
Goodbye Eternity's latest build v.0.13.6 is available in Windows, MacOS, Linux, Android platforms and currently Ongoing. We last updated this game in May 12, 2026.
Walkthrough and Guide
Walkthrough v0.3: FILEKNOT
Cheats Codes:
To unlock the codes it's necessary to collect the money hidden on all the backgrounds and to finish the game once.
Cheat Table: FILEKNOT
Old Cheat Table: FILEKNOT
How do I get a copy of Cheat Engine:
There are several ways to download the tool:
NB: Cheat Engine is available on Windows and MacOS only.
NB: Make sure you have the LATEST or at least a penultimate version of CE when using others' cheat tables to avoid incompatibility issues
How does Cheat Engine work:
It's basically a debugging tool on steroids. There's a lot to unpack on how it works, but my scripts rely on AOB signatures (be they hardcoded ASM cheats, pointers with offsets, etc) and LUA scripting. The challenge is to create consistent and resilient cheats working between versions, but there's nothing permanent with compilers and optimizations.
AOB signatures work like this: a byte signature is scanned to find the first match in the .text (code) section, then CE gracefully injects a detour jump to the allocated cheat script (or in a code cave) that tweaks the game behavior and then returns to the next instruction after the injection. Sometimes AOB-based cheat scripts modify a function's behavior in-place.
Lua scripts that are running in the CE's lua engine are basically meta-scripts to extend CE's functionality with a neat API.
Where do I put a cheat table / .CT file:
Wherever you deem suitable, usually tables are standalone .CT files and making dependencies for them isn't a good practice. When you run a cheat table, it's loaded into and interpreted by Cheat Engine.
How to use Cheat Engine:
First of all, make sure your Cheat Engine instance is running with administrator rights to make sure it is able to read, write to memory properly. To do that, you can grant administrator rights by clicking RMB on Cheat Engine shortcut (to open its context menu), then go to Properties -> Compatibility (tab) and tick 'Run this program as an administrator'. Likewise, you can go to CE settings (when in the CE GUI, Edit->Settings) you can also find 'Always attempt to launch as admin' option. Or if you need it once, just run CE as an administrator (RMB on the CE shortcut, 'Run as an administrator'
For cases when tables DON'T have an attach script in them:
When Cheat Engine is opened and/if a cheat table for a specific game is loaded into it, the first thing that's needed is to attach to the specific game executable.
Attach button is highlighted:
After pressing this button, you will see active processes with their PIDs exposed by Windows. If you struggle to find yours, check other tabs, there are 3 of them: Application, Processes, Windows.
For cases when tables DO have an attach script in them:
You'll see a script like *this*, just activate the checkbox. Does it fail to attach? Please read 'Why does the attach script fails when I activate it?' below
Attach script:
Once you are attached, activate other scripts that you need and have fun. Usually scripts are quite simple to use, but if there are instructions, just follow them to make it work. Sometimes certain actions are required for scripts to work properly, .e.g pressing a button to catch a pointer, loading into the game/level world to ensure a character actor is constructed, etc.
Sometimes scripts will fail to be executed. Usually the error will be written in the context menu of a script that's failed (just click RMB on the failed script, the first row will be the error message). Some scripts may print errors/tracebacks into the CE Lua Engine output window: either way, when you report an error, provide the reason WHY it fails.
Error Example: AOB not found:
If a script activates, but the intended behavior is not achieved (you'd be lucky if it doesn't crash though), most probably there was a game update that touched offsets (provided the table was based on any, which is probably the case) - a new field added, hence game compiled differently, a different game engine version used, or whatever that caused the shift. That means the table has to be updated - it's obvious if the game was updated recently, but the table was posted long before.
ALSO: go to 'OK, I'm attached to the game correctly, but next scripts fail to run OR crash the game. What's wrong?'
Cheats Codes:
To unlock the codes it's necessary to collect the money hidden on all the backgrounds and to finish the game once.
more = +5000¥
MacumbaEverywhere = Try this, trust meCheat Table: FILEKNOT
Old Cheat Table: FILEKNOT
How do I get a copy of Cheat Engine:
There are several ways to download the tool:
- Official Cheat Engine website - a free, compiled executable. While installing, make sure you decline all adware
- Dark Byte's Patreon - $2.5/mo membership to get the latest releases and hotfixes already compiled
- Cheat Engine Github - if you want to compile it or CE github releases
NB: Cheat Engine is available on Windows and MacOS only.
NB: Make sure you have the LATEST or at least a penultimate version of CE when using others' cheat tables to avoid incompatibility issues
How does Cheat Engine work:
It's basically a debugging tool on steroids. There's a lot to unpack on how it works, but my scripts rely on AOB signatures (be they hardcoded ASM cheats, pointers with offsets, etc) and LUA scripting. The challenge is to create consistent and resilient cheats working between versions, but there's nothing permanent with compilers and optimizations.
AOB signatures work like this: a byte signature is scanned to find the first match in the .text (code) section, then CE gracefully injects a detour jump to the allocated cheat script (or in a code cave) that tweaks the game behavior and then returns to the next instruction after the injection. Sometimes AOB-based cheat scripts modify a function's behavior in-place.
Lua scripts that are running in the CE's lua engine are basically meta-scripts to extend CE's functionality with a neat API.
Where do I put a cheat table / .CT file:
Wherever you deem suitable, usually tables are standalone .CT files and making dependencies for them isn't a good practice. When you run a cheat table, it's loaded into and interpreted by Cheat Engine.
How to use Cheat Engine:
First of all, make sure your Cheat Engine instance is running with administrator rights to make sure it is able to read, write to memory properly. To do that, you can grant administrator rights by clicking RMB on Cheat Engine shortcut (to open its context menu), then go to Properties -> Compatibility (tab) and tick 'Run this program as an administrator'. Likewise, you can go to CE settings (when in the CE GUI, Edit->Settings) you can also find 'Always attempt to launch as admin' option. Or if you need it once, just run CE as an administrator (RMB on the CE shortcut, 'Run as an administrator'
For cases when tables DON'T have an attach script in them:
When Cheat Engine is opened and/if a cheat table for a specific game is loaded into it, the first thing that's needed is to attach to the specific game executable.
Attach button is highlighted:
After pressing this button, you will see active processes with their PIDs exposed by Windows. If you struggle to find yours, check other tabs, there are 3 of them: Application, Processes, Windows.
For cases when tables DO have an attach script in them:
You'll see a script like *this*, just activate the checkbox. Does it fail to attach? Please read 'Why does the attach script fails when I activate it?' below
Attach script:
Once you are attached, activate other scripts that you need and have fun. Usually scripts are quite simple to use, but if there are instructions, just follow them to make it work. Sometimes certain actions are required for scripts to work properly, .e.g pressing a button to catch a pointer, loading into the game/level world to ensure a character actor is constructed, etc.
Sometimes scripts will fail to be executed. Usually the error will be written in the context menu of a script that's failed (just click RMB on the failed script, the first row will be the error message). Some scripts may print errors/tracebacks into the CE Lua Engine output window: either way, when you report an error, provide the reason WHY it fails.
Error Example: AOB not found:
If a script activates, but the intended behavior is not achieved (you'd be lucky if it doesn't crash though), most probably there was a game update that touched offsets (provided the table was based on any, which is probably the case) - a new field added, hence game compiled differently, a different game engine version used, or whatever that caused the shift. That means the table has to be updated - it's obvious if the game was updated recently, but the table was posted long before.
ALSO: go to 'OK, I'm attached to the game correctly, but next scripts fail to run OR crash the game. What's wrong?'
