Walkthroughs in the WebPlayer App(?)

[KVonGit]

This could definitely be improved, but it seems to work.

// v1.02

var allWalkthroughs = [];

var stepCounter = 0;
var wtCounter;
var wtInterval;

function runWalkthrough(wt, delay=500){
  if (wtInterval){
    addTextAndScroll('Walkthrough already running!<br/>');
    return;
  }
  var thisWalkthrough;
  var found = false;
  allWalkthroughs.forEach(w=>{
    if (w.name == wt || w == wt){
      thisWalkthrough = w;
    }
  });
  if (!thisWalkthrough){
    addTextAndScroll('Walkthrough does not exist!<br/>');
    return;
  }
  runWalkthroughSteps(thisWalkthrough.steps, delay);
}

function runWalkthroughSteps(steps, delay=500){
  if (delay < 500){
    delay = 500;
  }
  stepCounter = 0;
  wtCounter = steps.length;
  
  wtInterval = setInterval(()=>{
    if (stepCounter >= wtCounter){
      clearInterval(wtInterval);
      wtInterval = null;
      console.warn('Walkthrough overstep.');
      return;
    }
    canSendCommand=true;
    var step = steps[stepCounter];
    if (step.startsWith('event:')){
      var eventData = step.substring(6).split(';')
      var eventName = eventData[0];
      var param = eventData[1];
      addTextAndScroll('<br/>>' + step + '<br/>');
      ASLEvent(eventName, param);
    }
    else if (step.startsWith('assert:')){
      addTextAndScroll('<br/>>' + step + '<br/>');
      addTextAndScroll('Cannot assert in WebPlayer app at this time.<br/>');
    }
    else {
      sendCommand(step);
    }
    stepCounter++;
    if (stepCounter >= wtCounter){
      clearInterval(wtInterval);
      wtInterval = null;
      console.log('Walkthrough complete.');
      return;
    }
  }, delay);
}

---

// Let's create a walkthrough object, just like Quest's
var myWalkthrough = {
  name: "testing",
  steps: [
    "i",
    "x me",
    "xyzzy"
  ]
};
allWalkthroughs.push(myWalkthrough);

allWalkthroughs.push({name:"test2",steps:["jump","help"]});

---

I can do it like this: runWalkthrough('testing')

or this: runWalkthroughSteps(['l','i','x me','help'])

---

I was considering ignoring all keypresses and clicks during the walkthrough, but the desktop player doesn't do that. So, meh.

I do need to add:

• ability to nest a walkthrough within another walkthrough, just like the desktop player
• all the assert:, event:, etc. from WalkthroughRunner.vb (the events will be a piece of cake, but I haven't looked at how assert actually works yet)

---

Also, I think (maybe) Quest's source code could be modified to include walkthrough elements like it does object, function, command, etc., to make them accessible from within the game. This sounds like more work than it's worth, though. An author could simply create a normal object to use as a walkthrough object before publishing.

---

UPDATE

I added the optional delay parameter, but anything under 500 won't work; so, it will default to 500, and it will be set to 500 if anyone tries to make it run faster than that.

UPDATE 2
Also added event: (which is functional) and a message for assert: saying the web player can't do that (yet).

---

I've got a feeling I'm overlooking something important. (I always do, haha!)

I've got a feeling
A feeling this code's bad
Oh yeah