In JO, SP mods could be set up as true mods. They could be put in their own folder in Gamedata, so they did not have to be removed to play the base game or another mod. However, unlike with JO, the gamedata method in JA just does not work 100% for some reason.

I have been working on a SP mod since JA came out. If the Base folder method is used, new sabers show in the selection menu, objectives, level descriptions, end credits, transition from a custom opening text crawl to the first map, all work fine. With the gamedata method, they don't.

While the Base method works fine, it changes base JA as soon as a mod loads up. So, as an author of a mod, if you use the Base method, so your mod is polished and works as intended, those that play base JA and/or with other mods, have to move mods in and out of the base folder to prevent conficts.

While nothing more than a minor annoyance, it's disappointing. Sorry for the rant. :-)

Yeah. It's unfortunate. And unfortunate is also the fact that Raven is not likely to release a patch just to correct some SP issue. No wonder considering how silent the SP front is.

However, you can still use the Gamedata method if you don't use the in game menu load mod option but use the batch file method. That was used, for example, in Shadriss' Deception. It works perfectly.

Just place you mod in a gamedata/moddir, and then create a text file containin nothing but the following row:

jasp +set sv_pure 0 +set fs_game mod_dir_name

Rename the text file to mod_name.bat (or something else intelligent). This batch file must be located in the Gamedata folder. You can also ship it with your mod, and the players can use it as long as they place it in the Gamedata.

Hey Lassev,

Thanks a lot man, it works like a charm! :-)