fs_basegame behavior with mods errors with Couldn't load default.cfg about quake3e HOT 8 OPEN

I'd rather add support for multiple (space-separated) values in fs_basegame or something like that

from quake3e.

fs_basegame missionpack implies you are not having baseq3 anymore. And missionpack does not ship a default.cfg

EDIT: Looks like this is sort of a regression in behavior but I think it was done on purpose, however @ec- can maybe comment better why it was done. IIRC fs_basegame behavior was created originally in the vanilla game to allow you to base mods off of others while still also loading fs_game baseq3 too. But this no longer is the case here.

from quake3e.

Would you prefer restoring behavior or maybe an extra cvar like fs_extragame or something?

from quake3e.

@ensiform If you're not using Quake3e without baseq3 (a standalone build) wouldn't you be changing the base path on compile anyway? In that context fs_basegame would seem to serve no purpose.

@ec- So, something like "+set fs_basegame baseq3 missionpack +set fs_game modname", with the argument sequence for fs_basegame determining load priority?

from quake3e.

It would be useful still for example with baseoa or something standalone. But IMHO how many mods do you really want to.

The basepath may still differ but you can still have a different default mod path such as with the OpenArena example I guess, since basepath is the root not the mod subdir.

from quake3e.

For my own project I did some tinkering and worked around it to restore the search order since Generations is dependent on baseq3 existing. If an official change comes I'll update my codebase to include but for now it works for me.

from quake3e.

Applied in 93cb470, please test by using +set fs_basegame "baseq3/missionpack"

from quake3e.

It functions, however any boolean conditions that I have checked against fs_basegame within the game source fail since they are expecting "missionpack", not "baseq3/missionpack". Examples would be spawning in Team-Arena specific weapons as opposed to replacing them with alternatives (eg, Shotgun for TA Nailgun, Lightning Gun for TA Chaingun, and Grenade Launcher for TA Prox Launcher, and ammo, et al). I can fix that in my mod by changing the string comparison to account for this, though I'm not sure if any other projects out there explicitly check fs_basegame for any of their internal logic.

from quake3e.