Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I'm not sure if this works with other formats, but with working with Chapbook, I have discovered that we can enable debugging by adding the `options="debug"` when running a story.  I'm not sure if you'd want to have a "publish" and a "debug" button.  It doesn't work if you're using the 1.1.0 micro format (as expected, as that's the code that was removed to make it smaller), but if you don't use that smaller format, it works from what I can tell the same as the test button in the Twine editor.  

What I could do if it's not there already is give access to the story options field in metadata; it should have the same effect. But I'd rather not release a new version just for that. Thanks!

(+1)

I'll take a look.  I just had to log out and back in because my system borked when trying a new to me game...  

It looks like the options field isn't available in the metadata.  I'd rather have something like that anyway, rather than having something specific to a single feature.  

Randomly came across your comment. I'm writing a story in the Chapbook format and would prefer to do so in a text editor but didn't know Backstage was an option in that case. Is it possible as you seem to say here? Can you please explain how? I'm able to compile and build from twee files using VS Code, but I would love to know how to add the Backstage feature. Currently I'm using Twine even though I prefer a text editor, because Twine has the Test button/Backstage.

When I look, at my chapbook.html I have:

```

It looks like it needs a relatively small edit to the output file putting `options="debug"` in the `<tw-storydata>` seems to do it.
```

as the explanation so you would put the attribute `options="debug"` in the <tw-storydata> element.  It's a bit of a manual fix, but it probably can be automated somewhat.  There probably already is an options attribute.  So just add the debug option.

Hey, folks. Sorry for the long silence. I ended up not needing Tee-Wee myself after all, so kinda set it aside. Been working on another thing, but once it's released I hope to pick up this baby again and give it a bit of a refresh, including access to the options field in metadata. Thanks for the patience!

(+1)

It works well as is.  While there are maybe some "feature request" things, it seems to not have any actual bugs at this point.

(1 edit)

That's great news! I'll stick to making small changes then. Let me know what else you need.

Edit: by the way, I had another complaint about the looks. Should I give Tee-Wee a facelift? It would be a bit of work, but it probably can't break anything.

(+1)

I think that it could use a facelift, but I'm more for functionality than looking good.  So, if it's mostly a re-skinning?  Sure, but if it would require looking at how you're accomplishing certain functions, wait until you have some serious time to focus on it.

Thanks for your reply! I'm not actually using Tee-Wee, but VS Code. That said, I was able to ask in the Twine discord and found out that there's a command line option for Tweego (the command line twee file compiler) that is "-t" (for "test") and that worked!

Your comment, even though it's specific to Tee-Wee, got me on the hunt for being able to use something other than Twine itself to see the debugging Backstage sidebar when testing my Chapbook game, so thanks again...

What I was doing probably would work for the Tweego compiler as well.  But throwing a flag on your compile is *way* easier.