Use the In-Game Community Mods - Cross Platform PA Mod Manager (PAMM) is Obsolete

So... i have a steam version of PA. I installed PAMM, then installed some mods wit this, but nothing has happened and nothing changes.... maybe i doing something wrong?

Do you happen to have international characters such as äúí in your username? That's a longstanding bug in PA that causes mods not to load.

Try this link and read some of the things you can do to fix this.
the only thing i can remember when i had this issue was check my version number and make sure they matched PA for my mod manager.

https://forums.uberent.com/threads/rel-pa-mod-manager-cross-platform.59992/page-15#post-992126

Does anyone have a mirror for this?
https://github.com/pamods/pamm-atom/releases/latest

An unexpected error occurred during the mod archive extraction. TypeError:undefined is not a function.

This is what I get when trying to install any mod on linux please help a fellow planetsmasher out.

Ah, yeah. It seems to be something to do with a fresh install. My existing version of PAMM works fine on Linux, but when I remove it, reinstall and make a clean mods dir again, it gives the same error you get. Log from the command line:

Code:

[7382:1001/204535:INFO:CONSOLE(916)] "LOG: Generating Installed Mods List", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204535:INFO:CONSOLE(916)] "LOG: Generating Installed Mods List", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204535:INFO:CONSOLE(916)] "LOG: Generating Available Mods List", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204541:INFO:CONSOLE(916)] "LOG: Available Mods context filter client applied", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204553:INFO:CONSOLE(916)] "LOG: Installing mod 'com.pa.DeathByDenim.dFavouriteColour'", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204553:INFO:CONSOLE(916)] "LOG: Downloading mod 'com.pa.DeathByDenim.dFavouriteColour'", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204553:INFO:CONSOLE(916)] "LOG: [Message ID: 6] GET <code class='log_url'>https://github.com/DeathByDenim/dFavouriteColour/archive/v1.4.2.zip</code>", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204554:ERROR:nss_ocsp.cc(617)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[7382:1001/204554:ERROR:nss_ocsp.cc(617)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[7382:1001/204554:ERROR:nss_ocsp.cc(617)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[7382:1001/204554:ERROR:nss_ocsp.cc(617)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[7382:1001/204554:ERROR:nss_ocsp.cc(617)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[7382:1001/204554:ERROR:nss_ocsp.cc(617)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[7382:1001/204557:INFO:CONSOLE(916)] "LOG: [Message ID: 6] HTTP 200", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204557:INFO:CONSOLE(916)] "LOG: Writing client mods.json", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204557:INFO:CONSOLE(916)] "LOG: Writing ui_mod_list.js", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204557:INFO:CONSOLE(916)] "LOG: Writing mods_list.json", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)
[7382:1001/204557:INFO:CONSOLE(916)] "LOG: Writing server mods.json", source: file:///home/jarno/.local/pamm/resources/app/assets/js/pamm.js (916)

So how do we fix it?

Now we wait for @Mereth's time zone to come around.
Knowing how to reproduce it is half the battle.

I'll try to have a look on this tonight, could be an atomshell issue which could explain why new install only are concerned.

My hunch was good, it's an Atom Shell issue, updating it to the latest version break the install process on Windows too. I hope I can fix it on the pamm side.

Nice. I broke my pamm while diagnosing this, so I hope you can fix it soon.

Ok, it's now fixed! I had the same error on PAMM Server lately
Sadly, the auto update is broken too, because the problem was in the uncompress method, so you have to reinstall it again, sorry for that.

Alerting @raevn at the same time, because PAHub may be affected too if he used my crappy code as sample to uncompress zip files.

MSVCP100.dll missing to install pamm
Windows 10 preview x64

lol

http://www.microsoft.com/en-us/download/details.aspx?id=5555

No plan to add this to the installer.

i know^^ but im telling because maybe someting needs to be changed
or it works with the release version

Not yet implemented, thanks for the heads up though

Some more information about how the install -> activate/use mods process works would be very helpful, especially for newer users. I just clicked "install" on a mod but I have *no* idea if it is enabled automatically in the game or if I have to do anything else... Quite confusing to be honest.

*Edit: I mean during the first few installations a user does.. perhaps a short tutorial of some sort.

Installing a mod automatically enables it.

When you see a mod in one of the installed mods tabs there will be a circle next to it. If it is solid blue it is enabled. If it is hollow outline then it is disabled. Clicking toggles enabling/disabling. Disabling a prerequisite mod disables all mods that require the mod.

PAMM v1.0.0 is out !

I can hear the crowd roars : WHATS NEW WHATS NEW !

Well not so much :

• cyclic dependencies can now be made without crashing PAMM
• removed the "GAMMA" from the image title
• mods can now be enabled/disabled/uninstalled from the available mod list (from a previous minor version but not advertised)
• PAMM will now tell you about NON ASCII character in your user path (maybe Uber will fix this sooner than later ...) (from a previous minor version but not advertised)

So why 1.0.0 ? Because this version is pretty much stable, and, I don't expect any major feature implemented in a near future. As you know, PAHub is coming, and the mods management will be part of the core plugins, so I don't feel making any more efforts, except bugs fixes, in PAMM. After PAHub release, I'll take a look and see if some "fun to be made" plugins ... have to be made, and I already have some idea

tldr: PAMM is in maintenance mode