375 replies to this topic

[CamDawg]

BigRob, on Apr 6 2004, 07:22 PM, said:

Quote

Some classes can not be kitted - Sorcerers, monks, barbarians, and wild mages can not be kitted.

This means that these classes cannot be kitted for a PC, correct? NPC only kits for these classes can be made, can't they? (Good to know before I start trying to tinker about)

Err, no. These four really are hardcoded and unkittable. With a custom NPC though, you can grant extra abilities and such with a script that grants extra abilities at level-up.

[NiGHTMARE]

No, I don't believe you could create a kit for these class even if it were NPC-only. You could, however, simulate a kit for them by adding stuff to their .cre files, through scripting, etc.

EDIT: oh yeah, has anyone else noticed that there's a CLABMO01.2da? It suggests that Bioware at least thought about letting Monks have kits

Edited by NiGHTMARE, 06 April 2004 - 07:29 PM.

[BigRob]

Ah, thanks. Better learn some scripting then.

[Ghreyfain]

Idobek, on Apr 6 2004, 02:14 PM, said:

AddKit()ing a mage kit doesn't grant the extra spell per level.

I just tested this on Aerie, and basically just copied the cavalier entry in kitlist.2da, changed it's kit number and class number, then levelled her up. She got the extra mage spell slots that mage kits get.

[Idobek]

Heh, I had only tested this on Imoen and Nalia and assumed the problem to be universal, it is not. Adding a kit to trueclass or multiclass mage gives the extra spells. Adding a kit to a dualclass mage (or a mage/thief, at least) doesn't.

[Idobek]

Quote

KITLIST.2da - The PROFICIENCY column is unknown, save that every kit has a unique value.

I think it is the kit's column in weapprof.2da, with the ID column being 0.

Quote

LUABBR.2da (ToB only) - The index name must be 3 charactes in length; the file for the HLA table is always LUXXX.2da where XXX is the entry in this table.

I pretty sure the index name can be up to 6 charaters in length.

[Andyr]

I had some problems with the naming conventions for the LUXXX files - I don't know if the XXX is limited to 3 characters, but it seems it has to start with LU.

[CamDawg]

I dimly remember trying to use a HLA table with a name longer than LUXXX and it failed. It was a while ago, though.

[CamDawg]

Guest, on May 30 2004, 06:17 PM, said:

Hey, I'm new at this and have one question:

When you write the appending .2da files, do they have to be in that same order? (eg. in the tutorial you started with CLASWEAP, but could I have started with WEAPPROF?)

The ADD_KIT functions expects the appending done in a certain order, so you will need to stick with the order as given in the tutorial.

Quote

Also, I saw that the append stuff was after //, making it a comment?

The // comment tells WeiDU to ignore everything from // to the end of the line. Since the appends are not on the same line, they're fine. It is a bit confusing reading it on the forums, since it causes some lines to wrap depending on your setup.

The other type of commenting you may see are /* comments like this */. Anything between the /* and */ gets ignored, including if the comment runs more than one line.

[Wizard of Thay]

Ok, thanks alot Cam!

[CamDawg]

Glad to help.

[CamDawg]

Mathrim Cauthon has been kind enough to translate this tutorial into French. Part I has been translated so far and is available here.

[CamDawg]

Parts 2-4 are now translated as well. I should say that it was not just Mathrim, but the D'Oghmatiques translation team. Thanks again!

French translations:

• Part One
  
• Part Two
  
• Part Three
  
• Part Four

[Loriel]

Andyr, on Apr 6 2004, 04:54 PM, said:

Hang on...

So, you can add new mage kits as long as you don't add them to K_M_X.2DA files?

If so, does this mean we can create new mage kits and assign them to the PC with AddKit() or similar?

You mean we don't have to assign the K_M_X to mage kits? <frustration>*Commences hair pulling and screaming*</frustration> I share the common sentiment of "Why did they all say it was hardcoded, darn it!" This is what I've been doing for all my mage kits:

Create a bard kit
Create a script for changing to mage kit:

IF
blah
THEN
RESPONSE #100
ChangeClass(Myself,BARD)
AddKit(BARDKIT) // Add my kit
ChangeClass(Myself,MAGE)
ApplySpellRES("kitspell",Myself) // This spell fixes all the problems that changing to a bard created.
END

Wish I had seen this earlier!