Skip to main content

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

I'm having problems with ending the level. Whenever i give the final product to the receiver they take it tell me what they think and then just nothing happens

(+1)

Which level is this happening on?

All of them. It doesn't work on the tutorial nor the first level

I've tried looking into this and I can't seem to find an issue. Could you press F12 after this bug happens and post what it says in the "Console" section into a pastebin?

It just pulls up my windows thing in the bottom left corner, no console or anything i can copy comes up. Any other way to find that "console" or whatever it is?

Yep, so once you press f12 and it brings up that window, there should be some tabs on the top bar of that window - "Elements", "Sources", something like that. One of them should say Console. Can you try to replicate the error, then open up the console window and paste what's in it?

I don't see any elements or anything near that. It just comes up with the windows task bar thing. Just like if i pressed the windows button so i get down to where i can shut down the computer, settings and search.

If you follow this tutorial it should show you how to get the developer console open (starting at 0:40):

Thanks for helping out! It's really appreciated. I'll try and fix the bug and get it updated as soon as we find out what's going on.

hiya! not op, but here's mine: https://pastebin.com/axhTB83q - there's no error message/popup, it's just that there is no indication of how to progress with the game after presenting the item (e.g. sand) to the customer! thanks for troubleshooting

Awesome, thanks for posting this. I think I know what the issue is - I'm assuming you didn't play Artificer before the recent update (or you had new save data)? I think I messed up save data for new players.

I'll fix this asap and get the fix out by tomorrow if possible.

I have the same thing

Heyo, just fixed the issue. Sorry about that! 

alright, I should've fixed the bug now. Lemme know if the issue persists :)