Twine Wiki

The Twine windows installer has an incorrect version of the Visual C++ runtime redistributable included. As a result, users who did not already have a correct version of the runtime installed may not be able to run 1.4.

Try to install the VC++ 2008 Service Pack 1. Be sure to install the x86 version.

Annotation passages appear darker than intended when the “Faster but rougher story map display” preference is off.

When editing a passage, the monospace font uses the normal font's font size instead of its own.

The Sugarcane sidebar's CSS is missing “left:7.5em”, thus placing it too far to the left of the screen.

Put this CSS code in a stylesheet passage: #sidebar { left:7.5em; }

The syntax highlighting for external links is broken - all external links are displayed as bad links even if they begin with “http://”.

Due to a bug, you currently can't use variables as array indexes (such as $weapons[$hand]) unless you include extra padding whitespace.

Put a space between the array variable and the first square bracket: $weapons [$hand]

«choice» ought to disable both itself and every other «choice» macro in the passage - but in 1.4.0 it only disables itself.

The shorthand <<display>> syntax sometimes gives a nonsensical error if no arguments are given - for instance, <<Start>> doesn't work.

Put a space between the passage's name and the ending >>: <<Start >>

Due to a bug, «nobr» produces an error message if any text at all follows the closing «endnobr» tag, including whitespace. It also doesn't allow nesting «nobr» tags (but admittedly, that's not really useful at all).

Use the \ line-continuation symbol in place of «nobr» in situations where this would be an issue.

If you use the obfuscation option, the \ line-continuation symbol will be incorrectly changed to a backslash followed by a random letter, and the line will not continue.

This macro's absence is not actually a bug. «textinput», a macro that was added in the Twine 1.3.6 alpha, was removed from the Twine codebase by its author, as it was intended primarily for testing and was never meant for actual end-use. (In Twine 1.4.1, it may be possible to use raw HTML <input> tags to replicate the original functionality of «textinput», with the advantage of allowing more input types than just text boxes.)

You can re-insert «textinput» by including this script:

macros.textinput={handler:function(a,b,c){if(c[1]){var d=c[0].replace(/\$/g,"");el=document.createElement("span");var e="<input id='"+d+"' type='text' onkeypress=\"var charCode; if(event && event.which){charCode = event.which;}else if(window.event){event = window.event;charCode = event.keyCode;}if(charCode == 13) {state.history[0].variables."+d+" = this.value; state.display('"+c[1]+"')}\"/>";if(c[2]){e+="<input type='button' value='"+c[2]+"' onclick=\"state.history[0].variables."+d+" = getElementById('"+d+"').value; state.display('"+c[1]+"');\"/>"}el.innerHTML=e;a.appendChild(el)}else{throwError(a,'"[PassageName]" parameter missing')}}};

Just as in 1.3.5, the «back» macro may not function correctly for game states loaded from a bookmark. If you bookmark a passage that contains a «back» macro, then reload from the bookmark, the «back» macro won't work because the loaded page is the only page in the browser history. However, the «return» macro also suffers from this deficiency, for reasons

Use [[Return|previous()]] instead of «return».

If the StorySettings option “undo” is off, then «back» may cause link variables in preceding passages to be forgotten or incorrect.

In Twine 1.4, the “href” attribute was removed from internal links, because it has no purpose (except to clue the especially canny player into the fact that the link is specifically an internal link, which may “tip the hand” of certain authors unwillingly). However, this inadvertently means that the “a:link” CSS selector promoted by Ashton Raze no longer selects internal links (since “a:link” is a synonym for “a[href]”).

Use a more precise selector for passage links, such as “.passage a”, as described here. This selector has the advantage of not selecting links outside of the passage (for instance, in the Sugarcane sidebar).

Some old scripts, such as Leon Arnott's Tag CSS, contain a shim to get them to work with the Start passage in Twine 1.3.5, by using the state.history object. Unfortunately, the script (and presumably others like it) does not correctly check for the existence of state.history[0].passage, so it will crash in Twine 1.4. (If you are getting the error message state.history[0].passage is null or something similar, this is likely the reason.) Due to the popularity of this and other scripts, a counter-shim may be installed in Twine 1.4.1 to counteract this.

Strictly speaking, none of the 'monkey patch' Twine 1.3.5 scripts (which can be taken to mean “those that don't add new macros”) are officially supported by Twine 1.4 - since they directly replace key engine functions like History.prototype.display, they will likely eliminate new 1.4 engine features and replace them with inferior 1.3.5 features.

If you're using any of these scripts (which includes Tag CSS), you should delete them from your projects, as their functionality is present in Twine 1.4 out-of-the-box.