When setting the name, in rare cases, Jitsi was not initialized yet and setting the name would cause a JS error.
We are now waiting for Jitsi to be properly initialized before setting the name.
This change makes sure the character of the current player is fully loaded before we display the game scene.
Otherwise, you could have a glitch for 0.5-2 seconds between the GameScene being displayed and the actual character being displayed.
* wip
* wip
* random action on click
* removing actions
* register single key per command use
* change removeActionsMenu action name
* fixed actions menu not hiding content properly:
* actions menu fix
* added mock Block Player action
* ActionsMenu buttons styling
* added displaying priority for menu actions
* moved utils actionMenu features to the UI
* import as a type:
* more object oriented style for API
* removed registered actions from RemotePlayer instance
* readme update
* Fixing typos / Improving wording
* added instructions on AlterActionsMenu test map
Co-authored-by: Hanusiak Piotr <piotr@ltmp.co>
Co-authored-by: David Négrier <d.negrier@thecodingmachine.com>
* apply textures on openid login, fix pusher errors on woka list
* remove logging
* Returning a HTTP 400 id roomUrl parameter not set
Co-authored-by: David Négrier <d.negrier@thecodingmachine.com>
* Wrap websockets with HyperExpress
* Add endpoints on pusher to resolve wokas
* getting textures urls from pusher
* Adding OpenAPI documentation for the pusher.
The pusher now exposes a "/openapi" endpoint and a "/swagger-ui/" endpoint.
* revert FRONT_URL
* playerTextures metadata is being loaded via Phaser.Loader
* fetch textures every time character or customize scene is open
* Heavy changes: refactoring the pusher to always send the textures (and the front to accept them)
* Sending character layer details to admin
* Cleaning commented code
* Fixing regex
* Fix woka endpoints on pusher
* Change error wording on pusher
* Working on integration of the woka-list with the new admin endpoint.
* Switching from "name" to "id" in texture object + using zod for woka/list validation
* Add position on default woka data
* Remove async on pusher option method
* Fix woka list url
* add options for /register
* Fxiing loading the Woka list
* Actually returning something in logout-callback
* Copying messages to back too
* remove customize button if no body parts are available (#1952)
* remove customize button if no body parts are available
* remove unused position field from PlayerTexturesCollection interface
* removed unused label field
* fix LocalUser test
* little PlayerTextures class refactor
* Fixing linting
* Fixing missing Openapi packages in prod
* Fixing back build
Co-authored-by: Hanusiak Piotr <piotr@ltmp.co>
Co-authored-by: David Négrier <d.negrier@thecodingmachine.com>
* Add returns on pusher endpoints
Co-authored-by: Alexis Faizeau <a.faizeau@workadventu.re>
Co-authored-by: Hanusiak Piotr <piotr@ltmp.co>
Co-authored-by: Piotr Hanusiak <wacneg@gmail.com>
* remove customize button if no body parts are available
* remove unused position field from PlayerTexturesCollection interface
* removed unused label field
* fix LocalUser test
* little PlayerTextures class refactor
* Fixing linting
* Fixing missing Openapi packages in prod
* Fixing back build
Co-authored-by: Hanusiak Piotr <piotr@ltmp.co>
Co-authored-by: David Négrier <d.negrier@thecodingmachine.com>
* async call for recalculating tiles costs
* fixed setWalkingCostGrid still being a blocking process
* set exits tiles cost from the start
* removed typing error from code
Co-authored-by: Hanusiak Piotr <piotr@ltmp.co>
* base front production image on official nginx
* build multi-platform docker images
* build message types outside docker
* set docker build context to path
* build message types before running e2e tests
* add build for arm/v7
* remove build for arm/v7
* increase yarn network timeout
* set front port to 80
* add git labels to images
https://github.com/docker/build-push-action/blob/master/UPGRADE.md#tags-with-ref-and-git-labels
* add images input
* Adding back commented code in the Dockerfile (the protobuf message building).
This way, when node-grpc supports ARM64, we can uncomment the code again.
Co-authored-by: David Négrier <d.negrier@thecodingmachine.com>
Co-authored-by: Lukas Hass @lukashass
The docker-compose build used in E2E tests was running builds sequentially.
This is an attempt to run the builds in parallel to optimize the E2E startup time.
Before this commit, the "Start WorkAdventure" step takes 7m11 on GitHub
