Don’t rush, it’s going at a perfect pace.
It’s been a while and I was just wondering if there’s been any progress lately, not trying to BUMP the thread or rush you or anything…
LOR
243
@Dark_Bear2899 Nope, not rushing me at all. I’m actually in the process of getting another update out, all I really have left to do is write out a few dialogues you have with the characters and then it’s mostly good to go.
AWW YEAH! The thread hasn’t died! I am so happy this is going on! 
Thank goodness! I was starting to get worried #:-S
oh good I was getting worried lol xD can’t wait for the update
Oh that’s good. I like where this is going. My plans to woo myself into the Mistresses heart continue on! (I know it’s probably not possible…but head canon is a thing. ;___; )
LOR
249
Sooooo. I guess I went on an unannounced, semi-break to kind of collect my thoughts and get some stuff going on in my life under control. And I’ve recently become very inspired to start writing for Welcome To The Family again. My intention was to get the update out today or tomorrow so I started going through the demo to check for any mistakes and/or errors.
Basically, I need some coding help! My problem is something about “bad labels”. And how you fix them. Because this one little error is driving me crazy. Any bad label experts out there? :-S
Oh and @FallingCups the whole do-I-want-to-add-in-the-Mr-and-Mrs-as-ROs thing is still being debated (I know, I’m not good at this whole ‘deciding’ thing), so you have a chance! Maybe.
JLBH
250
Nice to have you back we missed you!
@LOR It would be helpful if you posted the exact error message, but odds are that there’s a spelling error causing a mismatch, ie. when you have *goto name, then *label name must also exist, because that goto needs to have somewhere to send the player, and both instances of name must be spelled -exactly- the same.
Smeet
253
@LOR Including capitalization, I believe. (continues P_Tigras statement)
LOR
254
@P_Tigras and @Smeet
The error message itself always comes up as line 129: bad label scene “att01” and the actual command on the document is a *goto scene “” one, so I’m not quite sure how to fix it.
@LOR Just a slight error (well, two) in your *goto_scene commands, e.g. in pro3.txt you have -
*goto scene “pro4”
in three places, which should be:
*goto_scene pro4
Note the under_score missing in the *goto_scene command itself, and no need for “quote marks” around the scene name.
(NB: When you’ve fixed those three, you will also need to remove the *finish commands immediately preceding each of them, or it won’t of course reach the *goto_scene commands as it will in each case *finish and immediately jump to the next sequential scene file).
LOR
256
@Vendetta Well, that’s actually how the code has always been in my game, so I haven’t changed anything in the older parts of the demo, code included. If it was area for an error, then wouldn’t that have come up already? I don’t mean to contradict you, this is an honest question. I’m using the newer version of Choicescript, if that means anything. But I’ve tried a few combinations from what you’ve said, and now I either get my first error (line 129: bad label scene “att01”) or a new error, which is:
Couldn’t load URL: scenes/“att01”.txt
[Exception…“Access to restricted URI denied” code: “1012” nsresult: “0x805303f4 (NS_ERROR_DOM_BAD_URI)” location: “file:///C:/Users/PublicDocuments/dfabulich-choicescript-87edd1f/web/scene.js Line: 277”]
JLBH
257
How many words is your game LOR
@LOR The reason you were getting a “bad label” error is that your command:
*goto scene (whatever)
means it was trying to reference (with the ordinary *goto command) a *label called scene, within the same file, and naturally couldn’t find one as it doesn’t exist. The correct command for jumping to a new file is indeed:
*goto_scene filename
where filename is the exact name of that .txt scene file, with no “quotes”. It is a different command to the ordinary *goto (label), but it really does need that *goto_scene underscore in there to understand what it is you’re trying to do, otherwise it treats it as an ordinary *goto.
All that said, I’ve just noticed that pro4.txt actually follows pro3.txt in your *scene_list, so you don’t actually need to use *goto_scene at all – just *finish will do fine there, so long as you don’t ever change the order of scenes listed in *scene_list.
Example:
*scene_list
aaa
bbb
ccc
If in aaa you want to go to bbb, you use *finish. If in bbb you want to go to ccc, you also use *finish. In effect, *finish means “go to the next file listed in *scene_list, regardless of what it’s called”.
However, if in aaa you want to jump straight to ccc, you use *goto_scene ccc. If in bbb or ccc you want to go back to aaa, you use *goto_scene aaa. In effect, *goto_scene means “go to this exact scene filename, regardless of where it is in the *scene_list sequence”.
HTH.
LOR
259
@Vendetta Ohhh. Thanks! That helped out a lot, really, thank you. Now all that’s left to do is finish checking over the update then I can finally put out some new content.
@JLBH According to Microsoft Word, there are a little over 21k words in my game
