Here are some issues experienced by users.
- You can reset the lake projects involved (i.e. the
server/
folder here as well as your game's folder) with the following commands:If you experience problems related to Lean or lake, you should first try to reset it this way.cd [THE PROJECT] rm -rf .lake/ lake update -R lake build
- If you don't get the pop-up, you might have disabled them, and you can reenable it by
running the
remote-containers.showReopenInContainerNotificationReset
command in vscode. - If the starting the container fails, in particular with a message
Error: network xyz not found
, you might have deleted stuff from docker via your shell. Try deleting the container and image explicitly in VSCode (left side, "Docker" icon). Then reopen vscode and let it rebuild the container. (this will again take some time) - On a working dev container setup, http://localhost:3000 should directly redirect you to http://localhost:3000/#/g/local/game, try if the latter is accessible.
Here are known issues/pitfalls with the local setup using npm
.
- If
CDPATH
is set on your mac/linux system, it might provide issues withnpm start
resulting in a server crash or blank screen. In particularnpm start
will displayAs a fix you might need to delete your manually set[server] sh: line 0: cd: server: No such file or directory [server] npm run start_server exited with code 1
CDPATH
environment variable.
Errors concerning uploads to the server.
- Your game overview loads but the server crashes on loading a level: Check your game's github action is identical to the GameSkeleton's, in particular that there is a step about building the "
gameserver
-executable".