Relive the historical mass terrestrial exodus of the 21st century and take the first wandering steps into the boundless frontier that we now call home. Recommended for entities human-age-equivalent-rating 12 and up.
I've run into a few weird path variable quirks myself. this video is a pretty good basic walkthrough. Sometimes it will fail to work after being added to the path because of spaces or missing semi-colons elsewhere in the path variable.
worst-case, you can always run npm by specifying the exact location of it on your machine...
There are other reports of this bug in the node installer joyent/node#4356
I just outlined 5 different approaches to v2 I've been thinking about on the wiki. I'd love to hear thoughts on them, maybe even put it to a vote on which dev plan we think is best.
So, @yayhappyface, if you don't know where the PATH is: Go to Start, in the search bar, type
Environment. It should show you something like Edit the system environment variables. In theSystem Properties window, in the Advanced tab, there should be a button at the bottom called Environment Variables. Click that. The image above shows you an example of what it should look like when you add the path that NodeJS was installed in
Make sure you obviously change it from
C:\Program Files\NodeJS to where you actually installed it
The Path variable you should be editing is this one
npm ERR! windows_NT 6.1.6701
those are the first 2
there are 13 altogether
The most likely is maybe that you aren't in the project directory with the package.json
You'll need to use the cd command to move into the-Oregon-trajectory directory in the cmd prompt.
The dir command lists things in your current working directory and may also be useful.
@yayhappyface , did you ever get npm to install for you? Getting set up on windows is quite a task on it's own.
Goooood Morning! So I've put some incredibly minor issues up on the github, let me know if you need anymore information or videos/images for them and I can grab them for you. So far everything else I noticed (such as mute button issues) have all been found! I'll add more when I find more, but so far it's looking good. I've tried it out on different browsers, different resolutions nothing seems to mess up yet!
Contrary to most places, if you uncover an issue and see it already exists in the tracker please do post a '+1' or 'me too'. It helps me to see which bugs are most irksome when I'm triage-ing.
deal with it a lot in startup-landia
basically they're not an educational game and it's pretty different from what I played in the demo
(from oregon trajectory, I mean)
are you worried they'll come after you or something? Because they probably can't, since this project predates theirs. And there are literally a million oregon trail style games out there ^^
I'm not worried at all, no.
I can audit it, make notes on GUI, game elements, etc
but it's honestly a really good base
and we're not constrained by the nasa competition rules anymore
Once we get that done I think we'll have a pretty easy time building up a community which will help guide our future decisions.