Ah right, so the way the Hag is programmed she tries to cut you off at the stairs rather than going straight after you. I might work in a fix where you can't just leave her pacing like that if you camp on the stairs.
Im not sure what youre talking about with "Usex64", where did you see that?
Haha nice catch, that is a graphical error. I intended to have the child take a sigh of relief if she managed to escape the hag but somewhere along the way didn't I see it through, you're seeing remnants of that attempt. I've fixed this in the newer build of the game.
Ah, there is a lot left up to assumption, partially because it's a short project, and also partially to give myself a lot of elbow room if I wanted to make a sequel. Thanks a bunch for talking about it, gives me a lot to think about!
oh i've never really messed with the app, that's a weird error. i've looked into it and seems like it's an issue with the app itself? apparently multiple games give this error message. i'm honestly not sure as to how to fix it, sorry!
interesting suggestions for sure! i do want to make a sequel after finishing my current game project, and i will consider these when planning for it. It's very unlikely that I will expand upon this build as I programmed the foundation really quickly with no consideration for scalability, so it would need to be a sequel which expands on the mechanics and fixes some of the gameplay issues.
thank you! rebinding is definitely something i'm going to have in all future games i make since it's pretty inconvenient to be stuck with whatever control scheme i make up. i want to spend my time making new games though, so unfortunately Gnarled Hag is going to stay in it's current state, warts and all.
thank you! the game i think is definitely too short and buggy to ask money for, but if i do end up making a sequel (BIG IF) i could look into putting it on steam.
Thank you! Yes all of those criticisms are very valid, and if I ever were to make a sequel I would take all of those things into a account (especially the trial and error with a lot patience-testing and harsh punishment for failure)
The extreme punishment of just restarting the whole game when you die was to add tension for failing, but the rest of the game would need to be a LOT more tightly designed to back such a ridiculous punishment up, and I don't really think it is, there are plenty of instances where the player fails and it's not really their fault.
The end chase sequence I think is the worst in this regard, because the player loses an insane amount of progress if they die, and there's really no guidance on what you're supposed to do, so 9/10 it's gonna be trial and error. Just a fumble on my part that I'll need to learn from going forward.
Great gameplay video! Thanks a bunch for playing and the feedback!
I won't lie, I honestly think the end part is just poorly put designed, after having the player get so far I should've more clearly conveyed what they were supposed to do.
I gave the player about 2 seconds of time to react, and in a game where the whole time you've been taught to run, almost every player of course will naturally try and run and get confused when they can't move, then die to no fault of their own. It's a lesson I will take in the future to not be so VAGUE, or at the very least more forgiving with checkpoints or something.
Thank you very much! The software I used to make it is Game Maker Studio 2, it's very friendly to people like me who have ZERO experience in programming.
I made all the art in Aseprite, which is probably the best software for making pixel art out there right now (imo)
