aftermathteam
patreon
Inheritance A51 FIX
🕑 Added 2021-02-20 21:34:12 +0000 UTCFix build! This (hopefully) fixes the following:
*There was an error with some old saves involving the time system in the game.
*There was an issue preventing the new content related to Vanni from appearing as intended.
*Fixed an issue with one of the apple scenes that was preventing it from appearing.
*A hand full of small fixes, spelling, grammar, etc.
Download links:
https://mega.nz/file/RChBRQbL#TbpDcGIBUBRcISDJwAt0iGBBquph74saLRFKbjZZ_XU
https://drive.google.com/file/d/1sX_lWlO8JodCUFEwpiOb7TXYJDuz9Jdg/view?usp=sharing
http://depositfiles.com/files/louior28l
Comments
Aftermath Team
You were a big help finding this problem. Thank you SO very much. We're cleaning up a few other minor issues, then we'll get a fix build up some time in the next few hours.
Shane Stevens
After a shit ton more testing over the last hour or so I can confirm it starts to happen after loading a save.
Aftermath Team
The gate detail might be very useful in running it down. I'll pass this to the coder as well. Thank you.
Shane Stevens
It might just be a guess and I need to test it more, but it seems to start AFTER I have loaded a save.
Shane Stevens
No sorry for the confusion: in Chrome it encountered the same problem except almost immediately upon starting a new game and leaving the master bedroom and trying to explore any other room, once I switched to Edge it worked for a little while without the error until I spent about a day in game, then attempting to leave the main hall started to trigger the error again and I'd get stuck in any room I entered, any attempt to leave would proc the error. I've started a couple new games thus far to see if I can nail down exactly when and where the game starts having this issue and exploring around I have noticed going outside to the Gate never fails to proc the issue, I haven't notice anywhere else that consistently causes it except for the fact that it always inevitably happens.
Aftermath Team
It worked in Chrome and not Edge?
Shane Stevens
No problem, it was weird cause it was working just fine once I switched from Chrome to Edge then this just started popping up literally EVERYWHERE.
Aftermath Team
Thank you. Just turned this over to our coders. Hoping to get a fix for this soon. Thank you for reporting.
Shane Stevens
Keep getting this error "Error: <>: cannot publish clock update: npc is not defined <>" I've tried switching to a different browser as well as redownloading and unzipping.
