I have a question regarding updating Pico-8 to newer versions. Do I need to do something specific? I usually just drag and drop the new version but it doesnt seem to work. I still get the error saying there is a version update on some Pico-8 games.
For newer versions, potentially you will need to update the list of expected file names, along with the MD5 hash.
Of course, you can always just be cheeky, and rename the new updates pico-8 to one of the previous older file names, and choose to ignore the MD5 hash check.
Either that, or potentially you may need to remove the old versions and then reload the launcher, do allow the conditions for the installer to run be met.
Also, try doing a dry run with nothing in the pico-8 directory and deliberately trigger an error, and then install it as lee normal.
Hopefully this works out!
How would I update the list of file names and the MD5 check? I was renaming newer versions to an older one because the new version wouldnt correctly install on the DEOT software without renaming. I did try to put the newest version on by renaming but it didnt fix it. Hope you have been doing well!
Have a peek in:
~/launcher/Menu/GameShell/50_PICO-8/compkginfo.json
I updated mine recently to look like this.
{
"GameDir":"/home/cpi/games/PICO-8/",
"InstallDir":"pico-8",
"NotFoundMsg":["Please purchase the PICO-8 \n|None|varela16",
"and copy it to the \"~/games/PICO-8\"|None|varela16"],
"MD5":{"pico-8_0.1.11g_raspi.zip":"a3f2995cf117499f880bd964d6a0e1f2",
"pico-8_0.1.11g_amd64.zip":"6726141c784afd4a41be6b7414c1b932",
"pico-8_0.1.12_raspi.zip":"08eda95570e63089a2b9f5531503431e",
"pico-8_0.1.12c_raspi.zip":"1a62b0d7d4e4be65f89f23ec9757cb66",
"pico-8_0.1.12c2_raspi.zip":"7a878795472fa39304e9a10128c1f712",
"pico-8_0.2.0e_raspi.zip":"085edfecd111c2b195b878b2197afe7a",
"pico-8_0.2.0i_raspi.zip":"be0c708d707fa967c77455512bd456c7",
"pico-8_0.2.1b_raspi.zip":"d72968c56b4de8bc3dda84a6d5b6270e",
"pico-8.zip":"whatever it takes"},
"Post-Up":"bash Post-Up.sh"
}
(I just edited it to be current as of 28/7/2020)
I’m not sure what the current version is, but hey! If could be this one, saving you some time.
If not, just add another line using the same kind of formatting.
And ahh. I’ve been trying to balance as much social time as possible, making up for a lot of lost social ground. That and binge playing/revisiting games. Just finished xenoblade, the last of us 2, nino kuni, hyrule warriors, skyward sword. Currently maxing out Persona 5 Royal, and playing through paper Mario. Next is Ghost of Tsushima.
Needless to say, I haven’t been on here in a while. Life just took me by the scruff of my neck. But hey! Thanks for asking! Hope you are going well yourself!
Thank you for the help as always! I am going to try to fix my issue! Good to hear you have been doing well! I just finished a playthrough of Gex Enter the Gecko! I havent played a Persona game yet but I am interested! I have been doing well, just working and trying to stay healthy!
a simpler way is rename any newer pico8 package to be pico-8.zip
then ignore the hash error dialog to install/update
Thank you for the help! One more question, does anyone know of a way to easily transfer games when updating? Im trying to save my favorites list, the search function doesn’t work too well and I dislike searching for my favorite games again when I update.
I am on the latest deot version, I cant seem to update to the latest pico-8 (pico-8_0.2.3_raspi). It does not update and pico-8 launches with the current installed one 0.2.2c. I tried to empty the pico-8 folder. But it returns directly to deot menu after launching.
Have you tried deleting the original pico-8 folder and then reinstalling?
Try deleting all the old Pico8 files, then restarting. You should get promoted to run the installation process again, after putting the compressed file in.
If I can remember (it’s been a while!) you should be able to remove the version number from the file, which will mean that you can pretty much install any version without it being on the white list.
The button used to accept or decline the installation was possibly also set to Xbox BAYX mode and not SNES ABXY; even if you change the mode in config. That could also be a problem, prematurely ending the installation.