Inexor Flex

Build Status

Inexor Flex is platform for managing Inexor Core instances and the Inexor Tree API and provides a scripting environment for servers and clients. Inexor Flex also makes multiple user interfaces using web technologies available.




  • Exposes the Inexor Tree API via REST/JSON
  • Provides multiple web applications (HTML5/JS/CSS)

Web Applications (HTML5/JS/CSS)

  • Inexor Flex User Interface
  • Inexor Core (Client) Menu & Application
  • Inexor Core (Client) HUD
  • Inexor Core (Server) User Interface

Inexor Tree Client

  • Communication to an local or remote instance of Inexor Flex using the Inexor Tree API via REST

Business Logic

  • Inexor Tree API
  • Texture-Manager
  • Map-Manager
  • Media-Manager (Music, Sound, Videos)
  • Server-List-Manager

Configuration Management

  • Reads/writes configuration files from disk / database
  • Reads configuration from command line parameters
  • Populates the Inexor Tree

Manages Inexor Core instances

  • Creates, starts, stops and destroys instances of Inexor Core

Operating System Bindings

  • Command line arguments parsing
  • URI-Scheme
  • Tray icon
  • Notifications

Implementation guide


The coding style-guide proposed by Airbnb is desirable. Since by default node >=6.9.1 is required, most ES6 features will work. Alternately, consider for reference.

Design guideline

The Inexor Flex has been designed to be as flexible as possible, therefore following a straight design guide:

  • everything, if possible, is a module
  • loosely-coupled components (such as plugins) are wired using electrolyte
  • by default unit tests with mocha are done for any file that matches *_test.js, though it is highly recommended to add a test folder to your module
  • by default documentation is done using JSDoc. don't break that.
  • if necessary (for important or big modules), we urge that you add a separate to the respective module
  • we preserve to force the style-guide in the future

The core implementation

Flex necessarily can't be decoupled as a whole, therefore the core implementation is splitted among the following parts:

  • server/ containing the webserver and RESTfull API
    • index.js wires up everything and takes care of the cli
  • src/ containing essential modules
    • src/tree/ contains extensive functions to work with binary trees ("the root of evil")
    • src/connector is the gateway to an instance of Inexor Core
    • src/manager manages Inexor Core instances
    • src/configurator reads configuration files and provides them to the game

Since those components tightly couple each other, and must work in order to start the game, components from src usually are hard-loaded via require. This in turn means that in order to hook into the API, code must be added manually.

The RESTfull API

Documentation shall be done via swagger as soon as the v3 spec is released, which brings AnyOf support. In the meantime please have a look at api/v1.The comments should be sufficient.

Writing plugins

Have a look at the plugin documentation.

Flex won't start, resolving conflicts with the module manager

If Inexor Flex won't start for strange reasons the most likely reason is that you've worked with a earlier revision in which the dependencies weren't at all ready. By that case you'll most likely get the master branch running again following down these steps:

  • unlink any globally linked module with sudo npm unlink @inexor-game/modulename
  • delete all node_modules folders using e,g: rm -r */node_modules && rm -r */*/node_modules
  • install the app again after all with npm install, which can take some time (the modules are small, but in a central dependency root they're quiet a bummer)


Following is still undone:

  • [x] complete the plugin framework
  • [ ] complete the TOML configurator
  • [ ] add extensive command line arguments to ./flex as described in the wiki
  • [x] fix the documentation
  • [ ] add a task to automagically reinstall modules once they are changed (for development)
  • [ ] test everything extensively, fix passages that are marked with TODO (and add unit tests!)
  • [ ] glue together UI, Flex and Core with submodules, see this issue
  • [ ] add a snapcraft.yaml to package flex independently