Skip to main content
Advanced Search
Search Terms
Content Type

Exact Matches
Tag Searches
Date Options
Updated after
Updated before
Created after
Created before

Search Results

103 total results found

The Fall of the House of Usher

Maps

Original Story The narrator approaches the gloomy house of usher on horseback. The sight fills him with dread, even more so when he sees its reflection in the tarn by the house. The narrator was summoned by the lord of the house and boyhood friend, Roderick U...

Basic Concepts - Authority and RPC

Technical Multiplayer

By default, everything in RadGame has the Server as authority. The only (so far) Exception is the player_input script that is part of each player character - the client that's controlling the character has the multiplayer authority over his input script. Move...

Spell Queue

Technical Spells

In order to make spell casting smoother, and not have short gaps between spells when the next is not triggered frame-perfectly, a spell queuing system exists. This system allows spells to be queued towards the end of a currently active cast, or a currently act...

First Playable Alpha

Milestones

The first playable alpha should consist of a functioning hub map, the first playable map (The Fall of the House of Usher), and at least one class per role that can be played. A more detailed list of features is as follows: A list of required features(cheese...

Setup

Service Overview meet.shiny.space - Jitsi

Jitsi can be ran in docker/podman containers. currently it runs on brix4, with an external STUN/TURN server at vps.shiny.space for clients with NAT issues or strict firewalls. The basic setup is described in the docs: https://jitsi.github.io/handbook/docs/dev...

Jitsi compose.yml

Service Overview meet.shiny.space - Jitsi

version: '3.5' services: # Frontend web: image: jitsi/web:${JITSI_IMAGE_VERSION:-stable-9753} restart: ${RESTART_POLICY:-unless-stopped} ports: - '${HTTP_PORT}:80' - '${HTTPS_PORT}:443' ...

nginx reverse proxy configuration

Service Overview meet.shiny.space - Jitsi

/etc/nginx/sites-available/meet.shiny.space (why debian?? we don't need sites-available for nginx... switch to alpine sometime) server { listen 443 ssl; server_name meet.shiny.space; client_max_body_size 500M; location /.well-known { root /var/w...

Config - ENV and interface customization

Service Overview meet.shiny.space - Jitsi

Most important is the ENV file - here's the currently set variables. if jitsi sees some usage, we'll add the optional services too. # config location changed to keep everything in one directory CONFIG=~/jitsi/.jitsi-meet-cfg # Exposed HTTP port (will redi...

STUN / TURN server

Service Overview meet.shiny.space - Jitsi

Some networks have complicated NAT in front of them which can make it a little difficult to open direct connections using Websockets (like jitsi does) or similar methods between two devices. Also, some firewalls can be very strict about what connections they a...

Short Overview

Service Overview

Short list that is hopefully easy to update. Running on shiny.space itself: Public services: forge.shiny.space - git repos, forgejo webui, including git lfs (currently no signups, but public repos possible)meet.shiny.space - voice/video call with jitsi meet ...

Network setup

DNS

Network setup

Basic setup: run our own DNS server. since it's basically required to run 2, run the master authoritative dns server in the homelab, and have a "slave" on the VPS that's constantly kept in sync. Note: since we want to use these DNS servers for ALL our domains...

New Page

Network setup DNS