Migrating To v3

Stefano Balietti edited this page Feb 20, 2017 · 11 revisions
  • status: complete
  • version: 3.x

Migrating to nodeGame 3.0 and 3.2

nodeGame version 3.0 and 3.2 are fully backward-compatible with version 2.x. For information about migrating from earlier versions refer to the Migrate to v.2 page.

Update! Version 3.5

Version 3.5 introduced new features that could potentially be backward-incompatible:

  • New properties of the game object (rename accordingly)

    • node.game.matcher
    • node.game.role
    • node.game.partner
  • New step properties (rename accordingly):

    • matcher
    • roles
  • API changes:

    • node.game.getProperty(property, notFound). The second parameter is now a value that should be returned in case the property is not found (before was gameStage). Replace with node.game.plot.getProperty(gameStage, property, notFound).
  • If you make use of the Matcher API, and you had an autoplay player, it might need to be adapted. See the ultimatum autoplay for a template.

Next Topics

Next: Start the Tutorial v.3

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.