Scripted world info does not appear in the world info menu

[45adhoc]

Now that the world info is accessible mid-adventure, I decided to look at the world info of one of my scripted adventures, only to find that it was empty. The following code demonstrates that scripted world info does exist in memory when run in an adventure:

const modifier = (text) => {
  
  if (!state.worldInfoAdded) {
    state.worldInfoAdded = true
    addWorldEntry('foo', 'bar')
    return {text: JSON.stringify(worldEntries)}
  }

return {text: text}
}

modifier(text)

However, it will not show up in the world info menu, even after setting world info to be shown in the scenario settings.

Update: It looks like the problem is a missing variable. Running the the above code in a test scenario produced the following:

[{"keys":"You","entry":"You are a cool dude.","isNotHidden":true},{"id":"0.23626612215539655","keys":"foo","entry":"bar"}]

The left entry was added through the world info menu, and the right was added through the script. It seems addWorldEntry has not been updated to use isNotHidden, which means scripted world info will never appear in the menu.

[Zynj-git]

const modifier = (text) => {
  
  addWorldEntry(`${worldEntries.length}`, "This is entry");
  worldEntries.forEach(entry => entry["isNotHidden"] = true); // true / false doesn't matter since it doesn't have an inherent effect.
  state.message = JSON.stringify(worldEntries);
  return {text: modifiedText}
}

// Don't modify this part
modifier(text)

Even when changing the isNotHidden variable for the entries they will remain hidden from the Edit Adventure -> World Information menu. This also happens for entries created via Scenario -> World Information that have been correctly assigned the variable, but altered via the above script.

[Zeracronius]

The property "isNotHidden" was deprecated and replaced by "hidden", as seen when exporting world info set to visible.

This means that you need to do "addWorldEntry(keys, entry, hidden = false)" instead.
Seems that they haven't updated the readme to reflect this yet.