metastruct / metastruct.net

Website for the Meta Construct community

metastruct.net

New website for the Meta Construct community

Build Setup

# install dependencies
$ yarn install

# serve with hot reload at localhost:3000
$ yarn run dev

# build for production and launch server
$ yarn run build
$ yarn start

# generate static project
$ yarn run generate

For detailed explanation on how things work, checkout Nuxt.js docs.

metastruct.net's Issues

Pixel Game

I heard @WicopeeDot made the back-end for the pixel game a standalone Node.js server. If that's the case we could have a page where once logged in with steam; users could add pixels to the pixel game just like in-game.

Automating referenced addons

Here's the idea, we make the server post the add-ons inside https://gitlab.com/metastruct/srvaddons/blob/master/metastruct_specific/lua/autorun/automount_addons.lua upon server restart to the website API, so its always updated. For the description of these we could maybe just get the description from the related workshop page (scrapping?).

We could do the same for caddons (https://gitlab.com/metastruct/srvaddons/blob/master/ClientsideAddons/lua/autorun/sh_caddons.lua) supposing that the URL field becomes optional and we wouldn't have to do scrapping this time because these already have a description.

Furthermore since currently add-ons on the website do not have a way to differentiate each others I propose the following solution:

Have a string that for workshop add-ons will be the workshop id and for external add-ons, just a arbitrary string (a name whatsoever). This allows us to update existing add-ons instead of adding new ones every time we are posting to the API.