Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit) (+1)

I initially ran past the pillar, got told to go back, did so, got the quest, but the invisible wall preventing progress never went away. Tried saving and reloading, tried talking to the pillar again, tried dying and returning to camp, didnt work.

Wonderful, so you got the quest but the invisible wall was still there. That gives me some way to operate here ^^, thank you

I know it's a lot to ask but have you tried replaying the game and checking if the issue persists? (If you choose an option skipping the whole tutorial you have only approx 5-7 minutes to get to that point on a New Game start).

Also, I know it is a weird question, but what is your OS language? In the past I had issues with users using certain languages and wanted to double-check if it might not be a similar issue again (basically naming of methods in the game's backend)

Thanks for the answer again and looking forward to your reply! ^^

Haven't tried replaying, I'll give that a go. By language do you mean speaking language? In which case it's English. I am on android.

Okay, it worked when I went to the pylon first. I didn't try running past again, that might be what causes it?

I've got another theory, your phone might have loaded the backend data not quickly enough (I noticed that I did a... let's say a temporary solution of just waiting a certain amount of seconds instead of properly checking if all the data in the backend/data persistence system is loaded and I've never changed it). The check for the invisible wall depends on the Quest Manager data, if it doesn't have it then the invisible wall stays where it is cause it doesn't have any quest list to check if you are on a correct stage of it.

(+1)

it seems that skipping the dialog might be what's causing it, I did interact with it at first but I was skipping most of what was said. Slowing it down might have been what solved it for me

Hmmm You might be right as well, as I see that the dialogue state variable was, in this case, set up right before the dialogue and there could have been edge cases where it was omitted by the dialogue system during skips (it never happened on the PC release tho).

Alongside the other fix I will put it at a second position. Thanks for the comment and theory!