Ohhhhhh I might have misunderstood you before.
So you mean pathfinding will only use nodes that the player has climbed before? Because I have a system where players need to inspect objects to create parkour opportunities (unless they use a very explicitly-clear parkour command to test it).
So what you mean is that for pathfinding, you need to not only know the route, but you have to walk through it manually first? That would make a lot more sense.
I was also considering borrowing a note from the GOTO command and making it so auto-parkour is a unique command that does things in stages, which the player must accept with the CONTINUE command. Part of this would also tell the player what the next step in the route would be, in case the player would rather do something else.
Yeah. First time through you get no pathfinding or only pathfinding up to but not across the “problem” area (if the path goes through a minefield, pathfinding will take you to the edge of the minefield but not through it).
Then if you successfully traverse the “problem” area, the path you used is now available for automatic pathfinding subsequently. That could be by explicitly storing each step (which might be needed if backtracking is part of the puzzle) or just flagging the individual locations/platforms/objects/whatever in the problem area to indicate that they’re available for use in pathfinding.
Ohhhhhhhh, okay! Yeah! I might also do a thing where if routes change, then it resets their availability for pathfinding as well.
Will be making notes for version 2.0!
Okay, in the interests of SpringThing time budgeting, I’ve simplified parkour pathfinding, and moved a few other things over to the “2.0 wish list”. This is a problem for future-me!
Parkour 1.0 is now 83% complete!!
I am so close to being done.
I’m maybe 98% done. I have to get some sleep. There’s maybe 2 hours of coding left. I cannot believe I didn’t get the whole thing done tonight.
But if I don’t sleep, then certain people will be grumpy with me.
PARKOUR (VERSION 1.0) IS COMPLETE
AT LONG LAST. NOW THE GET ON WITH THE REST OF THE GAME.
If anyone can help me out, by the way, I posted a question about screen reader accessibility, for this extension’s route listing menu. I’d appreciate knowing how screen readers might work with this, as I’m using @blindHunter’s For Everyone extension.
Also, I generally try to lean as hard as I can into screen reader support, as I am passionate about game accessibility as a whole.