Metastruct/artboard-api

Artboard WebSocket API and web page source code.

pixels-web-api

Web API for Artboard (fka Pixels).

Setup

Configuration

See config.example.js. Please make sure that every value that is in the configuration corresponds to types of the same value in the configuration example.

In case of errors in the types of one of the values in the configuration, the application will spew out an AssertionError, that provides where exactly was the error made.

Running

# Install dependencies, including developer ones
npm install --save-dev

# Compile TypeScript code
npm run build:ts

# Minify JavaScript with Closure Compiler
npm run build:web

# Start up the application
npm start

There's a file named ecosystem.config.js, that is specifically made for PM2 process. Before running, do not forget to do the first 3 steps above.

pm2 startOrReload ecosystem.config.js

Websocket

This software hosts a WebSocket server to communicate with Meta Construct servers and website clients.

Payloads

Every payload should be in JSON format.

{
  "op": "opCode",           // string,  OP code,                  required
  "data": "Hello, world!",  // any,     OP code data/argument(s), optional
}

If the client sends a payload, that does not follow the payload example above, the connection between the client and the server will be closed with code 1007 (unsupported payload).

Write access

Clients, whose IP addresses are in configuration property writeIPs have write access. This means that they can edit image data by sending addPixel payloads.

OP codes

addPixel

This OP code is used for both modifying the image data (if sent to the server) and notifying that the image data was edited (from the server).

Note that you can also use pixels field to modify more than one pixel.

Example payload

{
  "op": "addPixel",
  "data": {
    "x": 28,
    "y": 33,
    "color": 14,
    "steamId": "76561198086180059"
  }
}

{
  "op": "addPixel",
  "data": {
    "pixels": {...},
    "steamId": "76561198086180059"
  }
}

Sending

This OP code can be sent only by clients, that have write access. If the OP code was successfully sent, clients should receive addPixel OP code in return with the same arguments as the sent payload.

imageInfo

This OP code is sent from the server to the clients who have just connected. Its data contains information about the image, as well as the game's configured properties, such as banned, timeoutTime and dimensions.

Example payload

{
  "op": "imageInfo",
  "data": {
    "banned": {
      "76561198086180059": true
    },
    "data": {
      "image": [...],
      "palette": [
        [ 255, 255, 255 ],
        ...
      ],
      "paletteURL": "https://lospec.com/palette-list/random",
      "steamIDs": [ "76561198086180059", ... ]
    },
    "dimensions": [ 640, 480 ],
    "timeoutTime": 1000
  }
}

writeAccess

This OP code is sent from the server to the clients who have just connected. It contains boolean, which can be used to determine if the client has write access or not.

Example payload

{
  "op": "writeAccess",
  "data": true
}

executeTimeout

This OP code is sent only from the server whenever another client with write access has successfully sent the addPixel packet. This indicates to timeout the player whose Steam ID (in 64-bit format) is specified in data.

Example payload

{
  "op": "executeTimeout",
  "data": "76561198086180059"
}

imageUpdate

This OP code is sent only from the server whenever the image is changed. The payload data contains its difference between how it was updated before and after, as well as the Steam ID of the player (in 64-bit format) who made the change.

Example payload

{
  "op": "imageUpdate",
  "data": {
    "diff": {...},
    "steamId": "76561198086180059"
  }
}

imageReset

This OP code is only sent from the server each time the image is reset.