<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  
  <title>Dialogue Branch News &amp; Updates</title>
  <subtitle>News and release updates from the Dialogue Branch project.</subtitle>
  <link href="https://www.dialoguebranch.com/news/feed.xml" rel="self" />
  <link href="https://www.dialoguebranch.com/" />
  <updated>2026-11-13T00:00:00Z</updated>
  <id>https://www.dialoguebranch.com/</id>
  <author>
    <name>Fruit Tree Labs</name>
    <email>info@dialoguebranch.com</email>
  </author>
  <entry>
    <title>Dialogue Branch v0.10.0: Core Java API updates</title>
    <link href="https://www.dialoguebranch.com/news/2026/release-0-10-0/" />
    <updated>2026-11-13T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2026/release-0-10-0/</id>
    <summary>The core Java library is now easy to use on its own: load a project and play a dialogue in a few lines, with replies into other dialogues followed for you.</summary>
    <content type="html">&lt;p&gt;Just in time for the weekend, we released v0.10.0. This update focuses on the core Java library, making it easier to integrate Dialogue Branch into a Java application. Specifically:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A dialogue in a few lines.&lt;/strong&gt; Load a project, start a dialogue for a user, and each step comes ready to show: the speaker, the text and the replies. Choosing a reply gives you the next step. The &lt;a href=&quot;https://www.dialoguebranch.com/&quot;&gt;home page&lt;/a&gt; has a short example, and the &lt;a href=&quot;https://www.dialoguebranch.com/docs/core-java/&quot;&gt;core library documentation&lt;/a&gt; has more.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Replies into other dialogues just work.&lt;/strong&gt; When a reply leads into another dialogue, the library follows it by itself, in the same language and with the same variables.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Logs, going back and resuming.&lt;/strong&gt; Your application can keep a log of the conversation, go back a step, cancel, and pick up a dialogue later from its log, just as the Web Service does.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clearer errors.&lt;/strong&gt; All parse errors in a project are reported together in one exception, and choosing a reply that isn&#39;t on offer, or continuing a dialogue that has already ended, gives a clear error. Dialogues can be looked up by name and language, falling back to the source language when there&#39;s no translation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The command-line tool&lt;/strong&gt; plays a dialogue in the source language when it isn&#39;t translated, and keeps variables from one dialogue to the next.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Web Service and Studio.&lt;/strong&gt; An unknown step or reply now gets a &lt;em&gt;404 Not Found&lt;/em&gt; instead of a server error, also in test sessions, and Studio&#39;s workspace follows the conversation into the next dialogue.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you already use the core library directly, a few methods have changed: &lt;code&gt;ActiveDialogue&lt;/code&gt; now needs to know where to find other dialogues, and choosing a reply is now a single &lt;code&gt;selectReply(...)&lt;/code&gt;. The &lt;a href=&quot;https://github.com/dialoguebranch/platform/releases/tag/v0.10.0&quot;&gt;release notes&lt;/a&gt; list what to change. The Web Service, Studio and the JavaScript client need no changes.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Speakers, gendered translations and safer testing: Dialogue Branch 0.8 and 0.9</title>
    <link href="https://www.dialoguebranch.com/news/2026/speakers-and-translations/" />
    <updated>2026-11-12T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2026/speakers-and-translations/</id>
    <summary>Projects now know their speakers, translations can follow the gender of the speaker and the user, and testing a dialogue can no longer touch real user data.</summary>
    <content type="html">&lt;p&gt;We released v0.8.0, v0.8.1, v0.9.0, v0.9.1 and v0.9.2 over the past two weeks. Here&#39;s what&#39;s new.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Speakers.&lt;/strong&gt; A project can now define its speakers, each with a name, a gender and an optional default, and Studio checks the nodes against them. Renaming a speaker renames it in every node and translation, after showing what will change, and a node with an unknown speaker gets a warning (never an error). See &lt;a href=&quot;https://www.dialoguebranch.com/docs/language/dlb-project.html#speakers&quot;&gt;speakers&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Translations that follow gender.&lt;/strong&gt; In languages where a sentence changes with the gender of the speaker or of the person addressed, a translation can now follow both. The end user&#39;s gender is set through the reserved variable &lt;code&gt;$dlb.userGender&lt;/code&gt;, the Translation Editor has &lt;em&gt;Female user&lt;/em&gt; and &lt;em&gt;Male user&lt;/em&gt; translations, and Studio can test a dialogue as a female or male user. See &lt;a href=&quot;https://www.dialoguebranch.com/docs/language/dlb-project.html#translation-files&quot;&gt;translation files&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Testing never touches real data.&lt;/strong&gt; A test session runs against its own copy of the user&#39;s variables. Admins can &lt;em&gt;simulate&lt;/em&gt; a user to look into a problem without changing anything, and acting for real as someone else is clearly marked. A new &lt;em&gt;Users&lt;/em&gt; page erases everything stored about a user.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A sturdier External Variable Service.&lt;/strong&gt; The Web Service now authenticates to it with a Keycloak token, a slow or unreachable service no longer stalls a dialogue, and Studio shows whether it is running, with the hints it gives for its variables (type, allowed values, read-only). See &lt;a href=&quot;https://www.dialoguebranch.com/docs/web-services/external-variable-service.html&quot;&gt;the External Variable Service&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Simultaneous requests are safe.&lt;/strong&gt; Two requests from the same user at the same moment, such as a double tap or two open tabs, no longer overwrite each other.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A security update.&lt;/strong&gt; v0.9.1 moves the Web Service and Studio to Spring Boot 4.1 and current libraries, and the Docker images have no known critical or high vulnerabilities.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Variables per dialogue.&lt;/strong&gt; The list of a project&#39;s variables now says which dialogues read and write each one, so a client can show the variables of a single dialogue.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Two of these releases contain changes that can break existing setups: variable names with a dot in them (&lt;code&gt;$settings.theme&lt;/code&gt; is now one variable), the reserved &lt;code&gt;dlb.&lt;/code&gt; prefix for variable names, the new node colour tag, and the new authentication of the External Variable Service. Before you upgrade, read the notes of &lt;a href=&quot;https://github.com/dialoguebranch/platform/releases/tag/v0.8.0&quot;&gt;v0.8.0&lt;/a&gt; and &lt;a href=&quot;https://github.com/dialoguebranch/platform/releases/tag/v0.9.0&quot;&gt;v0.9.0&lt;/a&gt;, which list what to change. Every release, with its notes, is on the &lt;a href=&quot;https://github.com/dialoguebranch/platform/releases&quot;&gt;releases page&lt;/a&gt;.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Catching up: one platform, Studio, and a new website</title>
    <link href="https://www.dialoguebranch.com/news/2026/catching-up/" />
    <updated>2026-11-12T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2026/catching-up/</id>
    <summary>It&#39;s been quiet on this page since early 2024, but not in the code: everything now lives in one repository, the Web Client grew into Studio, there&#39;s a JavaScript client on npm, and a new website.</summary>
    <content type="html">&lt;p&gt;It&#39;s been quiet on this page since early 2024, but not in the code. Here&#39;s what has happened since:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One repository.&lt;/strong&gt; The language, the core Java library, the Web Service, the example scripts and everything else now live together in &lt;a href=&quot;https://github.com/dialoguebranch/platform&quot;&gt;dialoguebranch/platform&lt;/a&gt;, and are versioned and released together.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dialogue Branch Studio.&lt;/strong&gt; The Web Client from the &lt;a href=&quot;https://www.dialoguebranch.com/news/2024/release-1-2-0/&quot;&gt;v1.2.0 post&lt;/a&gt; grew into Studio: a web app where you edit dialogues as a graph of nodes, play them through, translate them, and publish them when they&#39;re ready, with drafts kept apart from what your users see (&lt;a href=&quot;https://www.dialoguebranch.com/docs/web-services/studio.html&quot;&gt;about Studio&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A JavaScript client on npm.&lt;/strong&gt; &lt;code&gt;@dialoguebranch/client-js&lt;/code&gt; lets your own app play dialogues from a Web Service, and is published with every release (&lt;a href=&quot;https://www.dialoguebranch.com/docs/web-services/third-party-clients.html&quot;&gt;connecting your app&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New version numbers.&lt;/strong&gt; Because the platform is still finding its final shape, its versions were reset to 0.x in September 2026, to say so honestly; the old 1.x release tags were renumbered with them. Full stability promises start at 1.0. Releases now come every few weeks; the latest is &lt;a href=&quot;https://github.com/dialoguebranch/platform/releases&quot;&gt;v0.9.2&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A new website and documentation.&lt;/strong&gt; You&#39;re looking at it: this website was rebuilt, and the &lt;a href=&quot;https://www.dialoguebranch.com/docs/&quot;&gt;Documentation Hub&lt;/a&gt; now lives right here on it, generated from the platform&#39;s own repository.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>Code Release v1.2.0!</title>
    <link href="https://www.dialoguebranch.com/news/2024/release-1-2-0/" />
    <updated>2024-02-01T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2024/release-1-2-0/</id>
    <summary>Release v1.2.0 brings the first version of the Dialogue Branch Web Client: a quick way to try out dialogues against a running Web Service, and a starting point for your own web apps.</summary>
    <content type="html">&lt;p&gt;We have created the v1.2.0 GitHub code releases for all of the Dialogue Branch software repositories: the Core Java Library, the Web Services and the Example Scripts. (These repositories have since been merged into &lt;a href=&quot;https://github.com/dialoguebranch/platform&quot;&gt;one&lt;/a&gt;, and their releases renumbered; see the &lt;a href=&quot;https://www.dialoguebranch.com/news/2026/catching-up/&quot;&gt;catch-up post&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;The major element of this release is the first version of the &lt;em&gt;Dialogue Branch Web Client&lt;/em&gt; application (see image below). The Web Client serves a couple of different purposes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;First, it&#39;s a quick and easy entry point to start experimenting with Dialogue Branch. Once you have a running Web Service, this tool allows you to easily interact with that web service by logging into an account, selecting a dialogue from the Dialogue Browser to start, using the Interaction Tester to run through the dialogues and seeing how variables are updated in real-time through the Variable Browser.&lt;/li&gt;
&lt;li&gt;Second, the Web Client is the quickest and friendliest way to test your dialogues before deploying them to a real application. Additional features are being planned to easily manipulate variables, so that different dialogue routes and corner cases may be tested with ease.&lt;/li&gt;
&lt;li&gt;And finally, the Web Client is the best starting point for making your own dialogue-driven web applications. It is a template for creating any type of web app that includes Dialogue Branch dialogues and consists of a neatly organized set of JavaScript classes that you may easily extend and use freely in your own applications.&lt;/li&gt;
&lt;/ul&gt;
&lt;img src=&quot;https://www.dialoguebranch.com/news/img/2024-02-01-web-client-screenshot.png&quot; class=&quot;news-image&quot; alt=&quot;The first Dialogue Branch Web Client, with its Dialogue Browser, Interaction Tester and Variable Browser&quot;&gt;
&lt;p&gt;So, go check out the code, and start exploring this new addition to the Dialogue Branch toolsuite!&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Code Release v1.1.0!</title>
    <link href="https://www.dialoguebranch.com/news/2023/release-1-1-0/" />
    <updated>2023-11-13T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2023/release-1-1-0/</id>
    <summary>Release v1.1.0 focuses on making the core Java library easier to read, dropping the DLB prefix from almost all of its class names.</summary>
    <content type="html">&lt;p&gt;Over the past days we have created the GitHub code releases v1.1.0 of the Dialogue Branch software packages: the Core Java Library, the Web Services and the Example Scripts. In order to simplify the version numbering between the different repositories, we will simultaneously release code versions for all Major and Minor updates (i.e. vX.Y.*), which also includes a release of the &amp;quot;Example Scripts&amp;quot; repository.&lt;/p&gt;
&lt;p&gt;In this release, the focus has been on improving code readability of the core Java library (and thus each package that uses it). In the previous library version, almost all Class names were prefixed with &amp;quot;DLB&amp;quot; — a convention that grew over time, but ultimately led to awkward code. Almost all of these references have now been removed. So, where previously we would talk about a &amp;quot;&lt;strong&gt;DLBParser&lt;/strong&gt;&amp;quot; parsing &amp;quot;&lt;strong&gt;DLBNode&lt;/strong&gt;s&amp;quot;, consisting of &amp;quot;&lt;strong&gt;DLBNodeHeader&lt;/strong&gt;s&amp;quot; and &amp;quot;&lt;strong&gt;DLBNodeBody&lt;/strong&gt;s&amp;quot;, now we refer to a &amp;quot;&lt;strong&gt;DialogueBranchParser&lt;/strong&gt;&amp;quot; that parses &amp;quot;&lt;strong&gt;Node&lt;/strong&gt;s&amp;quot;, consisting of &amp;quot;&lt;strong&gt;Body&lt;/strong&gt;s&amp;quot; and &amp;quot;&lt;strong&gt;Header&lt;/strong&gt;s&amp;quot;.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>New Examples Script Repository</title>
    <link href="https://www.dialoguebranch.com/news/2023/examples-repository/" />
    <updated>2023-05-15T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2023/examples-repository/</id>
    <summary>A new repository of example .dlb scripts, for learning the language or testing your own Dialogue Branch software.</summary>
    <content type="html">&lt;p&gt;We&#39;ve added a new repository to the &lt;a href=&quot;https://github.com/dialoguebranch/&quot;&gt;Dialogue Branch GitHub&lt;/a&gt; page, containing example .dlb scripts that are useful to learn the concepts of the Dialogue Branch language, or to test any software you&#39;re building that uses a Dialogue Branch parser. (Today, these examples live in the &lt;a href=&quot;https://github.com/dialoguebranch/platform/tree/main/examples&quot;&gt;examples folder&lt;/a&gt; of the platform repository.)&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Documentation Hub Online</title>
    <link href="https://www.dialoguebranch.com/news/2023/documentation-hub/" />
    <updated>2023-05-12T16:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2023/documentation-hub/</id>
    <summary>The Documentation Hub is online, with guides to the .dlb language and to running Dialogue Branch in a client-server setup.</summary>
    <content type="html">&lt;p&gt;Our &lt;a href=&quot;https://www.dialoguebranch.com/docs/&quot;&gt;Documentation Hub&lt;/a&gt; is now online. This should help new users navigate the software released earlier today. As a starting point, check out the &lt;a href=&quot;https://www.dialoguebranch.com/docs/language/&quot;&gt;Language Documentation&lt;/a&gt; explaining the .dlb language format that can be parsed by the core Java library, or look at the &lt;a href=&quot;https://www.dialoguebranch.com/docs/web-services/&quot;&gt;Web Services&lt;/a&gt; section if you&#39;re interested in using Dialogue Branch in a client-server setup.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Code Release v1.0.0 for Core Library and Web Services</title>
    <link href="https://www.dialoguebranch.com/news/2023/release-1-0-0/" />
    <updated>2023-05-12T10:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2023/release-1-0-0/</id>
    <summary>The first official stable releases of the core Java library and the web services.</summary>
    <content type="html">&lt;p&gt;On our &lt;a href=&quot;https://github.com/dialoguebranch&quot;&gt;Dialogue Branch GitHub page&lt;/a&gt;, we have created the v1.0.0 Release Tags for the core Java library and the web services. This marks the first official stable releases of the Dialogue Branch Platform Components.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>dialoguebranch.com Website Launch</title>
    <link href="https://www.dialoguebranch.com/news/2023/website-launch/" />
    <updated>2023-04-13T00:00:00Z</updated>
    <id>https://www.dialoguebranch.com/news/2023/website-launch/</id>
    <summary>Welcome to Dialogue Branch, the new open-source branching dialogue platform!</summary>
    <content type="html">&lt;p&gt;Welcome to Dialogue Branch, the new open-source branching dialogue platform!&lt;/p&gt;
&lt;p&gt;Over the next weeks and months, we will be releasing updates to the platform and its documentation. For now, we are working on getting our Documentation Hub up-and-running, releasing the source code for the Dialogue Branch Web Service, and preparing for an official platform launch!&lt;/p&gt;
&lt;p&gt;If you want to stay up to date, drop us an email at &lt;a href=&quot;mailto:info@dialoguebranch.com&quot;&gt;info@dialoguebranch.com&lt;/a&gt;.&lt;/p&gt;
</content>
  </entry>
</feed>