Open GhostieKoto opened 1 year ago
@GhostieKoto please can you provide some instructions for how to reproduce this? What steps to you take to "download"? Are you perhaps using your browser to save the page as a file locally (with right-click, 'save as...')? I don't see any mention of "download" in the README for this repository.
@GhostieKoto please can you provide some instructions for how to reproduce this? What steps to you take to "download"? Are you perhaps using your browser to save the page as a file locally (with right-click, 'save as...')? I don't see any mention of "download" in the README for this repository.
I clicked code, downloaded the files as a zip, and launched index.html.
I think I also tried extracting all before launching index.html
@GhostieKoto please can you provide some instructions for how to reproduce this? What steps to you take to "download"? Are you perhaps using your browser to save the page as a file locally (with right-click, 'save as...')? I don't see any mention of "download" in the README for this repository.
The school blocked all deployments. Which is super fricking annoying as I'm in a game development class. :/
So no GitHub.io, no vercel.app, no repl.co, etc
I've been able to run the game locally from a checkout of the repository by running a simple web server with: python3 -m http.server
. I've not attempted to run it from a file:
scheme.
Well, are you able to fix it so it can run as a file?
It would mean a lot to me
This seems to be a limitation imposed by the browser, not a bug in this game. See https://github.com/whatwg/html/issues/8121
@GhostieKoto - three things.
file:///
and 127.0.0.1
) than with other sources, because if you're tricky about things, you can get access to things on disk using relative pathsfile:///
url. The game is built from relative URLs, meaning it loads all its assets from wherever the base was loaded. This means it's trying to load the scripts from file:///
. That's a no-no.127.0.0.1
or localhost
, the normal names for your own computer, because they'll end up with the same issuehosts
file to point some name you pull from thin air to point somewhere
http://evolve/
or http://evo.lve/
, so that it can never collide with a real address. Plus it's fun127.0.0.1 evo.lve # loopback for evolve for cors
apache
or whatever, but that's a hassle, and since this webserver can be flimsy, it's probably easier to do something elsenode
or python
, and then install a development webserver from their package manager
npm install -g servehere
servehere -p 9123 -c
simplewebserver
, which someone else wrote for situations like this
*SUPER IMPORTANT!*
on your issues in the future. If I saw an issue like this on one of my repos, this would go to the very, very back of the queue, over this behavior.
This game doesn't load AT ALL when downloaded. You need to figure out why and fix it, please.