3 months ago1 point(+0/-0/+1Score on mirror)1 child
Look I might be retarded, how am I actually supposed to install this? the .zip I can pull off github doesn't have anything I can run and the install.md doesn't outright explain the process.
-Automatic (Windows) pulls down the tranny version since that's what's on the Windows package registry
-Manual doesn't explain shit, the standalone is supposed to have.exe's (which this doesn't) and it says for the "installer version" you need to "unzip the installer application" (what the fuck is that? again, no .exe's, what am I supposed to be running?)
If you've downloaded the .zip file on GitHub by opening `<> Code` and clicking `Download ZIP`, then it will only contain the source code itself which doesn't contain the .exe. To download the application containing the .exe file, you'll need to head over to the Releases page (https://github.com/Thumos96/VPKEdit/releases/latest) and download either the standalone version (VPKEdit-Windows-Standalone-msvc-Release.zip
) or the installer version (VPKEdit-Windows-Installer-msvc-Release.zip
).
Additionally, the `winget install vpkedit` command is only able to install VPKEdit from the main repository because my fork isn't in the Windows Package Manager. In order for the application to be added to the Windows Package Manager, I'll have to see if my fork is able to make it through the validation process before I'm allowed to change the `winget` command. In the meantime, I removed the command so users can avoid downloading the application from the wrong repository.
As for the INSTALL.md file, I forgot to modify the links that take you to the Releases page. Because of this, I edited the file so the links will redirect you to my fork of the repository.
3 months ago1 point(+0/-0/+1Score on mirror)1 child
Hi! I'm unsure how to contact you since you have your issues tab closed off (for obvious reasons), but I have a suggestion for a better looking icon: https://pomf2.lain.la/f/lumzsns.png
I've simply changed the design to be based off the Win 7 folder, and gave it HEV colors to make it look more recognizable (instead of the orange on yellow that makes the Lambda symbol barely visible).
I apologize for the late reply as I normally don't check this website very often. I like the idea you've provided for making the icon more distinct, and I decided to edit the current icon to make the colors look like the Half-Life 2 logo.
I definitely agree, though I'm not sure if it's even possible to change the icon of the .exe file itself. In the meantime, I could replace the patriotic icon for the debug version with the inverted icon once the main fork is properly able to build the artifacts for the Windows version. Of course, since the main repository is still using the trans icon, I'll leave the patriotic icon in the source code as an easter egg.
-Automatic (Windows) pulls down the tranny version since that's what's on the Windows package registry
-Manual doesn't explain shit, the standalone is supposed to have.exe's (which this doesn't) and it says for the "installer version" you need to "unzip the installer application" (what the fuck is that? again, no .exe's, what am I supposed to be running?)
) or the installer version (VPKEdit-Windows-Installer-msvc-Release.zip
).
Additionally, the `winget install vpkedit` command is only able to install VPKEdit from the main repository because my fork isn't in the Windows Package Manager. In order for the application to be added to the Windows Package Manager, I'll have to see if my fork is able to make it through the validation process before I'm allowed to change the `winget` command. In the meantime, I removed the command so users can avoid downloading the application from the wrong repository.
As for the INSTALL.md file, I forgot to modify the links that take you to the Releases page. Because of this, I edited the file so the links will redirect you to my fork of the repository.