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

Link to Bug tracker. It's most definitely a bug in PA, since the log files aren't written either. Weirdly enough, it does create the folder in the correct position though, so there seem to be multiple routines for accessing that data.

@Dusanak: You're settings and username were saved correctly in PA, right?

Yep both username and settings are saved correctly.

From https://forums.uberent.com/threads/beta-mod-changes.51520/:

So that's probably why this is happening. The system call will just be returning a string that PA doesn't know how to handle, while actually using the environment variable should get the correct file. It's also probably why PAMM can work with those files but PA can't.

Darn those English with their ASCII mindset.

It seems the SHGetKnownFolderPath function does read %LOCALAPPDATA% judging from MSDN. It's a bit unclear though.

Anyway, *if* it does, then I wonder if Dusanak could create a batch file containing

Code:

LOCALAPPDATA=C:\PAsettings
C:\Program Files\...something...\PA.exe

Where he would have to create the directory C:\PAsettings first of course. It seems batch files need to have the .cmd extension, so you would need to save it as pa.cmd or something. Does that automatically make those files executable? Who has Windows and want to be a guinea pig?

Sounds like a great way to break every other program that relies on it.

That's why it's in a batch script, so it only changes for PA, right?

That's why I need to read posts more carefully before I reply.

Didn't work. The script I used was

Code:

set LOCALAPPDATA=C:\PAsettings
"C:\Program Files (x86)\Planetary Annihilation\PA\PA.exe"

But it still just pulled data from my original folder.

Hey, could someone help me with this?

Whenever i try to open the mod manager, or the PAMM.hta file directly, it says that "PAMM.hta is not a valid Win32 application". While looking through this thread, i did manage to find someone who had a similar problem

Any he also apparently found a solution

With the problem being i don't really understand computers, and so have no idea what that means. Or more importantly, how to do it. Could someone explain?

File association means what program the operating system uses to open the file. For example, .txt files typically have a file association with notepad.

To change this for PAMM, right click on PAMM.hta and select "Open With" > "Choose Default Program". A box should come up, and ensure "Microsoft (R) HTML Application Host" is selected. If it's not in the list, click Browse and go to the C:\Windows\SysWOW64 folder (if running 64 bit windows, otherwise try System32 instead of SysWOW64), then select mshta.exe

Thanks, its working now

Looks like I'm having the same problem ( user folder name contains an "é"). Should I add something on the bugtracker entry that's already been made?

You should at least upvote it and probably leave a short comment.

Actually, doesn't Windows have some equivalent of sudo, "Run as User ..." or something?
Like this:
http://www.sevenforums.com/tutorials/419-run-different-user.html

That could be a workaround, right?

This actually works! ( when using a second/guest account. In fact the guest account is enough)

Only downside is that both PAMM and the PA launcher don't work in this manner unless I actually log into my guest account. Still, all I have to do is update PA with my regular account, check in on my guest account to update the PAMM once in a while and when I want to play simply launch PA directly with a slightly modified shortcut:

runas /user:guest "C:\Program Files (x86)\Planetary Annihilation\PA\PA.exe"

When you install something from the Available Mods list the install button isn't changing to reinstall until you refresh the list. I'm sure it used to. Likewise, even with the Not Install filter applied the mod won't disappear until you refresh.

I second this - I was having to resort to restarting the program after every change the yesterday b\c of this and my refresh was taking forever. I wasn't annoyed just thought I'd let you know I had the same occurrence.

The first one did use to change to reinstall straight away. Not sure when that stopped happening, but it's a bug.
I'll look into the second issue, too.