Skip to main content

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

Thanks for catching these! I've fixed these in the 1.2.1 update, along with some fixes for transparent videos.

4 was me writing the guide wrong, no brackets is the intended syntax.

2 is less a bug and more how regex reads each line. You could put a tag anywhere on a line and it would be picked up; VT just nukes anything that appears before the starting hyphen. For now, VT just puts faith on the dev to not put tags after the hyphen, and also assumes the chances of needing to actually write something with the exact syntax of a tag in the narrative are zero. There are fixes for this, but it would need a complete rewrite of VT's original tag system, and ultimately the time sink vs. benefit of this is pretty low.

(+2)

Awesome, thank you!

Gotcha, that makes sense for 2. (Only found out because i was using an "E! - " prefix as a sort of comment when trying to find out what was going on with the code)

Excited to make a little story about horrible lesbians now <3 thank you!

(1 edit)

found another bug i think?
GOTOs weren't working so i switched the order of the "drawDialogue(...)" and "if(goto!=null){...}" (to make drawDialogue after the goto check) blocks in the updateDialogue function, and now they work again.

idk the code so this miight have introduced a new bug or something? unsure! but now they work again and i'm happy

alright that looks like a new one i can't replicate, if you're able to throw me over the project when you're able to i can check out what situation causes that to happen

replicated it with a fresh copy by doing the following:

story.txt is

START
uhh
GOTO:CHAP12345 - asdf
###
CHAP12345
this will never print
###

delete all assets except blank, bg_title, bg_texture1.  Deleted all audio files and video files from the folders as well.

assets.js is:

const IMGs = {
    BG_TITLE:"images/BG_TITLE.png",
};
const VIDs = {
};
const MUSIC = {
};
const SPEAKERS = {    
  M: {name: "machine", colour: "#696969"},   E: {name: "engineer", colour: "#8b66ba"},   P: {name: "pilot", colour: "#e3a239"} };

I couldn't replicate it until i got rid of most of the assets, so I'm thinking that's the issue (and the debugger in firefox gave the consoler error

"Uncaught TypeError: track is null    sfxPlayer http://localhost:8000/code/tags.js:697"

so i think maybe that's messing stuff up a bit? and it's bailing on the rest of the function??? idk)

(1 edit)

ah, that's not a bug. VT:S requires you to keep the SFX_TEXT file since it's always used for progression. i'll probably include a note on that in the guide in the next update and break the name out into the config

oh!  makes sense!
thanks :)