Recently we completed a TWINE game with over 250k words. There are hundreds of variables and 1000+ passages. Great right? Well, then I realized that Harlowe data doesn't persist. Now I'm searching for a save option similar to one in sugarcube. Then, I'm ready to embark on learning that format. Any advice Twine wizards? Thanks as usual for your help in this.
Comments
The other question is if Harlowe has anything that SugarCube doesn't, feature wise, to avoid moving out of the frying pan and into the fire.
Case in point, IIRC, @greyelf posted a version of many of the "effect" styles from Harlowe for SugarCube on these forums at one point—I believe this is the post I'm remembering.
#1: UI.alert: The ui alert property is the equilavent in Harlowe as (alert:""). However, I try writing it into the passage like so
And I get an error. "Error: <<script>>: bad evaluation: UI is not defined "
Was I supposed to define the UI element somewhere? (I'm guessing in my CSS?) Worst of all, I have it defined. I pulled the bleached CSS sheet.
Now that I'm looking at it, is it that I don't have the UI.alert property specifically defined?
2. There are various posts to hide the bar. I just want to make sure that I understand the code here....
UI.saves() Now...the saves() is a function that I must define (or is it predefined?) in Javascript area of the editor?
Same with .
Note that in this case, I have the setup.stowUiBar in my javascript area.
I think once I get this figured out I should be able to move forward.
Thank you!
The current release of Twine 2 is from the v2.0.x series and comes preinstalled with SugarCube v1 only. If you want to use SugarCube v2, and you do, then you must install it manually.
The next significant update to Twine 2—the v2.1.x series—is currently in beta and will come preinstalled with SugarCube v2 as well.
That function is no longer necessary in SugarCube v2 as of release v2.12.0—current: v2.12.1. The UI API now has two methods—UI.stow() and UI.unstow()—which handle (un)stowing the UI bar.
I just wanted to say that you SHOULD use sugarcube. The flow is so much easier and it will make the process of creating a game much faster in the future. Great job @TheMadExile!
Yesss, this is the conclusion I've been dreading coming to, but it looks like the time has come. I'm just glad I realized this at the 30k mark, not when I'd finished transferring and coding the full 400k. o_o;;; Thank you for the advice! I can't even imagine how much rejiggering you're doing right now with your game.
And yes, @TheMadExile and @greyelf are boss.
1. I'm using software called "CODE COMPARE" to pull up two versions of my completed harlowe script.
2. Using find/replace, I've changed [[set: to <<set and so on.
After that, some changing in CSS and widget additions, it's basically the same.
Links are the same.
Variables are the same.
sooooooo, it's not impossible.
Note, I took a day to read the documentation and bug @TheMadExile on all questions I had until I feel comfortable doing this final read/copy & paste through.