Jump to content

Alignment problems on mod class kits


Guest Mythanthar

Recommended Posts

Guest Mythanthar

Hey all! I'm not sure if this belongs here so if it doesn't feel free to move it.

 

Now, my problem is that whenever i try to pick a class kit from any mod that adds new class kits, it won't let me choose an alignment right after choosing the new kit. Original kits like enchanter, swashbuckler etc work fine but any new ones appear as if the character is not eligible for any alignment (think paladin's lawful good restriction but with lawful good being unpickable aswell.)

 

So far i haven't found any info on this so im quite stumped. This has appeared on mods like Sword & Fist, The Darkest Day, SoS, Six's Kitpack, but no info on the respective faqs or bug reports. Any insight would be appriciated.

Link to comment
Guest Mythanthar

Small update: I tried Sword & Fist on my bro's computer and everything on character creation went fine. (Although his starting screen graphics are seriously messed up... go figure..) Still having the same problems tho :/

Link to comment
Something in your install is messed up. I have no idea what could cause that, so not knowing what else might be broken, I'd probably nuke the whole thing and start from scratch.

 

Alright, thanks for the quick reply. Doing a clean reinstall now. Could that something be in the original game files? Cause if that's the case i'll have to find new ones.

 

Nope, still have the same problem. Must be something in the original game files :undecided:

Link to comment
Can you post the contents of your alignmnt.2da file from your override folder?

 

Here it is.

 

 

L_G L_N L_E N_G N_N N_E C_G C_N C_E

MAGE 1 1 1 1 1 1 1 1 1

FIGHTER 1 1 1 1 1 1 1 1 1

CLERIC 1 1 1 1 1 1 1 1 1

THIEF 0 1 1 1 1 1 1 1 1

BARD 0 1 0 1 1 1 0 1 0

PALADIN 1 0 0 0 0 0 0 0 0

DRUID 0 0 0 0 1 0 0 0 0

RANGER 1 0 0 1 0 0 1 0 0

FIGHTER_MAGE 1 1 1 1 1 1 1 1 1

FIGHTER_CLERIC 1 1 1 1 1 1 1 1 1

FIGHTER_THIEF 0 1 1 1 1 1 1 1 1

FIGHTER_MAGE_THIEF 0 1 1 1 1 1 1 1 1

MAGE_THIEF 0 1 1 1 1 1 1 1 1

CLERIC_MAGE 1 1 1 1 1 1 1 1 1

CLERIC_THIEF 0 1 1 1 1 1 1 1 1

FIGHTER_DRUID 0 0 0 0 1 0 0 0 0

FIGHTER_MAGE_CLERIC 1 1 1 1 1 1 1 1 1

CLERIC_RANGER 1 0 0 1 0 0 1 0 0

ABJURER 1 1 1 1 1 1 1 1 1

CONJURER 1 1 1 1 1 1 1 1 1

DIVINER 1 1 1 1 1 1 1 1 1

ENCHANTER 1 1 1 1 1 1 1 1 1

ILLUSIONIST 1 1 1 1 1 1 1 1 1

INVOKER 1 1 1 1 1 1 1 1 1

NECROMANCER 1 1 1 1 1 1 1 1 1

TRANSMUTER 1 1 1 1 1 1 1 1 1

BERSERKER 0 0 0 1 1 1 1 1 1

WIZARD_SLAYER 1 1 1 1 1 1 1 1 1

KENSAI 1 1 1 1 1 1 0 0 0

CAVALIER 1 0 0 0 0 0 0 0 0

INQUISITOR 1 0 0 0 0 0 0 0 0

UNDEAD_HUNTER 1 0 0 0 0 0 0 0 0

FERALAN 1 0 0 1 0 0 1 0 0

STALKER 1 0 0 1 0 0 1 0 0

BEASTMASTER 1 0 0 1 0 0 1 0 0

ASSASIN 0 1 1 1 1 1 1 1 1

BOUNTY_HUNTER 0 1 1 1 1 1 1 1 1

SWASHBUCKLER 0 1 1 1 1 1 1 1 1

BLADE 0 1 0 1 1 1 0 1 0

JESTER 0 1 0 1 1 1 0 1 0

SKALD 0 1 0 1 1 1 0 1 0

TOTEMIC_DRUID 0 0 0 0 1 0 0 0 0

SHAPESHIFTER 0 0 0 0 1 0 0 0 0

BEAST_FRIEND 0 0 0 0 1 0 0 0 0

TALOS 0 0 1 0 0 1 0 0 1

HELM 0 1 0 0 1 0 0 1 0

LATHANDER 1 0 0 1 0 0 1 0 0

SORCERER 1 1 1 1 1 1 1 1 1

MONK 1 1 1 0 0 0 0 0 0

BARBARIAN 1 1 1 1 1 1 1 1 1

WILDMAGE 1 1 1 1 1 1 1 1 1

 

I don't see the new classes in here.. does that mean i'll have to add them manually? When i installed the mod it didn't report any problems.

Link to comment

Boo @ Microsoft.

 

To make sure these silent errors don't occur, your game needs to be installed somewhere outside of Program Files. If you move an existing install, you'll need to edit baldur.ini so it points to the new location, and start the game by running bgmain.exe.

Link to comment
Boo @ Microsoft.

 

To make sure these silent errors don't occur, your game needs to be installed somewhere outside of Program Files. If you move an existing install, you'll need to edit baldur.ini so it points to the new location, and start the game by running bgmain.exe.

 

I'll keep it in mind next time im installing it. Not sure why would that work though.. Won't there still be a compatibility files folder? If not then why is there one on the first place?

Link to comment

AFAIK, the Vista developers decided applications shouldn't be able to write to \Program Files without expressly asking permission to do so. When an application doesn't have permission, instead of denying the write completely, the write is made to a different file in the "virtual store" that you can view when you hit the compatibility files button.

 

So, when you're installing a mod, it thinks it's copying files into the override, but in reality they are getting redirected to another location, where they will not be recognised when you run BG.

 

If BG is installed outside of Program Files, then the operating system won't try to interfere.

Link to comment
AFAIK, the Vista developers decided applications shouldn't be able to write to \Program Files without expressly asking permission to do so. When an application doesn't have permission, instead of denying the write completely, the write is made to a different file in the "virtual store" that you can view when you hit the compatibility files button.

 

So, when you're installing a mod, it thinks it's copying files into the override, but in reality they are getting redirected to another location, where they will not be recognised when you run BG.

 

If BG is installed outside of Program Files, then the operating system won't try to interfere.

 

Aha i see.. although im on Windows 7 i guess its the same deal. Might explain some other weird stuff going on aswell. Thanks for the heads up, it's been more then helpful :undecided:

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...