SZ_GetSpace overflow in Paintball 2

Ha! I did it by cheating: finding an existing sound mod for Portal and examining it :D. Here's how, for posterity:

Apparently, the Source engine does not look for sounds in the directory. It looks for script files instead. Those script files define where to look for stuff.

So I did the following:

• Opened the main Portal GCF (that's portal content.gcf) file with GCFScape;
• Extracted GLaDOS's voice script file (that's scripts\npc_sounds_aperture_ai.txt) to the directory where the game engine will look at, which, according to the Valve wiki, is the one where GameInfo.txt is in. So STEAMAPPS\millenomi\portal\portal, so that I have STEAMAPPS\millenomi\portal\portal\scripts\npc_sounds_aperture_ai.txt

Now Portal will look relative to the scripts file for sounds! …not. Apparently, if the file has the same name it's still looked for using the same search path that led Source to pick up the original file instead. Sigh. So, instead, noticing the working mod had file names that were different from the ones in the archive, I changed the script and the filename to a name that wasn't used anywhere else in the game (vo/aperture_ai/00_part1_entry-1__MODIFIED.wav). And BAM!, it worked. :D

If you are using the latest vanilla launcher:

1. Create or edit a profile
2. Check the box labeled "Game Directory" and fill in a location to put it. It will automatically create the directory if it doesn't exist on next launch of the profile. (Note that I doubt it will expand shell variables, but it works just fine with symbolic links if you use those)
3. Click Save Profile

What I have done for this is I have created a directory under my $HOME called .minecraftProfiles and I put each separate profile in its own subdirectory. For example, vanilla 1.7.4 I have put at homedir/.minecraftProfiles/1.7.4-vanilla.

Sharing data between profiles:

• If and when I want to share a file and keep it shared (for better or for worse) I would symlink to it from one profile in the other(s).
• If I want to use some data (saves and such) as a basis for a new profile, I first copy the directory to a new one, create the new profile in the launcher (click "New Profile" when the one I'm copying is the selected profile), and after starting up that profile, (if necessary) do manual editing of the $HOME/.minecraft/versions/profilename/profilename.json when it is needed to have it actually keep some necessary data (if same version of Minecraft and wanting to keep Forge, for example)

Tips to avoid issues with losing valuable data:

• Keep multiple profiles in separate directories to avoid conflicting mods or mod configurations.
• Each profile should have a specific version set for the "Use version" under "Version Selection" in the Profile Editor to prevent it automatically updating and preventing you from playing on servers that haven't updated.
• Backup, backup, backup - before adding/removing mods, changing the version of a profile, and especially regular backups just in case your computer (or just Minecraft) crashes.

If you are not using the vanilla launcher (read: FTB / Technic launchers), all I can say with 100% reliability is you would have to either use a separate user account (for Linux, which you should be for different people anyways according to many Linux security specialists) or deal with moving the storage location of those launchers manually each time before starting.

(partially off topic) I choose to use a naming scheme of version-info for the naming of my profiles' directories, but you can opt for adding the user's name at the beginning of it.