Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
1) Yes, spellcheck is part of articy:draft 3.
2) articy has condition and instruction node specifically for scripting. The recommended workflow would be to not put everything on one layer and entire conversations into one node, but for example to use a single node as a container for a conversation and have the single dialogue lines subdivided by speakers nested within.
3) There is code highlighting, but it is not customizable and only for the internal scripting language.
4) That would be possible by creating a plugin with the Macro Devkit.
To be honest, it sounds like your twine workflow does not match well with the core concepts of articy. But of course, you can download a free 14-day trial of articy:draft 3 to check out for yourself if articy is the right tool for your specific project: https://www.nevigo.com/en/articydraft/try/
Best regards,
Karsten