art of portfiend

reblog blog: @huckleton personal blog: @sapari

my other works

my personal website, portfiend.quest

my sheezy art, sheezy.art/vyn

give me money

Comradery (recurring)

kofi (one-time)

source of "oc optics" meme: @ neo-kajatrash

space station 14 characters from the last round i've played.

yesterday i got to attend a rave event in a Space Station 14 server with my character glenn and he handed out snacks and drinks (and drugs) for like 4 hours

made a game where you get killed by circles to teach myself godot. you have to eat the smaller circles

Is there any way you could make some sort of tutorial on some of the related steps after initial setup of the template? Even just screenshots of how the files might look on Neocities could help for troubleshooting, or links to any similar setup tutorials (though I've followed a few so far that haven't really solved my issues...)

I'm not new to programming but am new to Eleventy, so I feel a little silly asking about it. Please ignore this ask if it's not possible for any reason :) Thank you!

sure thing! when you run "npm run build", it should create a "build" folder with the final files for your comic site. the contents of the "build" folder should effectively be 1-to-1 with the file structure of your neocities website, unless you add other files to your neocities site outside of the comic template.

for this example i'm starting fresh, by:

downloading the git repository for the comic template,

installing dependencies with npm install,

building everything with npm run build.

i didn't change anything else about my setup, so the files are unedited.

if i throw a local server up, it looks something like this, alongside the file list:

if i go to the actual neocities file list, you'll notice the folder structure is the same:

including the folders that just have an html file in them:

when you push the website to neocities, you should only push the contents of the "build" folder, and nothing else. don't put it in a subdirectory, think of the build folder itself as the "root".

Hey man.. come to Abnormality. We Have the stuff.

I also designed the exterior of this booth come check it out.

EVENT LOCATION: Abnormality (121, 127, 17)

again i TOTALLY understand if this is just my problem to figure out but I cant find helpful info elsewhere...

i'm assuming you're on windows!

so, windows has an "environment variable" called PATH. an environment variable is basically just a value that can be used by any program that can see it. your command line uses PATH to look for executable files that it can run as commands

so for example, imagine you have an executable (.exe) file at, say: -> C:/FileMaker/filemaker.exe in this case, if you add "C:/FileMaker/" to your PATH, then you can go in your command line and type "filemaker", and it would run filemaker.exe.

i'm assuming you're trying to run npm in your command line. however, if there is no npm.exe in your PATH, and you try to run npm i, then it'll give you "not recognized as an internal/external command".

this means one of the following:

npm is not installed. it can be installed bundled with node.js at the node.js website, or through nvm (or nvm-windows). when you install it with node.js, make sure "add to PATH" is enabled!

2. npm IS installed, but it is not in your PATH. this is weird and i'm not sure why it would happen, but if you can find npm.exe, this is quite easily remedied.

search for system "environment variables" in your computer. i use win10; for win10, there is a button called "Environment variables..." that opens a second window. then you find Path and then double click that, which opens a third window, then you wanna add the folder path to the end of the list

in case it helps and you need to track down npm.exe manually, i have two npm.exe files at these places, which might match your setup:

C:/Program Files/nodejs/npm.exe C:/Users/[user]/AppData/Roaming/npm/npm.exe

3. npm IS installed and it IS in your path, but your command line cannot see the environment variables. the primary reason for this would be that you did not restart the command line after installing node and/or updating the environment variables; go ahead and do that if you haven't. the secondary reason for this would be you're using a command line in something else (like vs code), and for some reason in that situation updating the environment variables can be very finnicky. try using your system's command line instead.

worst case scenario, you can also replace "npm" in your command line with the full path to npm. like: "C:/Program Files/nodejs/npm.exe i". this would work!

my friends and i spent two weeks putting together a Second Life in-world location for SCRIMBLO WORLD at River Center Mall where you can hang out and look at our stuff. go check it out!

there's also a scavenger hunt where you can find a bunch of prizes made by different contributors to the mall. we have two capsules to find, one of which contains a full avatar!

(SCRIMBLO WORLD is the name of our creative group where we make modifiable avatars and mods for cartoony/alternative body styles, toys, and other such things.)