yate

KO | EN

gitlite — search

#python #java #python3 #arduino #golang #machine-learning #rust #html #flask #javascript #seismology #nodejs

★ 17 Open GitHub ↗

"Yet Another Tabletop Experience" - Tabletop Browser Game Engine

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

![](https://raw.githubusercontent.com/RichtersFinger/yate/master/img/_server_/yate_banner.jpg)

# yate - „Yet Another Tabletop Experience"
„Yet Another Tabletop Experience" is a simple Node.js/Socket.io-based engine to play games with friends in your browser.
This project was initiated due to restrictions regarding personal contacts in early 2020 and the consequential limited options to play games with friends.
Originally, yate was intended as an engine solely for playing Pen&Paper games.
However, yate has since grown to support many more game elements (like cards or lotteries) needed up to the point where most games can be played out-of-the-box.
Its advantage compared to other board game simulations is the compatibility since only a modern browser is required to play.
Simply use a search engine to find an image of your favourite board game and/or other materials needed and start playing (see for example the [yate vanilla card deck](https://drive.google.com/drive/folders/11yqADr7aCYuwYoOLXXM1J0th-CLBmHYR) or [game of dice board](https://drive.google.com/drive/folders/1pG4pD0DvSxBVgI5RGgImXVmG2dzQ5-vl)).
Also have a look at the [YouTube channel](https://www.youtube.com/channel/UC_QIouG5f1K7kbNoxriW3LA) for a [trailer](https://youtu.be/Tz774QcYZ0E) and [demos](https://www.youtube.com/playlist?list=PL_T05W_uwBK1Fsq8mLjbVHRR-kKcc4KXz) for the setup and game management.

[<img src="http://img.youtube.com/vi/Tz774QcYZ0E/0.jpg">](https://youtu.be/Tz774QcYZ0E)

## Contents

* [Setup](#setup)
* [List of Features](#list-of-features)
   * [Recent Additions](#recent-additions)
	* [Controls](#controls)
   * [Game Elements](#game-elements)
   * [Game Settings & Actions](#game-settings--actions)
* [Planned Additions](#planned-additions)
* [Known Issues](#known-issues)
* [License](#license)

## Setup
The host of the game, i.e. the person running the server (this does not need to be the game master), has to install Node.js (the server software) and a few small components. See the [demo-playlist](https://www.youtube.com/playlist?list=PL_T05W_uwBK1Fsq8mLjbVHRR-kKcc4KXz) for a setup tutorial. Here is a detailed description of what the host has to do to set up yate:

1. Install `Node.js` with `npm` from [here](https://nodejs.org/).

(Optional: I recommend to add the binary directory of Node.js to your path variablea.)
2. Download the contents of this repository and move them into a clean directory.
3. Open a shell/terminal in the newly created yate directoryb. Execute `npm` to install the components `express` and `socket.io` using the command
 ```console
 $ <path-to-npm>/npm install express socket.io
 ```
4. Test the server by issuing
 ```console
 $ <path-to-node>/node index.js
 ```
 in the shell/terminal. If no errors occured, the shell/terminal message shows your public IP-address and the local port on which the server is listening in the format XXX.XXX.XXX.XXX:8080 . Paste this address (or simply localhost:8080 if you are on the same machine) into your browser address bar and connect to the server. You can change the local port in the file `index.js`.
5. In order to give other people access to your server, you most-likely have to configure your router to forward/map the port accordingly (TCP). Other players can then join your game using the IP-address from above. If you want to use a different local port, simply edit the line `const port = 8080;` in `index.js`.

6. Prepare a list of players (i.e. names of all players) by simply editing the existing file `players.dat` with a text editor. The first line of that file is referring to the game master. Note, that this game master will be the only „player" having full control over game elements. You can then add the names of players for your game line by line. If you prefer to have other players to verify themselves, you can add a required passphrase separated by a tabulator behind the player names.c

See the [List of Features](#list-of-features) and [demos](https://www.youtube.com/playlist?list=PL_T05W_uwBK1Fsq8mLjbVHRR-kKcc4KXz) for more information on how to prepare a simple game.

a The Windows-installer offers to do so automatically. Alternatively, see the instructions for Windows [here](https://stackoverflow.com/a/9546345).

b On Windows use Shift+Right Click in the directory then select the shell option from the context menu (see explanation for Windows [here](https://stackoverflow.com/a/60914)).

c Depending on your OS and choice of text editor the format for line endings may vary. The player list provided in this repository uses Unix (LF) line endings instead of Windows (CR+LF) line endings. If possible, change your editor settings accordingly or simply make a new `players.dat` file from scratch in the format shown in the setup tutorial.

### Additional Features
By additionally installing [Jimp](https://www.npmjs.com/package/jimp) you can create thumbnails for all images you placed in the `img/` directory. To this end, first install Jimp by entering
 ```console
 $ <path-to-npm>/npm install jimp
 ```
and after a successful install you can execute
 ```console
 $ <path-to-node>/node makethumbnails.js
 ```
This script will search for compatible image files (jpg or png) in your `img/` directory and automatically place thumbnails of those images in `img/_thumbnails_/`. If you then open an image selection-dialog in yate you get a thumbnail-preview of an image from the autocomplete you hover over with your mouse.

## List of Features

### Recent Additions
* **timer element added**: a configurable `Timer` element is now available
* **sfx volume+test**: added a test button and volume slider in `Play Sound` dialog
* **dice roll sfx**: animated dice make a dice roll sound on roll; disable globally with game option `disableDieSound`; animation has been improved
* **various minor changes**: fixed laggy zoom on `Canvas`, added banner shown while holding `Spacebar` to place animated pointers, visibility option for `Canvas`, ..
* **thispersondoesnotexist support**: Pictures of random faces can now be loaded in descriptions of `Tokens`. Those images are fetched from [thispersondoesnotexist.com/](https://thispersondoesnotexist.com/).
* **Canvas Overhaul**: The `Canvas` tool-window has been reworked for a more intuitive control. Brush types (as in creation of rectangles or ellipsis) and background transparency have been added.
* **Image Thumbnails**: Execution of the script `makethumbnails.js` enables the automated creation of image thumbnails (if [Jimp](https://www.npmjs.com/package/jimp) is installed, see Additional Features above for details). During image selection this thumbnail is shown on mouseover in the autocomplete list.
* **Controls**: The context now menu contains an option `Show Controls` opening a window detailing the controls.
* **New Log Window**: The log window can now be dragged and resized.
* **Animated Pointers**: Players and the game master can place animated pointers by holding `Spacebar` and clicking with 'Left Mouse Button'.
* **Change Indicator on Game Elements**: Game elements that have been changed but not pushed to the server yet are highlighted by a blinking border.

### Recent Fixes
* **jQuery migration**: migrated to jQuery 3.7
* **die roll sfx**: updated die roll sfx
* **card games**: fixed some issues when using game option-related settings like drag-to-top
* **canvas rectangles**: removed bug where rectangles were deleted on resize
* **more various changes**: see file `changelog.log` for details
* **various minor fixes**: fixed bugged `Marker` descriptions, ..
* **Canvas**:  A number of smaller issues have been fixed.
* **Thumbnails**: Thumbnail-previews are not correctly hidden if an image is selected.

### Controls
Players can open a list of controls with the option `Show Controls` from the context menu.
* **Move Camera**: Hold `Middle Mouse Button` and drag your mouse to move your view.
* **Zoom In/Out**: By turning the `Mouse Wheel` you can zoom in and out of the game.
* **Interact**: You can drag&drop most game elements (if you are permitted to by the game master) or double click with your `Left Mouse Button` to interact (e.g. double clicking on a `Die` will initiate a dice roll, whereas a double click on a `Card` will cause this card to turn over).
* **Modify**: By clicking with your `Right Mouse Button` you can open a [context menu](https://swisnl.github.io/jQuery-contextMenu/) of available actions.

Game Master Controls: Aside from general settings and actions you will find a section referring to the game element clicked on. This section is initiated with a label containing the type of the game element and its internal id. There the game master can `push`, `delete` or modify settings of this game element. See below for a detailed description of all functionalities. Most elements can also be manipulated in size or regarding the element layering by holding `Shift` or `Alt`, respectively, while turning the `Mouse Wheel`. Unpushed changes are indicated by an orange flashing or the respective game element's background/border.
* **Pointer**: By holding `Spacebar` and clicking with your `Left Mouse Button` you can place a pointer at that location visible to everyone else. This pointer is temporary and vanishes after a few seconds. The pointer color can be set by opening the context menu while holding down `a` and clicking on `Select Pointer Color`.

### Game Elements
Aside from the `Die` elements that are only visible for their creator, only the game master can create game elements. After creation those elements are initially only a local object until either the `Push This` or the `Push All` actions from the context menu are performed. Only then the server receives the information. In general, changes that are made in the configuration of game elements will be local until pushed to the server. In some cases there will also be shown a `Restore` option to reload the current server-side settings for the given element. Selecting `Push Delete` will immediately delete the selected element from the server. All updates the server receives are passed on to all clients.

* **Image Element**
   The `Image` element is simply a static image. Depending on your type of game you may use this for the game board, a table texture, or a map/illustration for your Pen&Paper game. By selecting `Load Image` in the context menu a small window will open prompting you to select an image from a list of files in the `img/` directory. If you added new images to this directory after the server was started, click `Update List` in order to find that image via the autocomplete functionality. Alternatively, you may upload your image file via drag&drop of the file onto the selection dialog. The file will then be uploaded upon the next push on this game element.

The configurable settings for this element are:
   * **Owner** - controls who has permission to drag this element
   * **Position Streaming** - toggle whether changes in the position of this element are streamed to the server
   * **Visibility** - toggle visibility for non-game master on and off
   * **Lock** - toggle whether this element can be moved
   * **Background** - toggle between white and a transparent background for this element
* **Image Label Element**
   The `Label` element can only be added to an existing `Image` element.

The configurable settings for this element are:
   * **Position and Size** - note that you can also modify the position and size of this element by holding down `Shift` + dragging with `Left Mouse Button` or turning the `Mouse Wheel`, respectively
   * **Set Text** - specify the text that will be displayed; alternatively using a double click on the `Label` as a shortcut
   * **Set Arc** - this setting controls whether the `Label` is displayed in an arc using [CircleType.js](https://circletype.labwire.ca/)
   * **Set Angle** - this option rotates the `Label` by the specified angle
   * **Set Color** - select the color of the `Label` using [jscolor](https://jscolor.com/)
* **Image Marker Element**
   The `Marker` element can only be added to an existing `Image` element. By selecting `Load Image` in the context menu a small window will open prompting you to select an image from a list of files in the `img/` directory. If you added new images to this directory after the server was started, click `Update List` in order to find that image via the autocomplete functionality. Alternatively, you may upload your image via drag&drop of the file onto the selection dialog. The file will then be uploaded upon the next push on this or its parent game element.

The configurable settings for this element are:
   * **Position and Size** - note that you can also modify the position and size of this element by holding down `Shift` + dragging with `Left Mouse Button` or turning the `Mouse Wheel`, respectively
   * **Description** - toggle whether a description window will be opened upon clicking with `Left Mouse Button`
   * **Set Marker Color** - select the `Marker`'s color from a list of colors
* **Token Element**
   The `Token` element is intended as player representation, e.g. in a regular board game or a Pen&Paper game. By selecting `Load Image` in the context menu a small window will open prompting you to select an image from a list of files in the `img/` directory. If you added new images to this directory after the server was started, click `Update List` in order to find that image via the autocomplete functionality. Alternatively, you may upload your image via drag&drop of the file onto the selection dialog. The file will then be uploaded upon the next push on this game element.

Any `Token` a player has control over is raised to the top layer making those `Tokens` always accessible.

The configurable settings for this element are:
   * **Image Section** - after loading an image you can adjust the image section shown on the token by holding down `Shift` + dragging with `Left Mouse Button` and turning the `Mouse Wheel`, respectively
   * **Owner** - controls who has permission to drag this element
   * **Position Streaming** - toggle whether changes in the position of this element are streamed to the server
   * **Visibility** - toggle visibility for non-game master on and off
   * **Description** - toggle whether a description window will be opened upon clicking with `Left Mouse Button`
   * **Set Token Size** - specify the size of the selected `Token`
   * **Reset Token Image** - this restores the default setting for the image section selection
   * **Set Color** - this option allows you to change the color of the `Token` border using [jscolor](https://jscolor.com/)
   * **Color From List** - this option allows you to quickly change the color of the `Token` border by selecting from a preset list of colors

* **Token/Marker Description**
    The description name and text of a `Token` or a `Marker` can be edited by first expanding the description. From there the description can either be edited by clicking `Edit` or loaded by clicking `Load`. The latter requires a file to be prepared in the `data/` directory in the format described in the demo-file `desctest.dat`.

In case of a `Token` description a `Random Face`-Button appears after clicking on `Edit`, which allows to load the current face from [thispersondoesnotexist.com/](https://thispersondoesnotexist.com/) as temporary image on click. This image is then stored by the server as a file on the next `Push`.

* **Canvas Element**
   The `Canvas` element based on [Fabric.js](http://fabricjs.com/) can be used in very different scenarios like an easy way to make records, quickly sketch surroundings in a Pen&Paper game, or drawing charades.

After creation double click with the `Left Mouse Button` to enter the drawing/editing mode. The menu on the right side of the screen provides the basic settings like brush type (free draw, create rectangles, or ellipsis), size, and color or enables the addition of Fabric.js-objects like `Images` or `Text` to the `Canvas`. Using the button on the bottom right or by pressing `Tab` you can toggle between `Drawing`- and `Edit`-mode. While in `Edit` mode you can select and manipulate objects previously added to the `Canvas`. This also includes a context menu for those `Canvas` objects.

The configurable settings for this element are:
   * **Owner** - controls who has permission to draw on this element
   * **Position Streaming** - toggle whether changes in the position of this element are streamed to the server
   * **Content Streaming** - toggle whether content changes of this `Canvas` are streamed to the server
   * **Visibility** - toggle visibility for non-game master on and off
   * **Transparent Background** - toggle whether the background of this canvas element is transparent
   * **Lock** - toggle whether this element can be moved
   * **Set Canvas Size** - specify the size of the selected `Canvas`

* **Card Element**
   Currently, `Card` elements can only be added by the use of the `New Deck` option in the context menu.

Upon selecting this option you are prompted with a file selection window from your browser to select a text file containing the information what `Cards` are in that deck. A demo file is located in `data/testdeck.dat` explaining the format. Every line after the first has to contain four tab-separated values each representing one card. The first two values are the current `Card`'s width and height. These values can be replaced by `-` to automatically get the length from the front image file. The third and fourth values are the relative paths to the image files on the server. If you do not need an image for the back of a card, you may enter only a `-` to indicate an empty card back (i.e. a generic logo).

`Card` elements have several additional controls/actions that can be performed (some are only available for the game master):
	* **Multi-Card Selection**: You can select multiple `Cards` at once by holding `Ctrl` while clicking with the `Left Mouse Button`. All `Cards` below your cursor at the time of the click will be added to the selection. Deselect by clicking again on another game element or the background. Actions like dragging, turning, rotating etc. are then performed on the selected stack of `Cards`.
	* **Turning Cards**: You can turn a `Card` element (or the current selection) by double clicking with the `Left Mouse Button`.
	* **Rotating Cards**: You can rotate a `Card` element (or the current selection) by turning the `Mouse Wheel` while those `Cards` are being dragged.
	* **Drawing/Discarding Cards**: By opening a context menu on a `Card` or selection of `Cards` and if the permission was given to you, you can draw `Cards` to your hand (an icon will be shown in the top left corner of the card). The `Card` will not be publicly turned but only be visible for you (or others who have drawn this `Card`/these `Cards` at the same time). The same procedure performed on a `Card` that is already on your hand will present you the option to discard that `Card` again.
	* **Turn Face Up/Down** - force all selected `Cards` to be turned face up/down
	* **Collect** - collect all selected `Cards` and position them in the same location as the `Card` for which the context menu was opened
	* **Arrange** - collect all selected `Cards` and arrange them with a small relative displacement
	* **Shuffle** - shuffle the selected stack of `Cards`
	* **Shuffle Angle** - shuffle the angle of the selected stack of `Cards`
	* **Prepare** - perform a forced discard, face down, collection, and shuffle action on the selected deck
	* **Grab Top N** - reduce the current selection of `Cards` to the top N `Cards`; N is always the last input from **Grab Top ..**
	* **Grab Top ..** - you are prompted to enter a number; reduce the current selection of `Cards` to the entered number of `Cards`

Some of the configurable settings for this element can be changed for the selected `Card`, the selected stack of `Cards`, and the entire deck of `Cards`; those options are presented in the corresponding submenus:
   * **Moving Rights** - controls who has permission to drag this element/these elements
   * **Viewing Rights** - controls who has the permission to view face down `Cards` or draw `Cards` to their hand
   * **Details**
	   * **Change Scale** - change the scale the selected `Cards` are displayed in
	   * **Border Color** - toggle between transparent and white border color
	   * **Highlight Color** - toggle between transparent and red highlight color (possibly useful for puzzles, where the orientation should not be revealed)
	   * **Drag to Top** - toggle whether `Cards` of this deck will be dragged to the top on initiation of a drag
	   * **Randomize Angles** - toggle whether the orientation of a `Card` from this deck will be randomized by a few degrees on termination of a drag
	   * **Angle Increment** - set a specific angle increment for turning `Cards` from this deck
	   * **Set Deck ID** - the layering of `Cards` from different decks of `Cards` is organized in such a way that all `Cards` from a deck with larger ID are always on top of `Cards` from decks with smaller IDs; use this setting to control what deck of `Cards` is on top of which deck
   * **Delete** - remove the selected deck from the game
* **Lottery Element**
   The `Lottery` element can have very different uses depending on the kind of game. It may serve as an indicator for who's turn it currently is, as a literal lottery enabling to pick randomly from a list of words, or even an emote by using the TTS support. Selecting `Set Options` in a `Lottery`'s context menu prompts the game master to enter a list of values separated by line breaks, commas are automatically exchanged by line breaks. The game master is also able to initialize the `Lottery` by specifying a current option inside the `Set Option` submenu. The next entry of the `Lottery` is picked by double clicking with the `Left Mouse Button` or via the `Lottery`'s context menu's option `Pick Next`.

The configurable settings for this element are:
   * **Owner** - controls who has permission to drag this element or pick next result
   * **Visibility** - controls element visibility for players and who will get `Lottery` results printed to the log
   * **Lock** - toggle whether this element can be moved
   * **Position Streaming** - toggle whether changes in the position of this element are streamed to the server
   * **Select Random** - toggle whether next pick will be random from the list of `Lottery` options
   * **Turn Indicator** - toggle whether this `Lottery` is treated as turn indicator printing changes to the log accordingly
   * **Write Log** - toggles whether `Lottery` results are printed to the log
   * **Use TTS** - toggles whether `Lottery` results are queued as TTS (text-to-speech) tofor all players (except the game master); this ignores the visibility setting

* **Timer Element**
	The `Timer` element can be used to indicate remaining time for a player's turn or to notify if a certain amount of time has passed since the `Timer` has been started. If the `Timer` is set to `autorestart`, then only the game master can stop the repeated countdown (by using the option `Stop Timer` in the context menu).

The configurable settings for this element are:
	* **Owner** - controls who has permission to drag this element or (re-)start the `Timer`
	* **Visibility** - controls element visibility for players and who can hear the sfx if enabled
	* **Position Streaming** - toggle whether changes in the position of this element are streamed to the server
	* **Lock** - toggle whether this element can be moved
	* **Set Duration** - specify the timeout duration in seconds
	* **Autorestart** - toggle whether the `Timer` will be restarted automatically after time has run out
	* **Play SFX** - toggle whether sfx will be played upon timeout
	* **Set SFX** - select the file for sfx playback
	* **Play Urgent SFX** - toggle whether urgency sfx will be played close to the timeout (maximum of 10s or 10% of total remaining)
	* **Set Urgent SFX** - select the file for urgency sfx playback
	* **Show Label** - toggle whether a digital indicator is shown on the `Timer`
	* **Link to Lottery** - use this to select a specific Lottery to be triggered on timeout; picking next in lottery causes the `Timer` to restart

* **Die Element**
   The `Die` element is the only kind of game element that all players can create. Also, this element is only visible for the local player and is not being saved when the connection is closed. This element will not be affected by repositioning of the camera or changes of the zoom. It can be rescaled by holding `Shift` while turning the `Mouse Wheel`. You can roll a `Die` by double clicking with the `Left Mouse Button` or by opening its context menu and selecting `Roll`.

The configurable settings for this element are:
   * **Set Die Color** - select the `Die`'s color from a list of colors
   * **Link to Token** - if a `Token` is in the game you have control over, you can also link this `Die` and said `Token`; linked `Dice` can be rolled from the `Token`'s context menu and the log message will state the `Token`'s name

* **Public Die Element**
   The `Public Die` element has mostly the same features as the `Die`. Differences are that the `Public Die` is visible for all players and its properties like color and size can only be controlled by the game master.

The configurable settings for the element are:
   * **Owner** - controls who has permission to drag or roll this the `Die`
   * **Lock** - toggle whether this element can be moved
   * **Set Die Color** - select the `Die`'s color from a list of colors
   * **Set-Able** - toggle whether the `Die`'s value can be set by turning the `Mouse Wheel` while hovering over the element
   * **Animation** - toggle whether rolling animation is shown after a roll is initiated

* **Soundboard Element**
	The `Soundboard` element enables the game master to set up a list of sound effects or TTS-messages that can be played by clicking a single button. The corresponding context menu option is located in the `Play Sound` submenu.

In the `Soundboard` click the `Add` button to open a menu where a new `Entry` can be configured and tested. At the top it can be selected whether a `File` or a `TTS` should be played. Below a label can be specified which will appear on the `Soundboard`. For the next input depending on the category of effect either select a sound file or enter a TTS-message. If you are setting up a TTS message, you can also configure options for the voice pitch and rate/speed. The input for a volume multiplier can also be accessed after the creation of a `Soundboard` entry. Lastly, the selection/input can be previewed. If a sound file was added after the server startup, clicking on the `Update List` button updates this file to be listed in the auto completion. Double clicking the `Soundboard` label offers the game master to change the soundboard name. The slider in every entry enables a quick adjustment of the playback volume (changes are pushed automatically).

The configurable settings for the element are:
	* **Owner** - controls who has permission to use the `Soundboard`

### Game Settings & Actions

* **Play Sound**
   The game master has multiple options to play sound from files (those need to be located in the `sound/` directory) or as text-to-speech (TTS) message for all players.
   * **Play Sound** Issues the singular playback of the selected sound file for all players.
   * **Play Looping Sound** Issues the repeated playback of the selected sound file for all players (ambient sounds/music).
   * **Stop Sound** Stop playback of all sounds currently playing for players.
   * **Queue TTS** Send a TTS message to all players.
   * **Volume** Use the slider input to adjust playback volume of sounds and the TTS system. For players this slider is available only if the key `a` is pressed while opening the context menu.
   * **Select TTS Voice** Select your preferred TTS voice/language from a list of available voices. For players this slider is available only if the key `a` is pressed while opening the context menu.

* **Game Options**
 In this submenu it is possible to add arbitrary (previously implemented) modifyers to the game. An example is the option to have `Cards` in a certain deck be dragged to the top layer of the deck on the initiation of a `Card`-drag (this is recommended for most basic card games). Suppose you want to play a game of cards where the `Card` that has been moved last should be raised to the top of the entire deck. For a deck ID of 2 a game option `d2dragtotop` has to be added to the game. For the implementation of a custom rule `<keyword>` you can simply use the condition
 ```
 if (gameoptions.includes('<keyword>')) {..}
 ```
 to test whether that rule is active. The `<keyword>` has only the requirement of containing no spaces. All changes to the list of game options are immediately forwarded to all clients.

* **Add Option**
      As described above this is an easy way to implement additional custom rules for yate that are kept track of by the server. You can add multiple options at once separated by a space.

Currently the following game options are implemented:
 * `d<deckid>dragtotop` - drag `Cards` of the deck with corresponding ID to the top on initiation of a drag (see shortcut in `Deck` → `Details`)
 * `d<deckid>randomizeangles` - have the orientation of a `Card` from the deck with corresponding ID be randomized by a few degrees on termination of a drag (see shortcut in `Deck` → `Details`)
 * `d<deckid>cardturnangleinc<intValue>` - use this option to set a specific angle increment for turning `Cards` from a specific `Deck` (see shortcut in `Deck` → `Details`)
 * `notes` - allow players to open a window where notes can be made; this can be useful for Pen&Paper games where character attributes or inventory may be noted; alternatively, the game master can use this to make player-specific notes
 * `yahtzee` - adds a 'Roll All' option the context menu of players; selecting this will perform a `Roll` on every die available
 * `disableDieSound` - disable dice roll sfx globally
 * `fontDecorative` - change the generic font to a more decorative/Fantasy-style font

* **Remove Options**
      The prompt is automatically filled with all currently set game options. You can remove multiple options at once separated by a space.

* **Show Log**
      Use this to toggle whether player (aside from game master) can see a log in the bottom right corner of their screen.

* **Set This Camera**
      Set the initial view (camera position and zoom) for newly joining clients to the current view.

* **Unset Camera**
      Revert view settings for newly joining clients back to default.

* **Set Global Token Size**
      Use this option to change the size of all `Tokens` at once.

* **Set Global Marker Size**
      Use this option to change the size of all `Markers` at once.
* **Rearrange Layering**
   The `Rearrange Layering` action goes over all present game elements and adjusts the layering of those elements to a predefined hierarchy. The order from lowest to highest layer is: `Image/Canvas` → `Card` → `Lottery` → `Token` → `Public Die`. A manual change of layering is possible by holding `Alt` and turning the `Mouse Wheel`. The changes in layering have to be pushed to become visible for players. Note that a `Token` that a player has control over will always stay on top regardless of other layering.

* **Push All**
   Loop over all game elements and perform a push to the server.

* **Force Discard All**
   Force all clients to discard all `Cards` that are currently visible due to being drawn onto their hand.

* **Copy Server Address**
   Try to copy the server's public address (ip + port) to the clipboard.

* **Save/Load**
   `Save` current state of the game to or `Load` a previous state of a game from an XML-file. On issuing a `Save` the server writes a savestate to the directory `savestates/` and offers the game master to also save this file on their machine. 'Load' requires the game master to select a suitable savestate from their local machine. Note that loading a savestate into a game where game elements exist already causes the elements from the savestate to be added to game additionally (they will not be replaced or deleted).
* **Restore All**
   Use this option to restore all game elements from the server where possible/implemented.
* **Delete All**
   Confirming this action cleans up the entire game.

## Planned Additions
Since yate is written in JavaScript you can easily implement modifications you may need for some specific kind of game.
Have a look at the notes in the section regarding [**Game Options**](#game-settings--actions) for a comment on how to do this most easily.
Feel free to ask for help on implementation of modifications, suggest features, or even provide the code that implements those features to be added to this repository.
Please refer to me via [mail](mailto:mail.yateofficial@gmail.com).

Next on the list of features/changes to be implemented:
* **Property Editor** Editor window to set up game element properties more comfortable.
* **n-die** n-sided die.
* **Chat**: Minimal text chat window.
* **Cleanup**: Due to the grown nature of yate, it is a (for now persistent) goal to clean up the code base and unify functionalities.

## Known Issues
For unstable internet connection some unexpected behavior regarding the synchronicity between server and client has been observed.

Due to the afore mentioned history regarding yate's development the code itself is rather messy.
As stated in the [Planned Additions](#planned-additions) section, the cleanup will require more time especially as it is (at the moment) low priority.

## License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

yate

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README